[Freeswitch-users] Weird port in "Contact", SIP/2.0 200 OK message

FSX ml88888 at hotmail.com
Fri Apr 12 08:42:07 MSD 2013


After resolving latest build problems and trying to make a test call to
voicemail I see the new problem, that wasn't here in the previous builds.
When call is answered by FS, FS sends "SIP/2.0 200 OK message", which now
suddenly specified the port #1 instead of its actual port (5080). Here is
this part of the message, that FS now sends to SIP client:
   Contact: <sip:2005 at IP.IP.IP.IP:1;transport=udp>
As a result, SIP client did not ACK that message and call becomes canceled
by FS soon... No audio, of course too. Here is what FS sent in the same
configuration using previous (2 weeks ago) build:
   Contact: <sip:2005 at IP.IP.IP.IP:5080;transport=udp>
where: 5080 is example of FS port, configured for taking connections form
SIP clients.

Here is yet another difference in console log that I hope may give a clue
why is that now. In the latest build FS prints this line:
2013-04-11 21:10:57.079034 [NOTICE] sofia_media.c:92 Pre-Answer
sofia/internal/2005 at domain
while with previous build (which was working well) the line was:
2013-04-11 21:15:22.361652 [NOTICE] sofia_glue.c:4281 Pre-Answer
sofia/internal/2005 at domain

While the latest build offered a lot of configuration changes comparing to
previous (and working) version, I can't find anything related to that
strange change...

Latest build, used for test (not working) (made 130410): fe4dff7
Previous (and working well) build (made 130326):  bb3114e



--
View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-200-OK-message-tp7589685.html
Sent from the freeswitch-users mailing list archive at Nabble.com.



Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users mailing list