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.
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 sip:1183285781@61.152.148.84 FAILED (retry: -1227500590s)
chinacts gateway sip:31200806@61.152.148.84 NOREG
vitelity gateway sip:idapted@sip5.vitelity.net FAILED (retry: -1227500590s)
sipphone gateway sip:17476731237@proxy01.sipphone.com FAILED (retry: -1227500590s)
binfone gateway sip:101586@sip.binfone.com REGED
efonica gateway sip:35299024@registrar.proxy.efonica.com 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
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org