VoIP Mailing List Archives

[jpalley at idapted.com]

Hi All -
Getting an odd sporadic problem with our gateways. Occasionally the registration will fail with a wrong timestamp and it will not recover from this failure until we run "sofia profile outbound restart".

Running "sofia status" gives something like:

chinacts2 gateway [url=sip:1183285781@61.152.148.84]sip:1183285781@61.152.148.84[/url] FAILED (retry: -1227500590s)
chinacts gateway [url=sip:31200806@61.152.148.84]sip:31200806@61.152.148.84[/url] NOREG
vitelity gateway [url=sip:idapted@sip5.vitelity.net]sip:idapted@sip5.vitelity.net[/url] FAILED (retry: -1227500590s)
sipphone gateway [url=sip:17476731237@proxy01.sipphone.com]sip:17476731237@proxy01.sipphone.com[/url] FAILED (retry: -1227500590s)
binfone gateway [url=sip:101586@sip.binfone.com]sip:101586@sip.binfone.com[/url] REGED
efonica gateway [url=sip:35299024@registrar.proxy.efonica.com]sip:35299024@registrar.proxy.efonica.com[/url] REGED


Notice how some gateways remained registered and others don't. The gateways are fine because, as mentioned previously, restarting the profile solves the problem.

This is happening sporadically.

Any ideas on this?

Thanks
JP

[anthony.minessale at g...]

the negative thing was a superficial bug that is fixed in trunk.
you can use the ping option in gateways to send periodic options packets that
can wake up a dead gateway once a proper response is detected.


On Sun, Nov 23, 2008 at 10:46 PM, Jonathan Palley <jpalley@idapted.com (jpalley@idapted.com)> wrote:

[jpalley at idapted.com]

Great. Thanks!

On Mon, Nov 24, 2008 at 12:55 PM, Anthony Minessale
<anthony.minessale@gmail.com> wrote:

[anthony.minessale at g...]

i made the timeout thing better in latest trunk also.


On Sun, Nov 23, 2008 at 11:19 PM, Jonathan Palley <jpalley@idapted.com (jpalley@idapted.com)> wrote: