<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-text-html" lang="x-western"> Hello all,<br>
<br>
I have been trying forever to get this Cisco 7970 to work properly
with our freeswitch (latest git). The phone will register fine,
and it will make outbound calls perfectly. The problem is with
inbound calls to this phone, where FS tries to contact it on the
wrong UDP port. The entire system here is on a local lan, and NAT
has been disabled via --nonat cmd line FS parameter.<br>
<br>
Here is what it looks like when registered:<br>
<br>
sofia status profile internal reg<br>
<br>
<tt>Call-ID: <a class="moz-txt-link-abbreviated"
href="mailto:00181844-c24f0002-25f0dff2-c470b5a7@192.168.2.59">00181844-c24f0002-25f0dff2-c470b5a7@192.168.2.59</a><br>
User: <a class="moz-txt-link-abbreviated"
href="mailto:15@x.y.com">15@x.y.com</a><br>
Contact: "user" <a class="moz-txt-link-rfc2396E"
href="sip:15@192.168.2.59:5060;transport=udp;fs_nat=yes;fs_path=sip%3A15%40192.168.2.59%3A49320%3Btransport%3Dudp"><sip:15@192.168.2.59:5060;transport=udp;fs_nat=yes;fs_path=sip%3A15%40192.168.2.59%3A49320%3Btransport%3Dudp></a><br>
Agent: Cisco-CP7970G/8.5.2<br>
Status: Registered(UDP-NAT)(unknown) EXP(2011-12-22
21:31:47) EXPSECS(724)<br>
Host: x.y.com<br>
IP: 192.168.2.59<br>
Port: 49165<br>
Auth-User: 15<br>
Auth-Realm: x.y.com<br>
</tt><br>
<br>
FS tries to contact the phone using the fs_path, which is getting
set incorrectly. I'm not why FS thinks the fs_path should be
different, as it appears the Cisco is sending proper Contact
header in the sip requests/responses.<br>
Also, we have a bunch of ATA's on the same lan which all work fine
(meaning the fs_path is correct). I tried chaning the
NDLB-force-rport param in the internal context, but didn't seems
to change anything.<br>
Here are the SIP traces which show what's happening. Any ideas of
what's going on would be appreciated.<tt> <br>
<br>
Thanks,<br>
Matt<br>
<br>
192.168.2.59 is the cisco phone. <br>
192.168.2.1 is FS (listening on port 5070).<br>
<br>
recv 713 bytes from udp/[192.168.2.59]:49320 at 02:28:01.712338:<br>
------------------------------------------------------------------------<br>
REGISTER <a class="moz-txt-link-freetext" href="sip:x.y.com">sip:x.y.com</a>
SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.2.59:5060;branch=z9hG4bKd9e43394<br>
From: <a class="moz-txt-link-rfc2396E" href="sip:15@x.y.com"><sip:15@x.y.com></a>;tag=00181844c24f0002a0bb4968-7b2b7dd4<br>
To: <a class="moz-txt-link-rfc2396E" href="sip:15@x.y.com"><sip:15@x.y.com></a><br>
Call-ID: <a class="moz-txt-link-abbreviated"
href="mailto:00181844-c24f0002-eb21e8a8-77681214@192.168.2.59">00181844-c24f0002-eb21e8a8-77681214@192.168.2.59</a><br>
Max-Forwards: 70<br>
Date: Fri, 23 Dec 2011 02:28:00 GMT<br>
CSeq: 101 REGISTER<br>
User-Agent: Cisco-CP7970G/8.5.2<br>
Contact: <a class="moz-txt-link-rfc2396E"
href="sip:15@192.168.2.59:5060;transport=udp"><sip:15@192.168.2.59:5060;transport=udp></a>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-00181844c24f>";+u.sip!model.ccm.cisco.com="30006"<br>
Supported: (null),X-cisco-xsi-7.0.1<br>
Content-Length: 0<br>
Reason: SIP;cause=200;text="cisco-alarm:20
Name=SEP00181844C24F Load=SIP70.8-5-2S Last=phone-keypad"<br>
Expires: 3600</tt><br>
<br>
<tt>send 689 bytes to udp/[192.168.2.59]:5060 at 02:28:01.715057:<br>
------------------------------------------------------------------------<br>
SIP/2.0 401 Unauthorized<br>
Via: SIP/2.0/UDP 192.168.2.59:5060;branch=z9hG4bKd9e43394<br>
From: <a class="moz-txt-link-rfc2396E" href="sip:15@x.y.com"><sip:15@x.y.com></a>;tag=00181844c24f0002a0bb4968-7b2b7dd4<br>
To: <a class="moz-txt-link-rfc2396E" href="sip:15@x.y.com"><sip:15@x.y.com></a>;tag=Qv2N52egZ2teH<br>
Call-ID: <a class="moz-txt-link-abbreviated"
href="mailto:00181844-c24f0002-eb21e8a8-77681214@192.168.2.59">00181844-c24f0002-eb21e8a8-77681214@192.168.2.59</a><br>
CSeq: 101 REGISTER<br>
User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-8059cdc
2011-12-22 14-03-32 -0600<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE,
INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, precondition, path, replaces<br>
WWW-Authenticate: Digest realm="x.y.com",
nonce="fae142ab-8b00-4ac7-89d7-04955e8714f6", algorithm=MD5,
qop="auth"<br>
Content-Length: 0</tt><br>
<br>
<tt>recv 958 bytes from udp/[192.168.2.59]:49320 at
02:28:01.725802:<br>
------------------------------------------------------------------------<br>
REGISTER <a class="moz-txt-link-freetext" href="sip:x.y.com">sip:x.y.com</a>
SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.2.59:5060;branch=z9hG4bK18d5a468<br>
From: <a class="moz-txt-link-rfc2396E" href="sip:15@x.y.com"><sip:15@x.y.com></a>;tag=00181844c24f0002a0bb4968-7b2b7dd4<br>
To: <a class="moz-txt-link-rfc2396E" href="sip:15@x.y.com"><sip:15@x.y.com></a><br>
Call-ID: <a class="moz-txt-link-abbreviated"
href="mailto:00181844-c24f0002-eb21e8a8-77681214@192.168.2.59">00181844-c24f0002-eb21e8a8-77681214@192.168.2.59</a><br>
Max-Forwards: 70<br>
Date: Fri, 23 Dec 2011 02:28:00 GMT<br>
CSeq: 102 REGISTER<br>
User-Agent: Cisco-CP7970G/8.5.2<br>
Contact: <a class="moz-txt-link-rfc2396E"
href="sip:15@192.168.2.59:5060;transport=udp"><sip:15@192.168.2.59:5060;transport=udp></a>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-00181844c24f>";+u.sip!model.ccm.cisco.com="30006"<br>
Authorization: Digest username="15",realm="x.y.com",uri=<a
class="moz-txt-link-rfc2396E" href="sip:x.y.com">"sip:x.y.com"</a>,response="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",nonce="fae142ab-8b00-4ac7-89d7-04955e8714f6",cnonce="4f2a64d4",qop=auth,nc=00000001,algorithm=MD5<br>
Supported: (null),X-cisco-xsi-7.0.1<br>
Content-Length: 0<br>
Reason: SIP;cause=200;text="cisco-alarm:20
Name=SEP00181844C24F Load=SIP70.8-5-2S Last=phone-keypad"<br>
Expires: 3600<br>
</tt><br>
<tt>send 649 bytes to udp/[192.168.2.59]:5060 at 02:28:01.737460:<br>
------------------------------------------------------------------------<br>
SIP/2.0 200 OK<br>
Via: SIP/2.0/UDP 192.168.2.59:5060;branch=z9hG4bK18d5a468<br>
From: <a class="moz-txt-link-rfc2396E" href="sip:15@x.y.com"><sip:15@x.y.com></a>;tag=00181844c24f0002a0bb4968-7b2b7dd4<br>
To: <a class="moz-txt-link-rfc2396E" href="sip:15@x.y.com"><sip:15@x.y.com></a>;tag=SeN78rgQSm7Kr<br>
Call-ID: <a class="moz-txt-link-abbreviated"
href="mailto:00181844-c24f0002-eb21e8a8-77681214@192.168.2.59">00181844-c24f0002-eb21e8a8-77681214@192.168.2.59</a><br>
CSeq: 102 REGISTER<br>
Contact: <a class="moz-txt-link-rfc2396E"
href="sip:15@192.168.2.59:5060;transport=udp"><sip:15@192.168.2.59:5060;transport=udp></a>;expires=3600<br>
Date: Fri, 23 Dec 2011 02:28:01 GMT<br>
User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-8059cdc
2011-12-22 14-03-32 -0600<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE,
INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, precondition, path, replaces<br>
Content-Length: 0<br>
</tt><br>
<b>--------------- OK, so far so good.. phone is now
registered.. Now look how FS tries to contact it.. sending
notify's here: Note the port it tries to use, 49320 in this
case.</b><br>
<br>
<tt>send 1034 bytes to udp/[192.168.2.59]:49320 at
02:28:01.837149:<br>
------------------------------------------------------------------------<br>
NOTIFY <a class="moz-txt-link-freetext"
href="sip:15@192.168.2.59:5060;transport=udp;fs_nat=yes;fs_path=sip:15%40192.168.2.59:49320%3Btransport%3Dudp">sip:15@192.168.2.59:5060;transport=udp;fs_nat=yes;fs_path=sip:15%40192.168.2.59:49320%3Btransport%3Dudp</a>
SIP/2.0<br>
Via: SIP/2.0/UDP
192.168.2.1:5070;rport;branch=z9hG4bKv92r0r53rQKNa<br>
Route: <a class="moz-txt-link-rfc2396E"
href="sip:15@192.168.2.59:49320"><sip:15@192.168.2.59:49320></a>;transport=udp<br>
Max-Forwards: 70<br>
From: <a class="moz-txt-link-rfc2396E"
href="sip:15@192.168.2.1"><sip:15@192.168.2.1></a>;tag=U07rcFjyK6KSF<br>
To: <a class="moz-txt-link-rfc2396E"
href="sip:15@192.168.2.1"><sip:15@192.168.2.1></a><br>
Call-ID: 93e179d6-a7b0-122f-d396-5254003b348b<br>
CSeq: 21967576 NOTIFY<br>
Contact: <a class="moz-txt-link-rfc2396E"
href="sip:mod_sofia@192.168.2.1:5070"><sip:mod_sofia@192.168.2.1:5070></a><br>
User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-8059cdc
2011-12-22 14-03-32 -0600<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE,
INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, precondition, path, replaces<br>
Event: message-summary<br>
Allow-Events: talk, hold, presence, dialog, line-seize,
call-info, sla, include-session-description, presence.winfo,
message-summary, refer<br>
Subscription-State: terminated;reason=timeout<br>
Content-Type: application/simple-message-summary<br>
Content-Length: 69<br>
<br>
Messages-Waiting: no<br>
Message-Account: <a class="moz-txt-link-freetext"
href="sip:15@x.y.com">sip:15@x.y.com</a></tt><br>
<br>
<b>The phone never responds, as FS is supposed to contact it on
port 5060, but FS is trying to use the same port that phone sent
is SIP messages on. Here is a sample INVITE:</b><br>
<br>
<tt>send 1229 bytes to udp/[192.168.2.59]:49320 at
02:38:15.217775:<br>
------------------------------------------------------------------------<br>
INVITE <a class="moz-txt-link-freetext"
href="sip:15@192.168.2.59:5060;transport=udp">sip:15@192.168.2.59:5060;transport=udp</a>
SIP/2.0<br>
Via: SIP/2.0/UDP
192.168.2.1:5070;rport;branch=z9hG4bK0D8U748HDUc0r<br>
Route: <a class="moz-txt-link-rfc2396E"
href="sip:15@192.168.2.59:49320"><sip:15@192.168.2.59:49320></a>;transport=udp<br>
Max-Forwards: 69<br>
From: "x x x" <a class="moz-txt-link-rfc2396E"
href="sip:11@192.168.2.1"><sip:11@192.168.2.1></a>;tag=63X9ZrB5K886e<br>
To: <a class="moz-txt-link-rfc2396E"
href="sip:15@192.168.2.59:5060;transport=udp"><sip:15@192.168.2.59:5060;transport=udp></a><br>
Call-ID: 00e33727-a7b2-122f-d396-5254003b348b<br>
CSeq: 21967883 INVITE<br>
Contact: <a class="moz-txt-link-rfc2396E"
href="sip:mod_sofia@192.168.2.1:5070"><sip:mod_sofia@192.168.2.1:5070></a><br>
User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-8059cdc
2011-12-22 14-03-32 -0600<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE,
INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, precondition, path, replaces<br>
Allow-Events: talk, hold, presence, dialog, line-seize,
call-info, sla, include-session-description, presence.winfo,
message-summary, refer<br>
Content-Type: application/sdp<br>
Content-Disposition: session<br>
Content-Length: 204<br>
X-FS-Support: update_display,send_info<br>
Remote-Party-ID: "x x x" <a class="moz-txt-link-rfc2396E"
href="sip:11@192.168.2.1"><sip:11@192.168.2.1></a>;party=calling;screen=yes;privacy=off<br>
<br>
v=0<br>
o=FreeSWITCH 1324545412 1324545413 IN IP4 192.168.2.1<br>
s=FreeSWITCH<br>
c=IN IP4 192.168.2.1<br>
t=0 0<br>
m=audio 62482 RTP/AVP 18 0 8 101 13<br>
a=rtpmap:101 telephone-event/8000<br>
a=fmtp:101 0-16<br>
a=ptime:20</tt><br>
<br>
</div>
</body>
</html>