Bogdan,
I'm really not sure where that garbage is coming from.
It almost seems like some weird artifact from printing to syslog..
I had it print out the length, and I see lines like this:
pinging contact: sip:208.xx.xxx.130:7538??z len: 23
sip:208.xx.xxx.130:7538 is 23 characters long, so the
Hi James,
thanks a lot for the feedback.
The log you added does not show anything wrong - the path fields may be
missing and the so called contact part (returned by usrloc) is either
the received URI (if present), either the contact URI (if not received URI).
What looks scary are the
Hi Bogdan,
I've been monitoring it (I wrote myself a script that checks the AORs
in memory against syslog).
I haven't seen any issues lately.
The trailing garbage is weird as well. In the DB, the contacts look ok.
I haven't tracked down where that is coming from yet.
-- James
On Fri, Jul 8, 2011
Hi Andrew,
Thanks God for mentioning this - the initial report from James missed
me, and I was not aware of the bug and the fix - I just fixed it right
now on the SVN trunk and 1.6
Thanks and regards,
Bogdan
On 07/01/2011 06:45 AM, Andrew Pogrebennyk wrote:
James,
On 01.07.2011 06:42,
Hi,
I've noticed after a period of time, Nathelper will stop sending pings to
some contacts.
I've verified that the contact is still registered (it is even in the
location table) but the ping process appears to skip some contacts for
unknown reasons.
Could someone please look into this? I have
James,
On 01.07.2011 06:42, James Lamanna wrote:
Hi,
I've noticed after a period of time, Nathelper will stop sending
pings to some contacts.
I've verified that the contact is still registered (it is even in the
location table) but the ping process appears to skip some contacts
for unknown
