[cisco-voip] Nortel 81C / CS1000 SIP Trunk to CUCM 10.5.2

[Daniel Pagan]

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:

CUCM		Nortel
	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:mvoity at 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-bounces at 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 at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>