Weird port in "Contact", SIP/2.0 200 OK message
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@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@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@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@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-... Sent from the freeswitch-users mailing list archive at Nabble.com.
Today [20130412] I made latest build, using git: 2684cc4 and I see the same story. :( FreeSWITCH advertises its port (port to connect to) as '1'. Here is the part of message it sends to SIP clients: Contact: <sip:2005@IP.IP.IP.IP:1;transport=udp> Of course it breaks further communications... Where it comes from? And, more importantly, how to fix it? Two weeks ago FS's build did not have such problem... -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
Lol wtf... Can you enable "sofia global siptrace on" then pastebin us the logs from that please. Specifically I'm wanting to know if the packets are leaving FS in this way, or if they are being mangled by something in-between. Cal On Sat, Apr 13, 2013 at 4:47 AM, FSX <ml88888@hotmail.com> wrote:
Today [20130412] I made latest build, using git: 2684cc4 and I see the same story. :( FreeSWITCH advertises its port (port to connect to) as '1'. Here is the part of message it sends to SIP clients: Contact: <sip:2005@IP.IP.IP.IP:1;transport=udp> Of course it breaks further communications...
Where it comes from? And, more importantly, how to fix it?
Two weeks ago FS's build did not have such problem...
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
Here is the log: http://pastebin.com/MTjdqbBF Watch for "Contact:" field, that FS sends in messages to its clients, and particularly, port value there... Again, configuration of FS used in this case, is the same as two weeks ago. But build is the newest. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
Can you enable debug logging and pastebin this as well? I can't think of anything off the top of my head as to why this would be happening, so hoping the debug logs shed some more info. Cal On Sun, Apr 14, 2013 at 6:12 AM, FSX <ml88888@hotmail.com> wrote:
Here is the log: http://pastebin.com/MTjdqbBF Watch for "Contact:" field, that FS sends in messages to its clients, and particularly, port value there...
Again, configuration of FS used in this case, is the same as two weeks ago. But build is the newest.
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
In attempt to find out why I can't use the latest builds, I've decided to do some experiment. As I've said earlier, I see some changes in configuration between 130326 release (working correctly) and the latest 130415 release (which is broken for me). I made 4 simple test calls to voicemail (just to reduce number of participants and therefore other potential problems). Even though that I see some (insignificant for this problem, INHO) differences in "conf" folders between builds, I've tested: 1. FS, made 130326 with its own "conf" folder 2. FS, made 130326 with new "conf" folder (copied from 130415 build) 3. FS, made 130415 with its own "conf" folder 4. FS, made 130415 with new "conf" folder (copied from 130326 build) In both 1 and 2 cases call was fine, while in both 3 and 4 cases FS fails to complete the call. It sends in its "SIP/2.0 200 OK" message this weird port in "Contact: <sip:205@IP.IP.IP.IP:1;transport=udp>"... Conclusion, some bug was introduced in FS code after 130326 (last build that I've made and it works) and before 130410 (first build, exhibiting this problem). Git hashes for these builds see in my first post. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
Why is this happening here instead of jira? On Apr 16, 2013 4:45 PM, "FSX" <ml88888@hotmail.com> wrote:
In attempt to find out why I can't use the latest builds, I've decided to do some experiment. As I've said earlier, I see some changes in configuration between 130326 release (working correctly) and the latest 130415 release (which is broken for me). I made 4 simple test calls to voicemail (just to reduce number of participants and therefore other potential problems).
Even though that I see some (insignificant for this problem, INHO) differences in "conf" folders between builds, I've tested: 1. FS, made 130326 with its own "conf" folder 2. FS, made 130326 with new "conf" folder (copied from 130415 build) 3. FS, made 130415 with its own "conf" folder 4. FS, made 130415 with new "conf" folder (copied from 130326 build)
In both 1 and 2 cases call was fine, while in both 3 and 4 cases FS fails to complete the call. It sends in its "SIP/2.0 200 OK" message this weird port in "Contact: <sip:205@IP.IP.IP.IP:1;transport=udp>"...
Conclusion, some bug was introduced in FS code after 130326 (last build that I've made and it works) and before 130410 (first build, exhibiting this problem). Git hashes for these builds see in my first post.
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
Btw check ext-sip-ip pr ext-sip-port for bad val or bad stun server. On Apr 16, 2013 5:06 PM, "Anthony Minessale" <anthony.minessale@gmail.com> wrote:
Why is this happening here instead of jira? On Apr 16, 2013 4:45 PM, "FSX" <ml88888@hotmail.com> wrote:
In attempt to find out why I can't use the latest builds, I've decided to do some experiment. As I've said earlier, I see some changes in configuration between 130326 release (working correctly) and the latest 130415 release (which is broken for me). I made 4 simple test calls to voicemail (just to reduce number of participants and therefore other potential problems).
Even though that I see some (insignificant for this problem, INHO) differences in "conf" folders between builds, I've tested: 1. FS, made 130326 with its own "conf" folder 2. FS, made 130326 with new "conf" folder (copied from 130415 build) 3. FS, made 130415 with its own "conf" folder 4. FS, made 130415 with new "conf" folder (copied from 130326 build)
In both 1 and 2 cases call was fine, while in both 3 and 4 cases FS fails to complete the call. It sends in its "SIP/2.0 200 OK" message this weird port in "Contact: <sip:205@IP.IP.IP.IP:1;transport=udp>"...
Conclusion, some bug was introduced in FS code after 130326 (last build that I've made and it works) and before 130410 (first build, exhibiting this problem). Git hashes for these builds see in my first post.
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
In all cases (working and not) "ext-rtp-ip" value is the same. But the old code works well with it now, while the new - doesn't. Here is the ext-rtp-ip/ext-sip-ip values, used in all cases: "ext-rtp-ip" = "stun:stun.counterpath.com" "ext-sip-ip" = "stun:stun.counterpath.com" I can't find "ext-sip-port" parameter in configuration though... -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
Try to comment out the param and also to use a difft stun server. Post the results in the Jira I asked to be opened because we don't like fielding issue reports over email. You try to maintain 1000 user issues in your head and you'll see where we are coming from. On Apr 16, 2013 9:39 PM, "FSX" <ml88888@hotmail.com> wrote:
In all cases (working and not) "ext-rtp-ip" value is the same. But the old code works well with it now, while the new - doesn't.
Here is the ext-rtp-ip/ext-sip-ip values, used in all cases: "ext-rtp-ip" = "stun:stun.counterpath.com" "ext-sip-ip" = "stun:stun.counterpath.com"
I can't find "ext-sip-port" parameter in configuration though...
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
Sorry that's my bad, I should have directed OP to JIRA at the beginning! Cal On Wed, Apr 17, 2013 at 3:43 AM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
Try to comment out the param and also to use a difft stun server. Post the results in the Jira I asked to be opened because we don't like fielding issue reports over email. You try to maintain 1000 user issues in your head and you'll see where we are coming from. On Apr 16, 2013 9:39 PM, "FSX" <ml88888@hotmail.com> wrote:
In all cases (working and not) "ext-rtp-ip" value is the same. But the old code works well with it now, while the new - doesn't.
Here is the ext-rtp-ip/ext-sip-ip values, used in all cases: "ext-rtp-ip" = "stun:stun.counterpath.com" "ext-sip-ip" = "stun:stun.counterpath.com"
I can't find "ext-sip-port" parameter in configuration though...
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
Commenting out both: "ext-rtp-ip" = "stun:stun.counterpath.com" "ext-sip-ip" = "stun:stun.counterpath.com" from both external.xml and internal.xml helped this time. For the record, before commenting when FS loaded in memory log indicated: Old 0326 release: 2013-04-16 13:59:42.470868 [DEBUG] sofia.c:3600 ext-rtp-ip [stun:stun.counterpath.com] 2013-04-16 13:59:42.470868 [DEBUG] sofia.c:3600 ext-sip-ip [stun:stun.counterpath.com] 2013-04-16 13:59:42.681187 [DEBUG] sofia_glue.c:1048 STUN Success [IP.IP.IP.IP]:[5080] New 0415 release: 2013-04-16 14:10:07.900078 [DEBUG] sofia.c:3686 ext-rtp-ip [stun:stun.counterpath.com] 2013-04-16 14:10:07.900078 [DEBUG] sofia.c:3686 ext-sip-ip [stun:stun.counterpath.com] 2013-04-16 14:10:09.232099 [DEBUG] sofia_glue.c:235 STUN Success [IP.IP.IP.IP]:[1] Note the different lines in sofia_glue.c file, which are generating different results... -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
Hi There, With apologies for not whinging earlier: [environment: clean Mac OS 10.6.8 with basic prerequisites installed (i.e., not using Brew/Fink/ports), on Core 2 Duo MBP] I note that, when building fS (with current as of today, with make current & make sure), I do get an odd comment in the configure output re. STUN. Running ./configure gives, during the mode_sofia part, the following fragment: configure: WARNING: ** STUN support disabled ** checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating packages/Makefile config.status: creating packages/sofia-sip-ua.pc config.status: creating packages/sofia-sip-ua-glib.pc config.status: creating libsofia-sip-ua/Makefile This has been the case for a while, but as I don't use STUN in my configurations, it doesn't bite me and does work (with my comments on fs-4786). Q: Does the configure output mean what it says, how does one enable stun support, and does this have an impact on the question here? all the best, Lawrence On 17 Apr 2013, at 03:43, Anthony Minessale wrote:
Try to comment out the param and also to use a difft stun server. Post the results in the Jira I asked to be opened because we don't like fielding issue reports over email. You try to maintain 1000 user issues in your head and you'll see where we are coming from. On Apr 16, 2013 9:39 PM, "FSX" <ml88888@hotmail.com> wrote:
In all cases (working and not) "ext-rtp-ip" value is the same. But the old code works well with it now, while the new - doesn't.
Here is the ext-rtp-ip/ext-sip-ip values, used in all cases: "ext-rtp-ip" = "stun:stun.counterpath.com" "ext-sip-ip" = "stun:stun.counterpath.com"
I can't find "ext-sip-port" parameter in configuration though...
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
We don't use that stun every anyways. Thats the one down in the sip stack. On Apr 18, 2013, at 6:14 AM, Lawrence Conroy <lconroy@insensate.co.uk> wrote:
Hi There, With apologies for not whinging earlier: [environment: clean Mac OS 10.6.8 with basic prerequisites installed (i.e., not using Brew/Fink/ports), on Core 2 Duo MBP] I note that, when building fS (with current as of today, with make current & make sure), I do get an odd comment in the configure output re. STUN. Running ./configure gives, during the mode_sofia part, the following fragment:
configure: WARNING: ** STUN support disabled ** checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating packages/Makefile config.status: creating packages/sofia-sip-ua.pc config.status: creating packages/sofia-sip-ua-glib.pc config.status: creating libsofia-sip-ua/Makefile
This has been the case for a while, but as I don't use STUN in my configurations, it doesn't bite me and does work (with my comments on fs-4786).
Q: Does the configure output mean what it says, how does one enable stun support, and does this have an impact on the question here?
all the best, Lawrence
On 17 Apr 2013, at 03:43, Anthony Minessale wrote:
Try to comment out the param and also to use a difft stun server. Post the results in the Jira I asked to be opened because we don't like fielding issue reports over email. You try to maintain 1000 user issues in your head and you'll see where we are coming from. On Apr 16, 2013 9:39 PM, "FSX" <ml88888@hotmail.com> wrote:
In all cases (working and not) "ext-rtp-ip" value is the same. But the old code works well with it now, while the new - doesn't.
Here is the ext-rtp-ip/ext-sip-ip values, used in all cases: "ext-rtp-ip" = "stun:stun.counterpath.com" "ext-sip-ip" = "stun:stun.counterpath.com"
I can't find "ext-sip-port" parameter in configuration though...
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
Could a core dev chime in? Slightly out of my depth on this one :/ Cal On Tue, Apr 16, 2013 at 10:42 PM, FSX <ml88888@hotmail.com> wrote:
In attempt to find out why I can't use the latest builds, I've decided to do some experiment. As I've said earlier, I see some changes in configuration between 130326 release (working correctly) and the latest 130415 release (which is broken for me). I made 4 simple test calls to voicemail (just to reduce number of participants and therefore other potential problems).
Even though that I see some (insignificant for this problem, INHO) differences in "conf" folders between builds, I've tested: 1. FS, made 130326 with its own "conf" folder 2. FS, made 130326 with new "conf" folder (copied from 130415 build) 3. FS, made 130415 with its own "conf" folder 4. FS, made 130415 with new "conf" folder (copied from 130326 build)
In both 1 and 2 cases call was fine, while in both 3 and 4 cases FS fails to complete the call. It sends in its "SIP/2.0 200 OK" message this weird port in "Contact: <sip:205@IP.IP.IP.IP:1;transport=udp>"...
Conclusion, some bug was introduced in FS code after 130326 (last build that I've made and it works) and before 130410 (first build, exhibiting this problem). Git hashes for these builds see in my first post.
-- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0-... Sent from the freeswitch-users mailing list archive at Nabble.com.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
participants (5)
-
Anthony Minessale
-
Cal Leeming [Simplicity Media Ltd]
-
FSX
-
Lawrence Conroy
-
Michael Jerris