Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco CUCM to CS1000 v7 Avaya System Manager 6.3 SIP Tie Line

Status
Not open for further replies.

idts

IS-IT--Management
Apr 30, 2007
2
US
Hello,
I am trying to bring up a link from a CS1000 to a CUCM v12. One the Cisco side everything looks good. The Avaya Session manager shows the Sip Entity as down 500 Service Unavailable. I have the Adaption configured and the SIP Entity. I left the locations as the Cs1000. when I check the log files it shows the CUCM up and then immediately down. I can ping from both the CUCM and Cs1000 so connectivty is there. I have been using the
Avaya Solution Interoperability Test Lab Configuring SIP Trunks among Avaya Aura® Session Manager Release 6.1, Avaya Communication Server 1000E Release 7.5 and Cisco Unified Communications Manager
Release 8.0(3) – Issue 1.0

can you point me in teh direction on what to look for in the Session Manager?
 
 https://files.engineering.com/getfile.aspx?folder=8acade45-1ec9-4e8e-9092-e80f61c88509&file=15372066-CS1000_SIP_CUCM.pdf
Look and see what ports the CUCM and SGR are set to use. ICMP (ping) is essentially portless but SIP uses ports.
 
Thanks Wanebo.
I have been more Cisco over the last 10 years and struggled with reacquiring CS1000 knowledge. I was able to ping from both CLI's to IP addresses and had no issues with responses. I actually had some issues with the CUCM showing the SIP trunk as up, but theCS1000 showed down I could use any IP in the CS1000 TLAn and get an registered SIP trunk on the cucm. I ended up going back through and found I had the incorrect IP in the CUCM SIP trunk. Reset the trunk and validated the trunk came back up. I was able to validate in the Session Manager that the SIP Entity was on line after the correct TLAN assignment. Once the trunk established I placed test calls. during testing I had intermittent call failures with a 408 timeout in the ladder diagrams from the CS1000. Then it took some time to go through the SIP logs and I found the normalization LUA was causing some of the issues and removed that. At this point removed the normalization and calls completed with no issues.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top