VoIP Mailing List Archives

[mattdfong at gmail.com]

A few users of mine have been getting hung-up on after leg b of the bridge hangsups. I looked in the logs and they are being hungup with an EXCHANGE_ROUTING_ERROR hangup cause. The problem is only occurring intermittently and only when both leg a and leg b are both passed thru external gateways (the problem does not exist if leg a is a softphone connected directly to FS).

I'm wondering if there are any known incompatibilities with equipment out there that would cause this error. Otherwise, I assume the best way to diagnosis this further is to ngrep, which I'll do, but thought I'd ask here first. Thanks.


--matt
hello hunter - hosted predictive dialer & voice broadcasting
http://www.hellohunter.com

[mrene_lists at avgs.ca]

Hi,

Digging a bit in mod_sofia releaved that it can be caused by a SIP
code 482 (loop detected), 483 (too many hops) or 484 (address
incomplete).

Do a SIP trace to sched more light on what's happening.

Mathieu Rene
Avant-Garde Solutions Inc
Office: + 1 (514) 664-1044 x100
Cell: +1 (514) 664-1044 x200
mrene@avgs.ca




Am 3-Aug-09 um 1:22 AM schrieb Matthew Fong:

[mattdfong at gmail.com]

Hi Mathieu, thanks for the reply. I enabled sip trace logging and got the logs below, but I am still at a loss at being able to identify the error or reproduce it consistently. The below log indicates to me that my FS server is initiating sending 2 BYE message to my DID provider (didforsale.com). Is there a way I can look further inside FreeSWITCH to see why it is sending this BYE packet?



sent 882 bytes to udp/[209.216.2.211]:5060 at 17:15:44.679208:
BYE sip:199.173.100.144:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 66.197.142.69:5080;rport;branch=z9hG4bKD0UKrDB508mDD
Route: <sip:209.216.2.211;ftag=dc7-13c4-2401b7-46dea593-2401b7;lr=on>
Route: <sip:65.217.40.210:5060;lr>
Route: <sip:63.110.102.238;lr>
Max-Forwards: 70
From: <sip:+1212381XXXX@63.110.102.238:5060;user=phone>;tag=Ztr5ycrv3QZ1g
To: <sip:+1909635XXXX@199.173.100.144:5060;user=phone>;tag=dc7-13c4-2401b7-46dea593-2401b7
Call-ID: a22bffb89064adc713c42401b78ca6b689e90b32fdbf612c0-0487-7441
CSeq: 118584736 BYE
Contact: <sip:+1212381XXXX@66.197.142.69:5080;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-14417M
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO
Supported: timer, precondition, path, replaces
Reason: Q.850;cause=25;text="EXCHANGE_ROUTING_ERROR"
Content-Length: 0





sent 882 bytes to udp/[209.216.2.211]:5060 at 17:15:45.182589:
BYE sip:199.173.100.144:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 66.197.142.69:5080;rport;branch=z9hG4bKD0UKrDB508mDD
Route: <sip:209.216.2.211;ftag=dc7-13c4-2401b7-46dea593-2401b7;lr=on>
Route: <sip:65.217.40.210:5060;lr>
Route: <sip:63.110.102.238;lr>
Max-Forwards: 70
From: <sip:+1212381XXXX@63.110.102.238:5060;user=phone>;tag=Ztr5ycrv3QZ1g
To: <sip:+1909635XXXX@199.173.100.144:5060;user=phone>;tag=dc7-13c4-2401b7-46dea593-2401b7
Call-ID: a22bffb89064adc713c42401b78ca6b689e90b32fdbf612c0-0487-7441
CSeq: 118584736 BYE
Contact: <sip:+1212381XXXX@66.197.142.69:5080;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-14417M
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO
Supported: timer, precondition, path, replaces
Reason: Q.850;cause=25;text="EXCHANGE_ROUTING_ERROR"
Content-Length: 0


On Sun, Aug 2, 2009 at 11:20 PM, Mathieu Rene <mrene_lists@avgs.ca (mrene_lists@avgs.ca)> wrote:

[matt at hellohunter.com]

Hi Mathieu, thanks for the reply. I enabled sip trace logging and got the logs below, but I am still at a loss at being able to identify the error or reproduce it consistently. The below log indicates to me that my FS server is initiating sending 2 BYE message to my DID provider (didforsale.com). Is there a way I can look further inside FreeSWITCH to see why it is sending this BYE packet?



sent 882 bytes to udp/[209.216.2.211]:5060 at 17:15:44.679208:
BYE sip:199.173.100.144:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 66.197.142.69:5080;rport;branch=z9hG4bKD0UKrDB508mDD
Route: <sip:209.216.2.211;ftag=dc7-13c4-2401b7-46dea593-2401b7;lr=on>
Route: <sip:65.217.40.210:5060;lr>
Route: <sip:63.110.102.238;lr>
Max-Forwards: 70
From: <sip:+1212381XXXX@63.110.102.238:5060;user=phone>;tag=Ztr5ycrv3QZ1g
To: <sip:+1909635XXXX@199.173.100.144:5060;user=phone>;tag=dc7-13c4-2401b7-46dea593-2401b7
Call-ID: a22bffb89064adc713c42401b78ca6b689e90b32fdbf612c0-0487-7441
CSeq: 118584736 BYE
Contact: <sip:+1212381XXXX@66.197.142.69:5080;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-14417M
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO
Supported: timer, precondition, path, replaces
Reason: Q.850;cause=25;text="EXCHANGE_ROUTING_ERROR"
Content-Length: 0





sent 882 bytes to udp/[209.216.2.211]:5060 at 17:15:45.182589:
BYE sip:199.173.100.144:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 66.197.142.69:5080;rport;branch=z9hG4bKD0UKrDB508mDD
Route: <sip:209.216.2.211;ftag=dc7-13c4-2401b7-46dea593-2401b7;lr=on>
Route: <sip:65.217.40.210:5060;lr>
Route: <sip:63.110.102.238;lr>
Max-Forwards: 70
From: <sip:+1212381XXXX@63.110.102.238:5060;user=phone>;tag=Ztr5ycrv3QZ1g
To: <sip:+1909635XXXX@199.173.100.144:5060;user=phone>;tag=dc7-13c4-2401b7-46dea593-2401b7
Call-ID: a22bffb89064adc713c42401b78ca6b689e90b32fdbf612c0-0487-7441
CSeq: 118584736 BYE
Contact: <sip:+1212381XXXX@66.197.142.69:5080;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-14417M
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO
Supported: timer, precondition, path, replaces
Reason: Q.850;cause=25;text="EXCHANGE_ROUTING_ERROR"
Content-Length: 0





On Sun, Aug 2, 2009 at 11:20 PM, Mathieu Rene <mrene_lists@avgs.ca (mrene_lists@avgs.ca)> wrote:

[mike at jerris.com]

http://wiki.freeswitch.org/wiki/Sofia#Debugging_Sofia-SIP

turn the logging all the way up and see what it says.


Mike

On Aug 4, 2009, at 2:51 PM, Matthew Fong wrote: