VoIP Mailing List Archives

[peter.olsson at vision...]

I’ve been using FS as a gateway to our OCS server for some time. It’s used just for testing, so it’s not really used every day. I don’t know when, but after some trunk update (right now I running r13945) of FS it doesn’t send the SIP traffic using tcp anymore (OCS only accepts tcp or tls).

My configuration is quite easy, I have a sofia gateway configured to OCS, this has the parameter <param name="register-transport" value="tcp"/> set in the config (nothing in the config has changed for ages). Then in the dialplan I use this gateway to connect the calls. When doing a siptrace I can see that the headers has transport=tcp set correctly, but according to the trace it’s sent using udp instead of tcp.

Has something changed so I need to configure it in another way, or is it just simply a bug? I just wanted to check this before issuing a jira case and providing more specific information and debug traces etc.

/Peter

[brian at freeswitch.org]

Please open a jira and attach sip traces of register and phone calls.

/b

On Jun 25, 2009, at 2:36 AM, Peter Olsson wrote:

[chris.chen2004 at gmai...]

I am having the same issue, now the SIP trunk over TCP between FS and Exchange 2007 UM just stops working, just stuck in a loop like this:

2009-06-25 00:02:55.542672 [DEBUG] sofia.c:3214 Channel sofia/external/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 00:02:55.584468 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/external/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 00:02:55.585657 [DEBUG] sofia.c:3214 Channel sofia/external/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 00:02:55.626474 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/external/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 00:02:55.627632 [DEBUG] sofia.c:3214 Channel sofia/external/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 00:02:55.668479 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/external/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 00:02:55.669608 [DEBUG] sofia.c:3214 Channel sofia/external/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 00:02:55.710473 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/external/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 00:02:55.711631 [DEBUG] sofia.c:3214 Channel sofia/external/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]

On my Exchange 2007 side nothing was changed which used to work fine with FS

Chris

On Thu, Jun 25, 2009 at 4:15 AM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote:

[brian at freeswitch.org]

Please open a jira and attach sip traces.

/b

On Jun 25, 2009, at 8:07 AM, Chris Chen wrote:

[peter.olsson at vision...]

Done, added as issue SFSIP-157.

Regards,

Peter Olsson

Från: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] För Brian West
Skickat: den 25 juni 2009 10:16
Till: freeswitch-users@lists.freeswitch.org
Ämne: Re: [Freeswitch-users] Outgoing sofia calls not using tcp anymore...



Please open a jira and attach sip traces of register and phone calls.


/b


On Jun 25, 2009, at 2:36 AM, Peter Olsson wrote:




I’ve been using FS as a gateway to our OCS server for some time. It’s used just for testing, so it’s not really used every day. I don’t know when, but after some trunk update (right now I running r13945) of FS it doesn’t send the SIP traffic using tcp anymore (OCS only accepts tcp or tls).



My configuration is quite easy, I have a sofia gateway configured to OCS, this has the parameter <param name="register-transport" value="tcp"/> set in the config (nothing in the config has changed for ages). Then in the dialplan I use this gateway to connect the calls. When doing a siptrace I can see that the headers has transport=tcp set correctly, but according to the trace it’s sent using udp instead of tcp.



Has something changed so I need to configure it in another way, or is it just simply a bug? I just wanted to check this before issuing a jira case and providing more specific information and debug traces etc.



/Peter


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org (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



Brian West

brian@freeswitch.org (brian@freeswitch.org)




-- Meet us at ClueCon! http://www.cluecon.com









!DSPAM:4a4333c332936913812693!

[brian at freeswitch.org]

Fixed revision 13948.


/b


On Jun 25, 2009, at 10:22 AM, Peter Olsson wrote:

[brian at freeswitch.org]

Can you verify that this is fixed... I think its related to the same issue...

/b

On Jun 25, 2009, at 8:07 AM, Chris Chen wrote:

[chris.chen2004 at gmai...]

I upgraded to 13950, still the same, keeping the same loop like the console log showing:
2009-06-25 12:23:31.951936 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:31.953179 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:31.993935 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:31.995134 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:32.35933 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:32.37184 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:32.77935 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:32.79108 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:32.119937 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:32.121170 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:32.162929 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)

Chris

On Thu, Jun 25, 2009 at 12:06 PM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote:

[anthony.minessale at g...]

are you redirecting it to yourself by any chance because of some proxy in your network?


On Thu, Jun 25, 2009 at 11:24 AM, Chris Chen <chris.chen2004@gmail.com (chris.chen2004@gmail.com)> wrote:

[peter.olsson at vision...]

What can I say - you guys provide far much better (and quicker) support then any commersial solution Thanks for the help!

/Peter


________________________________
Från: Brian West <brian@freeswitch.org>
Skickat: den 25 juni 2009 17:53
Till: freeswitch-users@lists.freeswitch.org <freeswitch-users@lists.freeswitch.org>
Ämne: Re: [Freeswitch-users] Outgoing sofia calls not using tcp anymore...

Fixed revision 13948.

/b

On Jun 25, 2009, at 10:22 AM, Peter Olsson wrote:

Done, added as issue SFSIP-157.

Regards,

Peter Olsson

Från: freeswitch-users-bounces@lists.freeswitch.org<mailto:freeswitch-users-bounces@lists.freeswitch.org> [mailto:freeswitch-users-bounces@lists.freeswitch.org] För Brian West
Skickat: den 25 juni 2009 10:16
Till: freeswitch-users@lists.freeswitch.org<mailto:freeswitch-users@lists.freeswitch.org>
Ämne: Re: [Freeswitch-users] Outgoing sofia calls not using tcp anymore...

Please open a jira and attach sip traces of register and phone calls.

/b

On Jun 25, 2009, at 2:36 AM, Peter Olsson wrote:


I’ve been using FS as a gateway to our OCS server for some time. It’s used just for testing, so it’s not really used every day. I don’t know when, but after some trunk update (right now I running r13945) of FS it doesn’t send the SIP traffic using tcp anymore (OCS only accepts tcp or tls).

My configuration is quite easy, I have a sofia gateway configured to OCS, this has the parameter <param name="register-transport" value="tcp"/> set in the config (nothing in the config has changed for ages). Then in the dialplan I use this gateway to connect the calls. When doing a siptrace I can see that the headers has transport=tcp set correctly, but according to the trace it’s sent using udp instead of tcp.

Has something changed so I need to configure it in another way, or is it just simply a bug? I just wanted to check this before issuing a jira case and providing more specific information and debug traces etc.

/Peter
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org<mailto: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

Brian West
brian@freeswitch.org<mailto:brian@freeswitch.org>

-- Meet us at ClueCon! http://www.cluecon.com<http://www.cluecon.com/>




_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org<mailto: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

Brian West
brian@freeswitch.org<mailto:brian@freeswitch.org>

-- Meet us at ClueCon! http://www.cluecon.com<http://www.cluecon.com/>




!DSPAM:4a439d8f32931361515932!

_______________________________________________
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

[brian at freeswitch.org]

I see what is wrong you're running it all on the same IP and the 302 is back to the same IP but a different port I need to fix that logic to compare the port number also.

/b

On Jun 25, 2009, at 11:24 AM, Chris Chen wrote:

[brian at freeswitch.org]

I found the problem... the fs_path refactor regression number 2 was just fixed.. It was assuming the route_uri was the contact and making it stick to the wrong place to send the invite... you should be able to update now and it work correctly.

/b

On Jun 25, 2009, at 11:35 AM, Anthony Minessale wrote:

[chris.chen2004 at gmai...]

Brian, 13952 fixed the problem, now SIP over TCP to my Exchange 2007 UM is working.
Thanks for your great work.

Chris

On Thu, Jun 25, 2009 at 12:53 PM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote:

[drago at windstream.net]

Will it be a Windows build with the fix available soon?

Drago

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Chris Chen
Sent: Thursday, June 25, 2009 1:05 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Outgoing sofia calls not using tcp anymore...


Brian, 13952 fixed the problem, now SIP over TCP to my Exchange 2007 UM is working.
Thanks for your great work.

Chris
On Thu, Jun 25, 2009 at 12:53 PM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote:
I found the problem... the fs_path refactor regression number 2 was just fixed.. It was assuming the route_uri was the contact and making it stick to the wrong place to send the invite... you should be able to update now and it work correctly.


/b


On Jun 25, 2009, at 11:35 AM, Anthony Minessale wrote:




are you redirecting it to yourself by any chance because of some proxy in your network?


On Thu, Jun 25, 2009 at 11:24 AM, Chris Chen <chris.chen2004@gmail.com (chris.chen2004@gmail.com)> wrote:
I upgraded to 13950, still the same, keeping the same loop like the console log showing:
2009-06-25 12:23:31.951936 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:31.953179 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:31.993935 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:31.995134 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:32.35933 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:32.37184 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:32.77935 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:32.79108 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:32.119937 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)
2009-06-25 12:23:32.121170 [DEBUG] sofia.c:3214 Channel sofia/internal/103@192.168.0.250 (103@192.168.0.250) entering state [calling][0]
2009-06-25 12:23:32.162929 [DEBUG] sofia_glue.c:1692 sip:103@192.168.0.250 ([email]sip%3A103@192.168.0.250[/email]);transport=tcp Setting proxy route to sofia/internal/103@192.168.0.250 (103@192.168.0.250)

Chris

On Thu, Jun 25, 2009 at 12:06 PM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote:
Can you verify that this is fixed... I think its related to the same issue...


/b


On Jun 25, 2009, at 8:07 AM, Chris Chen wrote:

[brian at freeswitch.org]

I don't think the windows build was updated to include the bug... but you can build it with MSVC Express Edition which is Free from Microsoft.

/b

On Jun 25, 2009, at 4:55 PM, Drago Totev wrote: