- Cisco Community
- Technology and Support
- Collaboration
- IP Telephony and Phones
- Have you ever found a
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
CUCM and Avaya CS1000 SIP connection
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2013 05:29 AM - edited 03-16-2019 08:43 PM
Hello - looking for some help on a SIP trunk configuration between the 2 devices. Currently we are running CUCM 9.1 with Avaya Session Manager 6.3. We are having issues with the call completing from the CS 1000 to the CUCM. Below are the session traces from both the Session Manager and CUCM. The CS1000 currently has 4 digit extensions and the CUCM has 7 digit extensions. We translate the number in the Session Manager to send the 7 digits. If you could lead in the right direction I would appreciate it. WOuld this have something to do with the context coming out of Session Manager? It looks like CDP.UDP and then only the 4 digits and the CUCM needs the 7. I also attached the configurations guide used for this.
Session Manager trace:
mil-ss-01 CUCM 9
SM100 10.101.2.75 10.174.2.75
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
13:04:53.730 |<--OPTIONS-| | | | | (1) sip:10.5.1.30
13:04:53.731 |--200 OK-->| | | | | (1) 200 OK (OPTIONS)
13:04:53,734 | Request Adaptation | Adapter: mil-ss-01
13:04:53,734 | Request Adaptation | Adapter: mil-ss-01
13:04:56.183 |--INVITE-->| | | | | (2) T:7317;phone-context=cdp.udp F:anonymous@anonymous U:7317;phone-context=cdp.udp
13:04:56.184 |<--Trying--| | | | | (2) 100 Trying
13:04:56,185 | Remote host is trusted | Trusted
13:04:56,185 | Request Adaptation | Adapter: mil-ss-01
13:04:56,186 | Applied ingress Adaptation | P-Asserted-Identity=<sip:00000000@company.com>, Request-URI=sip:7317@company.com, History-Info=<sip:7317@company.com>;index=1, <sip:7317@company.com>;index=1.1
13:04:56,186 | Originating Location found | Location: mil-cs1000m-01
13:04:56,186 | Try routing to determine if emergency call | Location: mil-cs1000m-01
13:04:56,186 | Request Dial Pattern route | for: sip:7317@company.com Location: mil-cs1000m-01
13:04:56,186 | Dial Pattern route parameters | URI Domain: company.com Location: mil-cs1000m-01
13:04:56,186 | Trying Dial Pattern route | Domain: company.com Location: mil-cs1000m-01
13:04:56,186 | Dial Pattern found | for: 7317 Pattern: 7317
13:04:56,186 | Route Policy found | Pattern: 7317 RoutePolicyList: to_CUCM9
13:04:56,187 | Route found | for: sip:7317@company.com SIPEntity: CUCM 9
13:04:56,187 | Entity Link found | SIPEntity: CUCM 9 EntityLink: mil-sessionmgr-01->TCP, biDirId=null, deny=false:5060
13:04:56,187 | Request Adaptation | Adapter: CUCM 9
13:04:56,188 | Applied egress Adaptation | NoAdaptationModuleExists=true, Request-URI=sip:7657317@10.5.131.12;routeinfo=0-0, Remote-Party-ID=<sip:00000000@company.com>;party=calling;screen=no;privacy=off,
13:04:56,188 | Routing SIP request | SipEntity: CUCM 9 EntityLink: mil-sessionmgr-01->TCP:5060
13:04:56,189 | No hostname resolution required | Routing to: sip:10.5.131.12;transport=tcp;lr;phase=terminating
13:04:56.191 | |--INVITE-->| | | | (2) T:7317;phone-context=cdp.udp F:anonymous@anonymous U:7657317 P:terminating
13:04:56.196 | |<--Trying--| | | | (2) 100 Trying
13:04:56.198 | |<--Not Fou-| | | | (2) 404 Not Found
13:04:56.199 | |----ACK--->| | | | (2) sip:7657317@10.5.131.12
13:04:56,200 | Request Adaptation | Adapter: CUCM 9
13:04:56,201 | Request Adaptation | Adapter: CUCM 9
13:04:56,201 | Request Adaptation | Adapter: mil-ss-01
13:04:56.202 |<--Not Fou-| | | | | (2) 404 Not Found
13:04:56.203 |----ACK--->| | | | | (2) sip:7317
13:05:07,597 | Remote host is not trusted | Host not trusted
13:05:07,597 | Originating Location found | Location: mil-cs1000m-01
13:05:12.657 | |<--------OPTIONS-------| | | (3) sip:10.5.2.51
13:05:12,659 | Remote host is not trusted | Host not trusted
13:05:12,659 | Originating Location found | Location: mil-cs1000m-01
13:05:12.660 | |--------200 OK-------->| | | (3) 200 OK (OPTIONS)
13:05:16.877 | |<--------------OPTIONS-------------| | (4) sip:10.5.2.51
13:05:16,879 | Remote host is trusted | Trusted
13:05:16,879 | Request Adaptation | Adapter: mil-ss-01
13:05:16,879 | Applied ingress Adaptation | P-Asserted-Identity=<sip:anonymous@company.com>
13:05:16,879 | Originating Location found | Location: sas-cs1000e-01
13:05:16.880 | |--------------200 OK-------------->| | (4) 200 OK (OPTIONS)
13:05:24.463 | |<--------------------OPTIONS-------------------| (5) sip:10.5.2.51
13:05:24,465 | Remote host is not trusted | Host not trusted
13:05:24,465 | Originating Location found | Location: mil-cs1000m-01
13:05:24.466 | |--------------------200 OK-------------------->| (5) 200 OK (OPTIONS)
CUCM Trace Invite:
SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.5.2.51 on port 46314 index 6 with 3188 bytes:
[1179,NET]
INVITE sip:7657317@10.5.131.12 SIP/2.0
P-AV-Message-Id: 1_1
Route: <sip:10.5.131.12;transport=tcp;lr;phase=terminating>
History-Info: <sip:7657317@company.com>;index=1, <sip:7657317@company.com>;index=1.1
Remote-Party-ID: <sip:00000000@company.com>;party=calling;screen=no;privacy=off
Allow: INVITE, ACK, BYE, REGISTER, REFER, NOTIFY, CANCEL, PRACK, OPTIONS, INFO, SUBSCRIBE, UPDATE
Contact: <sip:00000000;phone-context=UnknownUnknown@company.com:5060;maddr=10.5.1.30;transport=tcp;user=phone;gsid=68cac530-5d21-11e3-8b45-78e3b505dc88>
Alert-Info: <cid:external@company.com>
Supported: 100rel, x-nortel-sipvc, replaces
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3
Via: SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974
Via: SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140
Via: SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
Record-Route: <sip:22d074d4@10.5.2.51;transport=tcp;lr>
Record-Route: <sip:10.5.2.50:15060;transport=tcp;ibmsid=local.1372169047609_2400497_2400521;lr>
Record-Route: <sip:22d074d4@10.5.2.51;transport=tcp;lr>
P-Charging-Vector: icid-value="68cac530-5d21-11e3-8b45-78e3b505dc88"
User-Agent: Nortel CS1000 SIP GW release_7.0 version_linux-6.50.00 AVAYA-SM-6.3.1.0.631004
P-Asserted-Identity: <sip:00000000@company.com>
From: <sip:anonymous@anonymous.invalid;user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;phone-context=cdp.udp@company.com;user=phone>
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
Max-Forwards: 66
CSeq: 1 INVITE
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 1063
Av-Global-Session-ID: 68cac530-5d21-11e3-8b45-78e3b505dc88
P-Location: SM;origlocname="mil-cs1000m-01";origsiglocname="mil-cs1000m-01";origmedialocname="mil-cs1000m-01";termlocname="Cisco BE6K";termsiglocname="Cisco BE6K";smaccounting="true"
--unique-boundary-1
Content-Type: application/sdp
SDP Message
====================================================
v=0
o=- 746 1 IN IP4 10.5.1.30
s=-
c=IN IP4 10.5.1.36
t=0 0
m=audio 5234 RTP/AVP 18 0 8 101 111
c=IN IP4 10.5.1.36
a=tcap:1 RTP/SAVP
a=crypto:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
a=crypto:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
a=pcfg:1 t=1
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
a=sendrecv
--unique-boundary-1
Content-Type: application/x-nt-mcdn-frag-hex;version=linux-6.50.00;base=x2611
Content-Disposition: signal;handling=optional
0500bc05
0107130081900000a200
09090f00e9a4830001004000
1315070011fa0f00a10d02010102020100cc040000c56000
1e0403008183
4a1c0100180001001a011404000067353505000004000000000048710000
--unique-boundary-1
Content-Type: application/x-nt-epid-frag-hex;version=linux-6.50.00;base=x2611
Content-Disposition: signal;handling=optional
011201
3c:4a:92:f4:84:f4
--unique-boundary-1--
CUCM Trying Message:
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1180,NET]
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:anonymous@anonymous.invalid;user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;phone-context=cdp.udp@company.com;user=phone>
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Content-Length: 0
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1181,NET]
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:anonymous@anonymous.invalid;user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;phone-context=cdp.udp@company.com;user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Content-Length: 0
SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.5.2.51 on port 46314 index 6 with 623 bytes:
[1182,NET]
ACK sip:7657317@10.5.131.12 SIP/2.0
Route: <sip:10.5.131.12;transport=tcp;lr;phase=terminating>
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
From: <sip:anonymous@anonymous.invalid;user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;phone-context=cdp.udp@company.com;user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3
Via: SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974
CSeq: 1 ACK
Max-Forwards: 66
Content-Length: 0
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1180,NET]
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:anonymous@anonymous.invalid;user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;phone-context=cdp.udp@company.com;user=phone>
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Content-Length: 0
CUCM not found message:
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1181,NET]
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:anonymous@anonymous.invalid;user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;phone-context=cdp.udp@company.com;user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Content-Length: 0
CUCM ACK message:
SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.5.2.51 on port 46314 index 6 with 623 bytes:
[1182,NET]
ACK sip:7657317@10.5.131.12 SIP/2.0
Route: <sip:10.5.131.12;transport=tcp;lr;phase=terminating>
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
From: <sip:anonymous@anonymous.invalid;user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;phone-context=cdp.udp@company.com;user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3
Via: SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974
CSeq: 1 ACK
Max-Forwards: 66
Content-Length: 0
Thanks.
- Labels:
-
CUCM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2013 03:08 AM
This document worked for us between CUCM BE6000 ver 9.0 and the Avaya.
The main focus on the Cisco side is this: Page 37 - 41
5.4. Define SIP Trunk Security Profile
Expand System Security Profile and select SIP Trunk Security Profile. Click to
configure a SIP Trunk Security Profile.
Enter the following values and use defaults for remaining fields:
Name Enter name
Description Enter a brief description
Incoming Transport Type Verify “TCP+UDP” is selected
Outgoing Transport Type Verify “TCP” is selected
Accept Out-of-Dialog REFER Enter
Accept Unsolicited Notification Enter
Accept Replaces Header Enter
Click . The screen below shows SIP Trunk Security Profile for the sample configuration
5.5. Define SIP Profile
Expand Device Device Settings and select SIP Profile. Click to configure a SIP
Profile.
Under SIP Profile Information section, enter the following values and use defaults for
remaining fields:
Name Enter name
Description Enter a brief description
Default MTP Telephony Event Payload Type Enter “120”
Disable Early Media on 180 Enter
Note: Disabling Early Media allows local ringback to be used.
Under Parameters used in Phone section, scroll to end of section and enter the following values
and use defaults for remaining fields:
RFC 2543 Hold Enter
Click . The screen below shows SIP Profile for the sample configuration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2013 03:14 AM
Ed,
CUCM route calls based on the request URI and not the TO header..Here is the request URI
INVITE sip:7657317@10.5.131.12 SIP/2.0
So the called number presented to CUCM is 765731...You need to check that the CSS assigned to the CUCM sip trunk has access to the partiton of this extension
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2017 11:10 AM
Have you ever found a resolution to this, I have a sip trunk between UCM (11.0) and Nortel CS1K, can call from CUCM to Nortel, but from Nortel to CUCM (8756 is CUCM extension) Invite header adds ;phone-context=cdp.udp.
The Invite looks like this,
INVITE sip:8756;phone-context=cdp.udp@companyname.org;user=phone SIP/2.0.
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.1.235.32:5060;branch=z9hG4bK12d2e9a265d4167adb4fc427-be1610d8.1,SIP/2.0/TCP 10.1.235.31:5060;branch=z9hG4bK-30f3913-f376f382-38b1b572;received=10.1.235.31
From: "Nortel softphone" <sip:5754;phone-context=cdp.udp@companyname;user=phone>;tag=7de55f8-1feb010a-13c4-55013-30f3913-803faa0-30f3913
To: <sip:8756;phone-context=cdp.udp@companyname.org;user=phone>;tag=57600663~1ce102a2-c25d-4f65-9625-b4a4aa5237a3-62178266
Date: Mon, 22 May 2017 21:19:29 GMT
Call-ID: 82d9ad8-1feb010a-13c4-55013-30f3913-6f200e2-30f3913
CSeq: 1 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Server: Cisco-CUCM11.0
Session-ID: 00000000000000000000000000000000;remote=5449dba0877b5112794947ab57600663
Content-Length: 0
I believe the content after the 8756 has to be removed, tried it with the LUA script for Nortel CS1K on Cisco's download page, but no difference, as I believe this script is for MWI and diversion headers anayway. Looking for help??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2017 11:14 PM
I am not sure if your issue is related to the sip header you are referring to. The 404 not found cucm is sending is indicative of a few things
1. Check th CSS on the sip trunk and ensure it has access to the PT of the called number
2. Verify that that the@company-name.org is set as the organisation top level domain in cucm
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: