<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello List, <br>
<br>
So the SIP error has returned. Here is the SIP messages from
RTMT. Could someone help me decipher this to see if its still a
problem with my CUCM system - <br>
<br>
<a name="details"><br>
<b>Message Details</b><br>
<br>
</a><b>SENDER</b>: [SIP_Trunk_to_Avaya_SM_in_Waterman]
132.198.214.142<br>
<b>GUID</b>: <a class="moz-txt-link-abbreviated" href="mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10">762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10</a><br>
<b>MSG_LABEL</b>: BYE<br>
<b>RECEIVER</b>: 132.198.212.10<br>
<b>MAC_ADDRESS</b>: SIP_Trunk_to_Avaya_SM_in_Waterman<br>
<b>MSGTAG</b>: 247636<br>
<b>MSG_TYPE</b>: UCM_CTRACE<br>
<b>CORRELATIONID</b>: 1,100,14,52831.13^132.198.214.142^*<br>
<b>TIMESTAMP</b>: 2015/07/20 10:13:30.151<br>
<a name="sipmsg"><br>
<b>Detailed Sip Message</b><br>
<br>
</a>BYE <a class="moz-txt-link-freetext" href="sip:69989@132.198.212.10:5060;transport=tcp">sip:69989@132.198.212.10:5060;transport=tcp</a> SIP/2.0<br>
Supported: 100rel, x-nortel-sipvc, replaces<br>
User-Agent: Nortel CS1000 SIP GW release_7.0 version_ssLinux-7.50.17
AVAYA-SM-6.3.4.0.634014<br>
Av-Global-Session-ID: 77c7ab20-2ee9-11e5-847c-441ea147e4bc<br>
Via: SIP/2.0/TCP
132.198.214.142;branch=z9hG4bK931848089746318-AP;ft=6<br>
Via: SIP/2.0/TCP
132.198.214.143:15060;rport=35524;ibmsid=local.1395266134606_56407986_67625207;branch=z9hG4bK931848089746318<br>
Via: SIP/2.0/TCP
132.198.214.142;branch=z9hG4bK-fdd6d8-df8f3c38-31f77891-AP;ft=36420;received=132.198.214.142;rport=30320<br>
Via: SIP/2.0/TCP
132.198.214.130:5060;branch=z9hG4bK-fdd6d8-df8f3c38-31f77891<br>
Allow: INVITE, ACK, BYE, REGISTER, REFER, NOTIFY, CANCEL, PRACK,
OPTIONS, INFO, SUBSCRIBE, UPDATE<br>
From: <a class="moz-txt-link-rfc2396E" href="sip:68008@132.198.214.142">< sip:68008@132.198.214.142></a>
;tag=ad4defa8-82d6c684-13c4-55013-fdd6cb-2559fabb-fdd6cb<br>
To: " 200 19 ROOSEVELT HWY" <a class="moz-txt-link-rfc2396E" href="sip:69989@132.198.212.10">< sip:69989@132.198.212.10></a>
;tag=99915~0beb0a3f-1893-4c98-817f-0979807ce2fb-26487138<br>
Call-ID: <a class="moz-txt-link-abbreviated" href="mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10">762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10</a><br>
Max-Forwards: 67<br>
CSeq: 1 BYE<br>
Content-Length: 0<br>
<br>
<a name="log"><br>
<b>Message In Log File</b><br>
<br>
</a>2015/07/20
10:13:17.606|CC|SETUP|26487137|26487138|69989|68008|68008<br>
2015/07/20
10:13:17.642|CC|OFFERED|26487137|26487138|69989|68008|68008|SEPF02572786B0B|SIP_Trunk_to_Avaya_SM_in_Waterman<br>
2015/07/20
10:13:17.642|SIPT|26487138|TCP|OUT|132.198.212.10|5060|SIP_Trunk_to_Avaya_SM_in_Waterman|132.198.214.142|5060|1,100,14,16.18836^132.198.212.10^MTP_SWICK01|247610|<a class="moz-txt-link-abbreviated" href="mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10">762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10</a>|INVITE<br>
2015/07/20
10:13:17.645|SIPT|26487138|TCP|IN|132.198.212.10|5060|SIP_Trunk_to_Avaya_SM_in_Waterman|132.198.214.142|5060|1,100,14,44771.1445^132.198.214.142^*|247611|<a class="moz-txt-link-abbreviated" href="mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10">762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10</a>|100
Trying<br>
2015/07/20
10:13:17.660|SIPT|26487138|TCP|IN|132.198.212.10|5060|SIP_Trunk_to_Avaya_SM_in_Waterman|132.198.214.142|5060|1,100,14,44771.1446^132.198.214.142^*|247612|<a class="moz-txt-link-abbreviated" href="mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10">762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10</a>|180
Ringing<br>
2015/07/20
10:13:27.535|SIPT|26487138|TCP|IN|132.198.212.10|5060|SIP_Trunk_to_Avaya_SM_in_Waterman|132.198.214.142|5060|1,100,14,44771.1447^132.198.214.142^*|247632|<a class="moz-txt-link-abbreviated" href="mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10">762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10</a>|200
OK<br>
2015/07/20
10:13:27.536|SIPT|26487138|TCP|OUT|132.198.212.10|5060|SIP_Trunk_to_Avaya_SM_in_Waterman|132.198.214.142|5060|1,100,14,44771.1447^132.198.214.142^*|247633|<a class="moz-txt-link-abbreviated" href="mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10">762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10</a>|ACK<br>
2015/07/20
10:13:30.151|SIPT|26487138|TCP|IN|132.198.212.10|5060|SIP_Trunk_to_Avaya_SM_in_Waterman|132.198.214.142|48525|1,100,14,52831.13^132.198.214.142^*|247636|<a class="moz-txt-link-abbreviated" href="mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10">762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10</a>|BYE<br>
2015/07/20 10:13:30.156|CC|RELEASE|26487137|26487138|16<br>
2015/07/20
10:13:30.157|SIPT|26487138|TCP|OUT|132.198.212.10|5060|SIP_Trunk_to_Avaya_SM_in_Waterman|132.198.214.142|48525|1,100,14,52831.13^132.198.214.142^*|247637|<a class="moz-txt-link-abbreviated" href="mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10">762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10</a>|200
OK<br>
<br>
<br>
<pre class="moz-signature" cols="72">Michael T. Voity
Network Engineer
University of Vermont
</pre>
<div class="moz-cite-prefix">On 7/14/2015 9:48 AM, Michael T. Voity
wrote:<br>
</div>
<blockquote cite="mid:55A51334.7040307@uvm.edu" type="cite">Hi Dan,
<br>
<br>
<br>
Last night I migrated to 10.5.2.SU2 and then this morning applied
the ciscocm.FQDNwithDNS-v1.0.k3.cop.sgn patch.
<br>
<br>
On both CUCM and CS1000 we are using straight IP address and not a
FQDN for comm. Since I did this patch's I am going to let
things bake and see if the error(s) returns.
<br>
<br>
I will keep my eyes on RTMT too see how things behave.
<br>
<br>
-Mike
<br>
<br>
<br>
<br>
<br>
<br>
Michael T. Voity
<br>
Network Engineer
<br>
University of Vermont
<br>
(802) 656-8112
<br>
<br>
On 7/14/2015 9:29 AM, Daniel Pagan wrote:
<br>
<blockquote type="cite">Is your Nortel PBX sending a FQDN in the
Contact header? This is important because in 10.5(2) CUCM
performs a SRV and A Record lookup on FQDNs contained in a SIP
Contact header. If this lookup fails, then expect to see a
CANCEL followed by a BYE. I encountered this a few times over
the past few months and ended up creating a defect against it.
Check out CSCuu84269. If you want, I wouldn't mind taking a
quick look at your detailed CCM SDL traces offline and letting
you know if you're experiencing this defect. If you are, I'll
send you a sample LUA script to use for converting the FQDN to
IP address as a workaround which you can use for testing and
workaround purposes (... and I can't guarantee this will work
for you).
<br>
<br>
Hope this helps.
<br>
<br>
- Dan
<br>
-----Original Message-----
<br>
From: cisco-voip [<a class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On
Behalf Of Michael T. Voity
<br>
Sent: Monday, July 13, 2015 9:56 AM
<br>
To: voip puck
<br>
Subject: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM
10.5.2
<br>
<br>
Hello,
<br>
<br>
Before we installed our Cisco CM 10.5.2 system everything here
at the
<br>
University is fed from a Nortel Avaya 81c / CS1000 system. The
Telcom
<br>
group has a bunch of systems on it that support SIP and SIP
gateways.
<br>
We setup a SIP trunk between the two systems from a guide that
Avaya
<br>
provided. It works fine like 99% of the time.
<br>
<br>
I am finding that I have to reset the SIP trunk every couple of
days because it looks like the Nortel is busying out all the
channels and it
<br>
can only pass certain traffic. Example is that someone from
Nortel
<br>
land dials a 5 digit extension that has been routed to CUCM, the
line on CUCM rings once and then discos the call.
<br>
<br>
Looking at RTMT on the SIP traffic I can tell that the Nortel is
sending
<br>
the "BYE" message on the trunk right when the CUCM sends the
"RINGING"
<br>
The only way that I have found to correct this is to reset the
SIP trunk from CUCM.
<br>
<br>
Has anyone see an issue like this and or heard of this?
<br>
<br>
Any ideas would be helpful!
<br>
<br>
-Mike
<br>
<br>
--
<br>
Michael T. Voity
<br>
Network Engineer
<br>
University of Vermont
<br>
<br>
_______________________________________________
<br>
cisco-voip mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<br>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>