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

[Rob Dawson]

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-bounces at 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-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

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip