Please open a jira and attach sip traces.
/b
On Jun 25, 2009, at 8:07 AM, Chris Chen wrote:
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/[email protected]
entering state [calling][0]
2009-06-25 00:02:55.584468 [DEBUG] sofia_glue.c:1692 sip:[email protected];transport=tcp
Setting proxy route to sofia/external/[email protected]
2009-06-25 00:02:55.585657 [DEBUG] sofia.c:3214 Channel sofia/external/[email protected]
entering state [calling][0]
2009-06-25 00:02:55.626474 [DEBUG] sofia_glue.c:1692 sip:[email protected];transport=tcp
Setting proxy route to sofia/external/[email protected]
2009-06-25 00:02:55.627632 [DEBUG] sofia.c:3214 Channel sofia/external/[email protected]
entering state [calling][0]
2009-06-25 00:02:55.668479 [DEBUG] sofia_glue.c:1692 sip:[email protected];transport=tcp
Setting proxy route to sofia/external/[email protected]
2009-06-25 00:02:55.669608 [DEBUG] sofia.c:3214 Channel sofia/external/[email protected]
entering state [calling][0]
2009-06-25 00:02:55.710473 [DEBUG] sofia_glue.c:1692 sip:[email protected];transport=tcp
Setting proxy route to sofia/external/[email protected]
2009-06-25 00:02:55.711631 [DEBUG] sofia.c:3214 Channel sofia/external/[email protected]
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 <[email protected]>
wrote:
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
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Brian West
[email protected]
-- Meet us at ClueCon! http://www.cluecon.com
_______________________________________________
Freeswitch-users mailing list
[email protected]
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
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Brian West
[email protected]
-- Meet us at ClueCon! http://www.cluecon.com
_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
