Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2
Full set of detailed CCM SDL traces would be needed, not just the call logs section, in order to dig in deeper. Feel free to send me a set of traces offline - I can take a quick look. I'm interested specifically in looking at the ACK from CUCM. If you send traces, it'd need to be from all nodes too. You went to SU2 and not SU2a, correct? - Dan From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Michael T. Voity Sent: Monday, July 20, 2015 10:44 AM To: voip puck cisco-voip@puck.nether.net Subject: Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2 Hello List, 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 - Message Details SENDER: [SIP_Trunk_to_Avaya_SM_in_Waterman] 132.198.214.142 GUID: 762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10 MSG_LABEL: BYE RECEIVER: 132.198.212.10 MAC_ADDRESS: SIP_Trunk_to_Avaya_SM_in_Waterman MSGTAG: 247636 MSG_TYPE: UCM_CTRACE CORRELATIONID: 1,100,14,52831.13^132.198.214.142^* TIMESTAMP: 2015/07/20 10:13:30.151 Detailed Sip Message BYE sip:69989@132.198.212.10:5060;transport=tcp SIP/2.0 Supported: 100rel, x-nortel-sipvc, replaces User-Agent: Nortel CS1000 SIP GW release_7.0 version_ssLinux-7.50.17 AVAYA-SM-6.3.4.0.634014 Av-Global-Session-ID: 77c7ab20-2ee9-11e5-847c-441ea147e4bc Via: SIP/2.0/TCP 132.198.214.142;branch=z9hG4bK931848089746318-AP;ft=6 Via: SIP/2.0/TCP 132.198.214.143:15060;rport=35524;ibmsid=local.1395266134606_56407986_67625207;branch=z9hG4bK931848089746318 Via: SIP/2.0/TCP 132.198.214.142;branch=z9hG4bK-fdd6d8-df8f3c38-31f77891-AP;ft=36420;received=132.198.214.142;rport=30320 Via: SIP/2.0/TCP 132.198.214.130:5060;branch=z9hG4bK-fdd6d8-df8f3c38-31f77891 Allow: INVITE, ACK, BYE, REGISTER, REFER, NOTIFY, CANCEL, PRACK, OPTIONS, INFO, SUBSCRIBE, UPDATE From: sip:68008@132.198.214.142sip:68008@132.198.214.142 ;tag=ad4defa8-82d6c684-13c4-55013-fdd6cb-2559fabb-fdd6cb To: 200 19 ROOSEVELT HWY sip:69989@132.198.212.10sip:69989@132.198.212.10 ;tag=99915~0beb0a3f-1893-4c98-817f-0979807ce2fb-26487138 Call-ID: 762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10 Max-Forwards: 67 CSeq: 1 BYE Content-Length: 0 Message In Log File 2015/07/20 10:13:17.606|CC|SETUP|26487137|26487138|69989|68008|68008 2015/07/20 10:13:17.642|CC|OFFERED|26487137|26487138|69989|68008|68008|SEPF02572786B0B|SIP_Trunk_to_Avaya_SM_in_Waterman 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|762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10|INVITE 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|762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10|100 Trying 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|762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10|180 Ringing 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|762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10|200 OK 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|762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10|ACK 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|762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10|BYE 2015/07/20 10:13:30.156|CC|RELEASE|26487137|26487138|16 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|762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10mailto:762c8200-5ad101fd-b8bc-ad4c684@132.198.212.10|200 OK Michael T. Voity Network Engineer University of Vermont On 7/14/2015 9:48 AM, Michael T. Voity wrote: Hi Dan, Last night I migrated to 10.5.2.SU2 and then this morning applied the ciscocm.FQDNwithDNS-v1.0.k3.cop.sgn patch. 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. I will keep my eyes on RTMT too see how things behave. -Mike
Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2
I was going to mention the FQDN issue as I ran into it last month. Also, we had a scenario where the Nortel was sending SRTP keys in the SDP and it would cause issues, though I believe the symptom there was one way audio and not a complete failure. The fix for that was to disable SRTP in the COS on the Nortel. Rob -Original Message- From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Daniel Pagan Sent: Tuesday, July 14, 2015 9:30 AM To: Michael T. Voity; voip puck Subject: Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2 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). Hope this helps. - Dan -Original Message- From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Michael T. Voity Sent: Monday, July 13, 2015 9:56 AM To: voip puck Subject: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2 Hello, Before we installed our Cisco CM 10.5.2 system everything here at the University is fed from a Nortel Avaya 81c / CS1000 system. The Telcom group has a bunch of systems on it that support SIP and SIP gateways. We setup a SIP trunk between the two systems from a guide that Avaya provided. It works fine like 99% of the time. 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 can only pass certain traffic. Example is that someone from Nortel land dials a 5 digit extension that has been routed to CUCM, the line on CUCM rings once and then discos the call. Looking at RTMT on the SIP traffic I can tell that the Nortel is sending the BYE message on the trunk right when the CUCM sends the RINGING The only way that I have found to correct this is to reset the SIP trunk from CUCM. Has anyone see an issue like this and or heard of this? Any ideas would be helpful! -Mike -- Michael T. Voity Network Engineer University of Vermont ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2
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). Hope this helps. - Dan -Original Message- From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Michael T. Voity Sent: Monday, July 13, 2015 9:56 AM To: voip puck Subject: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2 Hello, Before we installed our Cisco CM 10.5.2 system everything here at the University is fed from a Nortel Avaya 81c / CS1000 system. The Telcom group has a bunch of systems on it that support SIP and SIP gateways. We setup a SIP trunk between the two systems from a guide that Avaya provided. It works fine like 99% of the time. 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 can only pass certain traffic. Example is that someone from Nortel land dials a 5 digit extension that has been routed to CUCM, the line on CUCM rings once and then discos the call. Looking at RTMT on the SIP traffic I can tell that the Nortel is sending the BYE message on the trunk right when the CUCM sends the RINGING The only way that I have found to correct this is to reset the SIP trunk from CUCM. Has anyone see an issue like this and or heard of this? Any ideas would be helpful! -Mike -- Michael T. Voity Network Engineer University of Vermont ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2
Hi Dan, Last night I migrated to 10.5.2.SU2 and then this morning applied the ciscocm.FQDNwithDNS-v1.0.k3.cop.sgn patch. 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. I will keep my eyes on RTMT too see how things behave. -Mike Michael T. Voity Network Engineer University of Vermont (802) 656-8112 On 7/14/2015 9:29 AM, Daniel Pagan wrote: 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). Hope this helps. - Dan -Original Message- From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Michael T. Voity Sent: Monday, July 13, 2015 9:56 AM To: voip puck Subject: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2 Hello, Before we installed our Cisco CM 10.5.2 system everything here at the University is fed from a Nortel Avaya 81c / CS1000 system. The Telcom group has a bunch of systems on it that support SIP and SIP gateways. We setup a SIP trunk between the two systems from a guide that Avaya provided. It works fine like 99% of the time. 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 can only pass certain traffic. Example is that someone from Nortel land dials a 5 digit extension that has been routed to CUCM, the line on CUCM rings once and then discos the call. Looking at RTMT on the SIP traffic I can tell that the Nortel is sending the BYE message on the trunk right when the CUCM sends the RINGING The only way that I have found to correct this is to reset the SIP trunk from CUCM. Has anyone see an issue like this and or heard of this? Any ideas would be helpful! -Mike -- Michael T. Voity Network Engineer University of Vermont ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2
Sounds good. I should mention the FQDN in the Contact header is completely independent from your SIP trunk destination settings, so there's a high probability this defect was being triggered, especially if you have no issues post upgrade and patch. I've seen customers using IP addresses on their trunks and their PBX will still include an FQDN in the SIP Contact header. A working integration becoming a broken integration upon upgrading from pre 10.5(2) to 10.5(2) with no changes to the SIP trunk. Also... since we're on this topic... There's a related defect where CUCM strips the maddr= field if it's found in a SIP Contact header as well, leading to immediate call failure. Found this issue in a CUCM 10.5(2)ES integration with a Nortel environment. This would be CSCus47768. The defect mentions IPv6 but IPv4 applies to this as well. You also might not see a DNS lookup in SDL traces, but rather CUCM will simply fail to include the maddr= field found in the Contact header into the request URI. Example: CUCMNortel INVITE-- 100 180 Require 100rel -- (Contact header contains maddr= field) PRACK -- (Request URI doesn't contain the maddr= field) 500 (Destination Unreachable) CANCEL -- 200 This also applies to SIP trunks where the destination is an IP address. Hope this helps. - Dan -Original Message- From: Michael T. Voity [mailto:mvo...@uvm.edu] Sent: Tuesday, July 14, 2015 9:49 AM To: Daniel Pagan; voip puck Subject: Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2 Hi Dan, Last night I migrated to 10.5.2.SU2 and then this morning applied the ciscocm.FQDNwithDNS-v1.0.k3.cop.sgn patch. 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. I will keep my eyes on RTMT too see how things behave. -Mike Michael T. Voity Network Engineer University of Vermont (802) 656-8112 On 7/14/2015 9:29 AM, Daniel Pagan wrote: 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). Hope this helps. - Dan -Original Message- From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Michael T. Voity Sent: Monday, July 13, 2015 9:56 AM To: voip puck Subject: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2 Hello, Before we installed our Cisco CM 10.5.2 system everything here at the University is fed from a Nortel Avaya 81c / CS1000 system. The Telcom group has a bunch of systems on it that support SIP and SIP gateways. We setup a SIP trunk between the two systems from a guide that Avaya provided. It works fine like 99% of the time. 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 can only pass certain traffic. Example is that someone from Nortel land dials a 5 digit extension that has been routed to CUCM, the line on CUCM rings once and then discos the call. Looking at RTMT on the SIP traffic I can tell that the Nortel is sending the BYE message on the trunk right when the CUCM sends the RINGING The only way that I have found to correct this is to reset the SIP trunk from CUCM. Has anyone see an issue like this and or heard of this? Any ideas would be helpful! -Mike -- Michael T. Voity Network Engineer University of Vermont ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2
That's the one thing I do not have. It unpredictable when it happens. NateCCIE responded to me off list indicating I should upgrade to 10.5.2SU2 and apply the COP. He indicated that there is a bug where CS1000 and CM don't play nice. -Mike Michael T. Voity Network Engineer University of Vermont On 7/13/2015 3:36 PM, Mark Holloway wrote: Do you have a Wireshark capture of the SIP signaling for a failed call? On Jul 13, 2015, at 9:55 AM, Michael T. Voity mvo...@uvm.edu wrote: Hello, Before we installed our Cisco CM 10.5.2 system everything here at the University is fed from a Nortel Avaya 81c / CS1000 system. The Telcom group has a bunch of systems on it that support SIP and SIP gateways. We setup a SIP trunk between the two systems from a guide that Avaya provided. It works fine like 99% of the time. 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 can only pass certain traffic. Example is that someone from Nortel land dials a 5 digit extension that has been routed to CUCM, the line on CUCM rings once and then discos the call. Looking at RTMT on the SIP traffic I can tell that the Nortel is sending the BYE message on the trunk right when the CUCM sends the RINGING The only way that I have found to correct this is to reset the SIP trunk from CUCM. Has anyone see an issue like this and or heard of this? Any ideas would be helpful! -Mike -- Michael T. Voity Network Engineer University of Vermont ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2
While I am not sure if this would impact whatever issue you are having, are you running with the SIP normalization script provided in the following doc? Also, you might want to look through the rest of this doc to look for any other ideas: http://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/interoperability-portal/avaya-app-note-external.pdf -Dave On Mon, Jul 13, 2015 at 3:45 PM, Michael T. Voity mvo...@uvm.edu wrote: That's the one thing I do not have. It unpredictable when it happens. NateCCIE responded to me off list indicating I should upgrade to 10.5.2SU2 and apply the COP. He indicated that there is a bug where CS1000 and CM don't play nice. -Mike Michael T. Voity Network Engineer University of Vermont On 7/13/2015 3:36 PM, Mark Holloway wrote: Do you have a Wireshark capture of the SIP signaling for a failed call? On Jul 13, 2015, at 9:55 AM, Michael T. Voity mvo...@uvm.edu wrote: Hello, Before we installed our Cisco CM 10.5.2 system everything here at the University is fed from a Nortel Avaya 81c / CS1000 system. The Telcom group has a bunch of systems on it that support SIP and SIP gateways. We setup a SIP trunk between the two systems from a guide that Avaya provided. It works fine like 99% of the time. 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 can only pass certain traffic. Example is that someone from Nortel land dials a 5 digit extension that has been routed to CUCM, the line on CUCM rings once and then discos the call. Looking at RTMT on the SIP traffic I can tell that the Nortel is sending the BYE message on the trunk right when the CUCM sends the RINGING The only way that I have found to correct this is to reset the SIP trunk from CUCM. Has anyone see an issue like this and or heard of this? Any ideas would be helpful! -Mike -- Michael T. Voity Network Engineer University of Vermont ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
