it's sending it to the wrong place and giving up.
is there nat involved?
if not, edit your sip profile and comment
aggressive-nat-detection and apply-nat-acl both from your config
otherwise if you don't have those options set, try enabling them instead.
The same problem happens if you are missing the options when you need them as when you have the options and you don't need them so try both.
I updated to latest svn, but exactly the same is happening now. This is a SIP trace from before I restart FreeSWITCH:And here after I restart it:I have done this several times now, and I see that FreeSWITCH always sends several SIP/2.0 200 OKand 0.5 seconds after the last one, FreeSWITCH sends a BYE sip:Unknown@81.201.82.28 SIP/2.0 message.I was wrong in my earlier message in that it was the other end who sends the bye message, it is in fact FreeSWITCH who sends it.You can see that from the traces.This is a subscribed DID from Voxbone, and I can redirect it to another URL if you want, and have my wife call the did number (she is on holiday in Romania, where the DID number is subscribed) and see if the same happens (maybe bridge to some music, so my wife doesn't have to say anything).IvanDen 9. juli. 2008 kl. 23:39 skrev Brian West:Can you update to the latest your may rev's behind?_______________________________________________On Jul 9, 2008, at 4:29 PM, Ivan C Myrvold wrote:I should add that after 1 day, the same happens again. So I have to restart FreeSWITCH at least once a day._______________________________________________IvanDen 9. juli. 2008 kl. 23:16 skrev Ivan C Myrvold:My FreeSWITCH is behind nat, and I have calls coming in from internet on port 5060. This works great after I got the IP range set in acl.conf.xml._______________________________________________But the calls get hung up after 40-50 seconds into the call for no reason at all. But after I restart FreeSWITCH, this annoying behaviour doesn't happen.I traced both cases, when the call is hung up here:It looks like FreeSWITCH is resending SIP/2.0 200 OK for some reason, until the other end gives up and sends a BYE sip:Unknown@81.201.82.28 SIP/2.0But after a restart, FreeSWITCH behaves much better, and the call goes on until one of the parties hang up normally:I am not sure if this is a bug, or a misconfiguration of FreeSWITCHFreeSWITCH Version 1.0.trunk (8900)Ivan
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
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
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
_______________________________________________
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