Are they ignoring the options packet we send them or are they maybe getting lost behind NAT?
we send an OPTIONS and even if we get a error back we consider that a successful reply.
We did have a patch into SVN very recently to correct a problem with OPTIONS ping in a NAT situation.
Maybe try latest trunk first then capture the console log with sip traffic in place if it still does not work so we can have a look.
to capture the log use these 2 commands from the cli.
sofia profile internal siptrace on
console loglevel debug
Hi,I'm fairly sure my problem lies with my voip provider VoipTalk but wonder if you could help me understand a couple of things. My config is very simple, I'm using freeswitch to accept incoming calls via a voip gateway and record messages. Here's the problem:- When freeswitch starts the gateways are all created and register correctly- I have the ping parameter set to make sure the gateway stays alive.- The first time freeswitch pings the gateway it fails even though the registration appears intact as calls are still coming through to freeswitch- Freeswitch then tries to re-register the gateway but this fails. The SIP trace shows an Unauthorized message and the actual log entry is 'Registration Failed with status Operation has no matching challenge [904]'- eventually the registration times out with my provider and all is lost.- if I call 'sofia profile external restart' or restart the software this fixes the problemMy questions are:1) Why would the ping fail when the registration appears to be intact?2) Whay would the auto re-register not work but a restart would?This ones driving me nuts so any help greatly appreciated.regardsAndy
_______________________________________________
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