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!

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

SIP trunking: Avaya IPO Server Edition and Cisco Call Manager 2

Status
Not open for further replies.
BrianCosta

BrianCosta

Systems Engineer
Oct 25, 2018
376
JO
Hi,

I need an assist me in attempting to complete a SIP call to a Cisco Call Manager (CUCM11.5) from an Avaya IPOSE 11.1. I am able to successfully call from any Avaya IP Phone on the IP Office to any extension on the CCM, but I cannot complete any calls from the CCM to the IPOSE. Here is a sample sys monitor output from a failed call, and How I configured the SIP trunk it from my side, Have I overlooked anything?

11:57:29 519692392mS SIP Call Rx: 5
INVITE sip:1846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2a56212d74e917
From: "jabber Test" <sip:2222@172.20.101.21>;tag=27600801~a3e24dc8-8444-4488-bc75-cbe3658de430-35209806
To: <sip:1846@10.234.11.1>
Date: Tue, 14 Mar 2023 08:59:06 GMT
Call-ID: 7843ae80-4101375a-1f0e3f-156514ac@172.20.101.21
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 102 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 345a186000105000a0006c030921e027;remote=00000000000000000000000000000000
Cisco-Guid: 2017701504-0000065536-0000060454-0358945964
Session-Expires: 1800
P-Asserted-Identity: "jabber Test" <sip:2222@172.20.101.21>
Remote-Party-ID: "jabber Test" <sip:2222@172.20.101.21>;party=calling;screen=yes;privacy=off
Contact: <sip:2222@172.20.101.21:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP6C030921E027"
Max-Forwards: 69
Content-Length: 0

11:57:29 519692392mS CMCallEvt: 0000000000000000 0.1610614097.0 -1 BaseEP: NEW CMEndpoint f52ea120 TOTAL NOW=1 CALL_LIST=0
11:57:29 519692392mS Sip: SIP Line (5): sip_trunk_config_items 50020001, sip_trunk_config_items_2 00000000, voip.flags 80800949
11:57:29 519692392mS Sip: SIPDialog f52e8538 created, dialogs 3 txn_keys 1 video 1 presentation 1 camera 1 unsupp audio 0
11:57:29 519692392mS CMMap: IP::SetCodec pcp[463]b0r0 0 -> f6ac6ba8
11:57:29 519692393mS Sip: SIP Line (5) GetNetworkTopologySource Use Network Topology badly configured
11:57:29 519692393mS Sip: SIP Line (5) GetNetworkTopologySource Use Network Topology badly configured
11:57:29 519692393mS Sip: SipTCPUser 4297 has 1 dialog open (AttachDialogToSipTCPUser)
11:57:29 519692393mS Sip: SIP Line (5): License, Valid 1, Available 15, Consumed 0
11:57:29 519692393mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForRequest from 172.20.101.21:5060 to 172.20.101.21:5060
11:57:29 519692394mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForResponse from 172.20.101.21:5060 to 172.20.101.21:5060
11:57:29 519692394mS SIP Call Tx: 5
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2a56212d74e917
From: "jabber Test" <sip:2222@172.20.101.21>;tag=27600801~a3e24dc8-8444-4488-bc75-cbe3658de430-35209806
Call-ID: 7843ae80-4101375a-1f0e3f-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
To: <sip:1846@10.234.11.1>;tag=6a85cf84df11c56d
Content-Length: 0

11:57:29 519692394mS SIP Tx: TCP 10.234.11.1:5060 -> 172.20.101.21:47563
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2a56212d74e917
From: "jabber Test" <sip:2222@172.20.101.21>;tag=27600801~a3e24dc8-8444-4488-bc75-cbe3658de430-35209806
Call-ID: 7843ae80-4101375a-1f0e3f-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
To: <sip:1846@10.234.11.1>;tag=6a85cf84df11c56d
Content-Length: 0

11:57:29 519692394mS Sip: SIP Line (5): Incoming SIP Call Failed.
11:57:29 519692395mS Sip: SIP Line (5): Incoming SIP Call Failed.
11:57:29 519692395mS Sip: 0aea0b0160000551 5.1610614097.1 -1 SIPTrunk Endpoint(f52e8538) Present Call, no match (1846) from URI in To header or (1846) from request URI
11:57:29 519692395mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForResponse from 172.20.101.21:5060 to 172.20.101.21:5060
11:57:29 519692395mS SIP Call Tx: 5
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2a56212d74e917
From: "jabber Test" <sip:2222@172.20.101.21>;tag=27600801~a3e24dc8-8444-4488-bc75-cbe3658de430-35209806
Call-ID: 7843ae80-4101375a-1f0e3f-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
Reason: Q.850;cause=1;text="Unallocated (unassigned) number"
To: <sip:1846@10.234.11.1>;tag=6a85cf84df11c56d
Content-Length: 0

11:57:29 519692395mS SIP Tx: TCP 10.234.11.1:5060 -> 172.20.101.21:47563
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2a56212d74e917
From: "jabber Test" <sip:2222@172.20.101.21>;tag=27600801~a3e24dc8-8444-4488-bc75-cbe3658de430-35209806
Call-ID: 7843ae80-4101375a-1f0e3f-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
Reason: Q.850;cause=1;text="Unallocated (unassigned) number"
To: <sip:1846@10.234.11.1>;tag=6a85cf84df11c56d
Content-Length: 0

11:57:29 519692546mS SIP Rx: TCP 172.20.101.21:47563 -> 10.234.11.1:5060
ACK sip:1846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2a56212d74e917
From: "jabber Test" <sip:2222@172.20.101.21>;tag=27600801~a3e24dc8-8444-4488-bc75-cbe3658de430-35209806
To: <sip:1846@10.234.11.1>;tag=6a85cf84df11c56d
Date: Tue, 14 Mar 2023 08:59:06 GMT
Call-ID: 7843ae80-4101375a-1f0e3f-156514ac@172.20.101.21
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: presence
Content-Length: 0

SIP1_qehzyh.png

SIP2_hpemoq.png

SIP3_tb1koy.png

SIP4_k1xpre.png

SIP5_gww31v.png


I know very well that the bug is here :

11:57:29 519692395mS Sip: 0aea0b0160000551 5.1610614097.1 -1 SIPTrunk Endpoint(f52e8538) Present Call, no match (1846) from URI in To header or (1846) from request URI

Any thoughts?
 
Sort by date Sort by votes
So do you have an extension and user 1846 on the IP Office?

Stuck in a never ending cycle of file copying.
 
Upvote 0 Downvote
@sizbut: of Course I have

SIP10_t04w7a.png


SIP11_fvwm3a.png


On The IPOSE, we have a SIP trunk, The DID starts from 032091840 to 032091875, and the ext.no starts from 1840, so each extension has DID and DOD reference to the SIP trunk DID.

SIP13_ixniwk.png


SIP14_tw3jvf.png


This is the Output of systemstatus when the Cisco User call 32091846

Trace Output - All Channels:
3/14/23 11:15:57 AM-346ms Line = 5, Channel = 1, SIP Message = Response, Direction = From Switch, From = 2222@172.20.101.21, To = 32091846@10.234.11.1, Response = 100 Trying
3/14/23 11:15:57 AM-359ms Line = 5, Channel = 1, SIP Message = Response, Direction = From Switch, From = 2222@172.20.101.21, To = 32091846@10.234.11.1, Response = 503 Service Unavailable
3/14/23 11:15:57 AM-639ms Line = 5, Channel = 1, SIP Message = Ack, Direction = To Switch, From = 2222@172.20.101.21, To = 32091846@10.234.11.1
 
Upvote 0 Downvote
I'm not sure if it's 100% required in this situation, but do you have an ICR entry built for incoming group 30 with a blank incoming number and a . wildcard for the destination?
I've had to do this when integrating with other systems using SIP before.
 
 https://files.engineering.com/getfile.aspx?folder=b0aed32a-46fa-4e30-991f-eb6df5566d52&file=SIP_to_CUCM.PNG
Upvote 0 Downvote
I remember that I had to put in my incoming call route the 8xxx (so 1xxx for you) for my extension range and as destination . otherwise it would not work.

set the incoming call route to take any number with * and send it directly to an extension no matter what is called then you know if the problem is in the call routing which I think it is and then play with the settings for it.

if that is not successful then try it with Auto as setting in your URI even if you only use one of your 2 URI's which seem identical from first glance without opening both up.






Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
Upvote 0 Downvote
@BrianCosta - No "of course I have" about it - you didn't say so we had to ask.

Stuck in a never ending cycle of file copying.
 
Upvote 0 Downvote
Hi All,

I try all things you mentioned above, but nothing changed.
the cisco side try to call 1846 once and with the prefix 32091864
the no-match URI message now not occurs, but there is an " incompatible destination" and "503 services unavailable"
Here is the trace from both cases:

" 11:24:43 1134802mS SIP Rx: TCP 172.20.101.21:55586 -> 10.234.11.1:5060
INVITE sip:1846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aea9d6fe295f9
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887852~a3e24dc8-8444-4488-bc75-cbe3658de430-35228723
To: <sip:1846@10.234.11.1>
Date: Wed, 15 Mar 2023 08:26:20 GMT
Call-ID: ed9a380-4111812c-1f699a-156514ac@172.20.101.21
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 102 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 0d0959de00105000a0006c030921e027;remote=00000000000000000000000000000000
Cisco-Guid: 0249144192-0000065536-0000061739-0358945964
Session-Expires: 1800
P-Asserted-Identity: "jabber Test" <sip:9712222@172.20.101.21>
Remote-Party-ID: "jabber Test" <sip:9712222@172.20.101.21>;party=calling;screen=yes;privacy=off
Contact: <sip:9712222@172.20.101.21:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP6C030921E027"
Max-Forwards: 69
Content-Length: 0

11:24:43 1134802mS SIP Call Rx: 5
INVITE sip:1846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aea9d6fe295f9
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887852~a3e24dc8-8444-4488-bc75-cbe3658de430-35228723
To: <sip:1846@10.234.11.1>
Date: Wed, 15 Mar 2023 08:26:20 GMT
Call-ID: ed9a380-4111812c-1f699a-156514ac@172.20.101.21
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 102 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 0d0959de00105000a0006c030921e027;remote=00000000000000000000000000000000
Cisco-Guid: 0249144192-0000065536-0000061739-0358945964
Session-Expires: 1800
P-Asserted-Identity: "jabber Test" <sip:9712222@172.20.101.21>
Remote-Party-ID: "jabber Test" <sip:9712222@172.20.101.21>;party=calling;screen=yes;privacy=off
Contact: <sip:9712222@172.20.101.21:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP6C030921E027"
Max-Forwards: 69
Content-Length: 0

11:24:43 1134802mS CMCallEvt: 0000000000000000 0.268436464.0 -1 BaseEP: NEW CMEndpoint ab6f380 TOTAL NOW=1 CALL_LIST=0
11:24:43 1134802mS Sip: SIP Line (5): sip_trunk_config_items 50020001, sip_trunk_config_items_2 00000000, voip.flags 80800949
11:24:43 1134802mS Sip: SIPDialog ab663c8 created, dialogs 3 txn_keys 1 video 1 presentation 1 camera 1 unsupp audio 0
11:24:43 1134802mS CMMap: IP::SetCodec pcp[11]b0r0 0 -> ab5c6d0
11:24:43 1134803mS Sip: SipTCPUser 6 has 1 dialog open (AttachDialogToSipTCPUser)
11:24:43 1134803mS Sip: SIP Line (5): License, Valid 1, Available 15, Consumed 0
11:24:43 1134803mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForRequest from 172.20.101.21:5060 to 172.20.101.21:5060
11:24:43 1134803mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForResponse from 172.20.101.21:5060 to 172.20.101.21:5060
11:24:43 1134803mS SIP Call Tx: 5
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aea9d6fe295f9
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887852~a3e24dc8-8444-4488-bc75-cbe3658de430-35228723
Call-ID: ed9a380-4111812c-1f699a-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
To: <sip:1846@10.234.11.1>;tag=dac654dadeeff48c
Content-Length: 0

11:24:43 1134803mS SIP Tx: TCP 10.234.11.1:5060 -> 172.20.101.21:55586
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aea9d6fe295f9
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887852~a3e24dc8-8444-4488-bc75-cbe3658de430-35228723
Call-ID: ed9a380-4111812c-1f699a-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
To: <sip:1846@10.234.11.1>;tag=dac654dadeeff48c
Content-Length: 0

11:24:43 1134803mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForResponse from 172.20.101.21:5060 to 172.20.101.21:5060
11:24:43 1134803mS SIP Call Tx: 5
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aea9d6fe295f9
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887852~a3e24dc8-8444-4488-bc75-cbe3658de430-35228723
Call-ID: ed9a380-4111812c-1f699a-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
Reason: Q.850;cause=88;text="Incompatible destination"
To: <sip:1846@10.234.11.1>;tag=dac654dadeeff48c
Content-Length: 0

11:24:43 1134803mS SIP Tx: TCP 10.234.11.1:5060 -> 172.20.101.21:55586
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aea9d6fe295f9
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887852~a3e24dc8-8444-4488-bc75-cbe3658de430-35228723
Call-ID: ed9a380-4111812c-1f699a-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
Reason: Q.850;cause=88;text="Incompatible destination"
To: <sip:1846@10.234.11.1>;tag=dac654dadeeff48c
Content-Length: 0

11:24:44 1135087mS SIP Rx: TCP 172.20.101.21:55586 -> 10.234.11.1:5060
ACK sip:1846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aea9d6fe295f9
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887852~a3e24dc8-8444-4488-bc75-cbe3658de430-35228723
To: <sip:1846@10.234.11.1>;tag=dac654dadeeff48c
Date: Wed, 15 Mar 2023 08:26:20 GMT
Call-ID: ed9a380-4111812c-1f699a-156514ac@172.20.101.21
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: presence
Content-Length: 0

11:24:44 1135087mS SIP Call Rx: 5
ACK sip:1846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aea9d6fe295f9
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887852~a3e24dc8-8444-4488-bc75-cbe3658de430-35228723
To: <sip:1846@10.234.11.1>;tag=dac654dadeeff48c
Date: Wed, 15 Mar 2023 08:26:20 GMT
Call-ID: ed9a380-4111812c-1f699a-156514ac@172.20.101.21
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: presence
Content-Length: 0

11:24:44 1135393mS SIP Rx: TCP 10.234.12.246:44089 -> 10.234.11.1:5060
SUBSCRIBE sip:1840@10.234.11.1:5060;transport=tcp SIP/2.0
From: <sip:1840@adports.ae>;tag=d1d5ac88-f306-4878-90d5-679f62e56d42
To: <sip:1840@adports.ae>;tag=318b85797285db90
Call-ID: 980e2103-8fd5-4ef6-90b4-f76b42b9cc7a
CSeq: 6508 SUBSCRIBE
Max-Forwards: 70
Via: SIP/2.0/TCP 10.234.12.246:44089;branch=z9hG4bK002e1276-94d7-465b-bc71-f8825889e921
Supported: eventlist,outbound,replaces
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
User-Agent: Avaya Communicator Android/3.14.0 (FA-RELEASE54-BUILD.19; Avaya Vantage; K155D01A)
Contact: <sip:1840@10.234.12.246:44089;transport=tcp>;+sip.instance="<urn:uuid:28ec9d8a-06af-469e-aea3-9f02f87d5ee0>"
Authorization: Digest realm="ipoffice",nonce="07ebd22e03e37f7e04ac",uri="sip:adports.ae",response="41a5fb0a1fb9cb05d426ac8361eb0d35",username="1840"
Event: message-summary
Expires: 3600
Accept: application/simple-message-summary
Content-Length: 0

11:24:44 1135393mS Sip: SIPDialog ab63888 created, dialogs 4 txn_keys 1 video 1 presentation 1 camera 1 unsupp audio 0
11:24:44 1135394mS Sip: SipTCPUser 4 has 1 dialog open (AttachDialogToSipTCPUser)
11:24:44 1135394mS Sip: SipTCPUser 4 has 2 dialogs open (AttachDialogToSipTCPUser)
11:24:44 1135394mS SIP Tx: TCP 10.234.11.1:5060 -> 10.234.12.246:44089
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.234.12.246:44089;branch=z9hG4bK002e1276-94d7-465b-bc71-f8825889e921
From: <sip:1840@adports.ae>;tag=d1d5ac88-f306-4878-90d5-679f62e56d42
Call-ID: 980e2103-8fd5-4ef6-90b4-f76b42b9cc7a
CSeq: 6508 SUBSCRIBE
Expires: 180
Contact: <sip:1840@10.234.11.1:5060;transport=tcp>
Supported: timer,100rel
Server: IP Office 11.1.2.3.0 build 47
To: <sip:1840@adports.ae>;tag=318b85797285db90
Content-Length: 0

11:24:44 1135394mS SIP Tx: TCP 10.234.11.1:5060 -> 10.234.12.246:44089
NOTIFY sip:1840@10.234.12.246:44089;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.234.11.1:5060;rport;branch=z9hG4bK550459b2fb783d556412d8cd20c97b30
From: <sip:1840@adports.ae>;tag=318b85797285db90
To: <sip:1840@adports.ae;transport=tcp>;tag=d1d5ac88-f306-4878-90d5-679f62e56d42
Call-ID: 980e2103-8fd5-4ef6-90b4-f76b42b9cc7a
CSeq: 6509 NOTIFY
Contact: "Amer Alhamoori" <sip:VM.Amer%20Alhamoori@10.234.11.1:5060;transport=tcp>
Supported: timer,100rel
Max-Forwards: 70
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Content-Length: 88

Messages-Waiting: no
Message-Account: sip:1840@adports.ae
Voice-Message: 0/0 (0/0)

11:24:44 1135406mS SIP Rx: TCP 10.234.12.246:44089 -> 10.234.11.1:5060
SIP/2.0 200 OK
From: <sip:1840@adports.ae>;tag=318b85797285db90
To: <sip:1840@adports.ae;transport=tcp>;tag=d1d5ac88-f306-4878-90d5-679f62e56d42
Call-ID: 980e2103-8fd5-4ef6-90b4-f76b42b9cc7a
CSeq: 6509 NOTIFY
Via: SIP/2.0/TCP 10.234.11.1:5060;branch=z9hG4bK550459b2fb783d556412d8cd20c97b30
Supported: eventlist,outbound,replaces
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
User-Agent: Avaya Communicator Android/3.14.0 (FA-RELEASE54-BUILD.19; Avaya Vantage; K155D01A)
Content-Length: 0

11:24:45 1136088mS Sip: SIPDialog ab663c8 deleted, dialogs 3 txn_keys 0
11:24:45 1136088mS CMCallEvt: 0aea0b01100003f0 5.268436464.1 -1 SIPTrunk Endpoint: StateChange: END=X CMCSIdle->CMCSDelete
11:24:45 1136088mS Sip: SipTCPUser 6 has 1 dialog open (Close)
11:24:45 1136088mS CMTARGET: ??: ~CMTargetHandler 0ab6bdb0 ep 00000000
11:24:45 1136088mS CMCallEvt: 0aea0b01100003f0 5.268436464.1 -1 BaseEP: DELETE CMEndpoint ab6f380 TOTAL NOW=0 CALL_LIST=0
11:24:45 1136093mS CMMap: a=1.500 b=0.0 Mapper::FreeCodec freed CMRTVocoder(ab5c6d0) resource busy 0, total 120
11:24:45 1136407mS Sip: SIPDialog ab63888 deleted, dialogs 2 txn_keys 0
11:24:45 1136407mS Sip: SipTCPUser 4 has 2 dialogs open (Close)
11:24:45 1136407mS Sip: SipTCPUser 4 has 1 dialog open (Close)
11:24:45 1137116mS SIP Rx: TCP 10.234.12.9:59025 -> 10.234.11.1:5060


11:24:45 1137116mS SIP Tx: TCP 10.234.11.1:5060 -> 10.234.12.9:59025

11:24:49 1141164mS SIP Rx: TCP 172.20.101.21:55586 -> 10.234.11.1:5060
INVITE sip:32091846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aeaa019d3ae3b
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887883~a3e24dc8-8444-4488-bc75-cbe3658de430-35228729
To: <sip:32091846@10.234.11.1>
Date: Wed, 15 Mar 2023 08:26:27 GMT
Call-ID: 1305c100-41118133-1f699c-156514ac@172.20.101.21
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 102 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 3eb6d95d00105000a0006c030921e027;remote=00000000000000000000000000000000
Cisco-Guid: 0319144192-0000065536-0000061740-0358945964
Session-Expires: 1800
P-Asserted-Identity: "jabber Test" <sip:9712222@172.20.101.21>
Remote-Party-ID: "jabber Test" <sip:9712222@172.20.101.21>;party=calling;screen=yes;privacy=off
Contact: <sip:9712222@172.20.101.21:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP6C030921E027"
Max-Forwards: 69
Content-Length: 0

11:24:49 1141165mS SIP Call Rx: 5
INVITE sip:32091846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aeaa019d3ae3b
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887883~a3e24dc8-8444-4488-bc75-cbe3658de430-35228729
To: <sip:32091846@10.234.11.1>
Date: Wed, 15 Mar 2023 08:26:27 GMT
Call-ID: 1305c100-41118133-1f699c-156514ac@172.20.101.21
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 102 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 3eb6d95d00105000a0006c030921e027;remote=00000000000000000000000000000000
Cisco-Guid: 0319144192-0000065536-0000061740-0358945964
Session-Expires: 1800
P-Asserted-Identity: "jabber Test" <sip:9712222@172.20.101.21>
Remote-Party-ID: "jabber Test" <sip:9712222@172.20.101.21>;party=calling;screen=yes;privacy=off
Contact: <sip:9712222@172.20.101.21:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP6C030921E027"
Max-Forwards: 69
Content-Length: 0

11:24:49 1141165mS CMCallEvt: 0000000000000000 0.268436465.0 -1 BaseEP: NEW CMEndpoint ab6f380 TOTAL NOW=1 CALL_LIST=0
11:24:49 1141165mS Sip: SIP Line (5): sip_trunk_config_items 50020001, sip_trunk_config_items_2 00000000, voip.flags 80800949
11:24:49 1141165mS Sip: SIPDialog ab663c8 created, dialogs 3 txn_keys 1 video 1 presentation 1 camera 1 unsupp audio 0
11:24:49 1141165mS CMMap: IP::SetCodec pcp[13]b0r0 0 -> ab66298
11:24:49 1141166mS Sip: SipTCPUser 6 has 1 dialog open (AttachDialogToSipTCPUser)
11:24:49 1141166mS Sip: SIP Line (5): License, Valid 1, Available 15, Consumed 0
11:24:49 1141166mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForRequest from 172.20.101.21:5060 to 172.20.101.21:5060
11:24:49 1141167mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForResponse from 172.20.101.21:5060 to 172.20.101.21:5060
11:24:49 1141167mS SIP Call Tx: 5
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aeaa019d3ae3b
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887883~a3e24dc8-8444-4488-bc75-cbe3658de430-35228729
Call-ID: 1305c100-41118133-1f699c-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
To: <sip:32091846@10.234.11.1>;tag=94c76235f415485e
Content-Length: 0

11:24:49 1141167mS SIP Tx: TCP 10.234.11.1:5060 -> 172.20.101.21:55586
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aeaa019d3ae3b
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887883~a3e24dc8-8444-4488-bc75-cbe3658de430-35228729
Call-ID: 1305c100-41118133-1f699c-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
To: <sip:32091846@10.234.11.1>;tag=94c76235f415485e
Content-Length: 0

11:24:49 1141167mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForResponse from 172.20.101.21:5060 to 172.20.101.21:5060
11:24:49 1141167mS SIP Call Tx: 5
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aeaa019d3ae3b
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887883~a3e24dc8-8444-4488-bc75-cbe3658de430-35228729
Call-ID: 1305c100-41118133-1f699c-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
Reason: Q.850;cause=88;text="Incompatible destination"
To: <sip:32091846@10.234.11.1>;tag=94c76235f415485e
Content-Length: 0

11:24:49 1141167mS SIP Tx: TCP 10.234.11.1:5060 -> 172.20.101.21:55586
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aeaa019d3ae3b
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887883~a3e24dc8-8444-4488-bc75-cbe3658de430-35228729
Call-ID: 1305c100-41118133-1f699c-156514ac@172.20.101.21
CSeq: 102 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
Reason: Q.850;cause=88;text="Incompatible destination"
To: <sip:32091846@10.234.11.1>;tag=94c76235f415485e
Content-Length: 0

11:24:49 1141455mS SIP Rx: TCP 172.20.101.21:55586 -> 10.234.11.1:5060
ACK sip:32091846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aeaa019d3ae3b
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887883~a3e24dc8-8444-4488-bc75-cbe3658de430-35228729
To: <sip:32091846@10.234.11.1>;tag=94c76235f415485e
Date: Wed, 15 Mar 2023 08:26:27 GMT
Call-ID: 1305c100-41118133-1f699c-156514ac@172.20.101.21
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: presence
Content-Length: 0

11:24:49 1141455mS SIP Call Rx: 5
ACK sip:32091846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2aeaa019d3ae3b
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=27887883~a3e24dc8-8444-4488-bc75-cbe3658de430-35228729
To: <sip:32091846@10.234.11.1>;tag=94c76235f415485e
Date: Wed, 15 Mar 2023 08:26:27 GMT
Call-ID: 1305c100-41118133-1f699c-156514ac@172.20.101.21
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: presence
Content-Length: 0

11:24:49 1141633mS SIP Rx: TCP 10.234.12.9:59025 -> 10.234.11.1:5060
SUBSCRIBE sip:1841@10.234.11.1:5060;transport=tcp SIP/2.0
From: <sip:1841@adports.ae>;tag=cfcc965a-23c7-4739-a4db-addc52cee0e3
To: <sip:1841@adports.ae>;tag=88f4366e7cb0cf13
Call-ID: 33fa4968-a6ba-4aec-9061-39dab1232fa7
CSeq: 17285 SUBSCRIBE
Max-Forwards: 70
Via: SIP/2.0/TCP 10.234.12.9:59025;branch=z9hG4bK77925c53-5d65-491e-913c-9b80c30f7d17
Supported: eventlist,outbound,replaces
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
User-Agent: Avaya Communicator Android/3.14.0 (FA-RELEASE54-BUILD.19; Avaya Vantage; K155D01A)
Contact: <sip:1841@10.234.12.9:59025;transport=tcp>;+sip.instance="<urn:uuid:741288e7-2873-44d5-a87f-d6d82d8c102b>"
Authorization: Digest realm="ipoffice",nonce="28fd9a1ecada2ac1628d",uri="sip:adports.ae",response="116c46b6618969b2b4d35bbeafd4807f",username="1841"
Event: avaya-ccs-profile
Expires: 3600
Accept: application/profile+xml
Content-Length: 0

11:24:49 1141633mS Sip: SIPDialog ab63888 created, dialogs 4 txn_keys 1 video 1 presentation 1 camera 1 unsupp audio 0
11:24:49 1141634mS Sip: SipTCPUser 7 has 1 dialog open (AttachDialogToSipTCPUser)
11:24:49 1141634mS Sip: SipTCPUser 7 has 2 dialogs open (AttachDialogToSipTCPUser)
11:24:49 1141634mS SIP Tx: TCP 10.234.11.1:5060 -> 10.234.12.9:59025
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.234.12.9:59025;branch=z9hG4bK77925c53-5d65-491e-913c-9b80c30f7d17
From: <sip:1841@adports.ae>;tag=cfcc965a-23c7-4739-a4db-addc52cee0e3
Call-ID: 33fa4968-a6ba-4aec-9061-39dab1232fa7
CSeq: 17285 SUBSCRIBE
Expires: 180
Contact: <sip:1841@10.234.11.1:5060;transport=tcp>
Supported: timer,100rel
Server: IP Office 11.1.2.3.0 build 47
To: <sip:1841@adports.ae>;tag=88f4366e7cb0cf13
Content-Length: 0

11:24:49 1141634mS SIP Tx: TCP 10.234.11.1:5060 -> 10.234.12.9:59025
NOTIFY sip:1841@10.234.12.9:59025;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.234.11.1:5060;rport;branch=z9hG4bKb345c2c2d63be3096065736989232bfd
From: <sip:1841@adports.ae>;tag=88f4366e7cb0cf13
To: <sip:1841@adports.ae;transport=tcp>;tag=cfcc965a-23c7-4739-a4db-addc52cee0e3
Call-ID: 33fa4968-a6ba-4aec-9061-39dab1232fa7
CSeq: 17286 NOTIFY
Contact: <sip:1841@10.234.11.1:5060;transport=tcp>
Supported: timer,100rel
Max-Forwards: 70
Event: avaya-ccs-profile
Subscription-State: active
Content-Length: 0

11:24:49 1141643mS SIP Rx: TCP 10.234.12.9:59025 -> 10.234.11.1:5060
SIP/2.0 200 OK
From: <sip:1841@adports.ae>;tag=88f4366e7cb0cf13
To: <sip:1841@adports.ae;transport=tcp>;tag=cfcc965a-23c7-4739-a4db-addc52cee0e3
Call-ID: 33fa4968-a6ba-4aec-9061-39dab1232fa7
CSeq: 17286 NOTIFY
Via: SIP/2.0/TCP 10.234.11.1:5060;branch=z9hG4bKb345c2c2d63be3096065736989232bfd
Supported: eventlist,outbound,replaces
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
User-Agent: Avaya Communicator Android/3.14.0 (FA-RELEASE54-BUILD.19; Avaya Vantage; K155D01A)
Content-Length: 0

 
Upvote 0 Downvote
Have you tried setting up an incoming call route on line group 30 with an incoming number of 1XXX and then the destination of 1XXX ?

 
Upvote 0 Downvote
And Here is the trace from System Status from cisco to IPO

3/15/23 3:05:48 PM-623ms Line = 5, Channel = 1, SIP Message = Bye, Call Ref = 27, Direction = To Switch, From = 9712444@172.20.101.21, To = 32091846@10.234.11.1
3/15/23 3:05:48 PM-623ms Line = 5, Channel = 1, SIP Message = Response, Call Ref = 27, Direction = From Switch, From = 9712444@172.20.101.21, To = 32091846@10.234.11.1, Response = 200 OK

There is now no 180 Ringing Msg.
This is the trace from monitor:
5:05:48 9636486mS SIP Call Tx: 5
ACK sip:9712444@172.20.101.21:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.234.11.1:5060;rport;branch=z9hG4bK14c4fc7f36a4c7e223b043bb9770201f
From: "Control Room" <sip:32091846@10.234.11.1>;tag=d4407e0658f35d7b
To: <sip:9712444@172.20.101.21>;tag=27941799~a3e24dc8-8444-4488-bc75-cbe3658de430-35234352
Call-ID: d1096e04d41525dac29e09df6eddd89c
CSeq: 1154577902 ACK
Max-Forwards: 70
User-Agent: IP Office 11.1.2.3.0 build 47
Content-Length: 0

15:05:48 9636486mS SIP Tx: TCP 10.234.11.1:4129 -> 172.20.101.21:5060
ACK sip:9712444@172.20.101.21:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.234.11.1:5060;rport;branch=z9hG4bK14c4fc7f36a4c7e223b043bb9770201f
From: "Control Room" <sip:32091846@10.234.11.1>;tag=d4407e0658f35d7b
To: <sip:9712444@172.20.101.21>;tag=27941799~a3e24dc8-8444-4488-bc75-cbe3658de430-35234352
Call-ID: d1096e04d41525dac29e09df6eddd89c
CSeq: 1154577902 ACK
Max-Forwards: 70
User-Agent: IP Office 11.1.2.3.0 build 47
Content-Length: 0

15:05:48 9636486mS CMLineRx: v=0
CMConnect
Line: type=SIPLine 5 Call: lid=5 id=1342178369 in=0
Called[Control Room] Type=Default (100) Reason=CMDRdirect Calling[1846] Type=Internal Plan=Default
IE CMIEFastStartInfoData (6) 2 item(s)
IE CMIEFastStartInfoData (6) 2 item(s)
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=9712444
IE CMIEDeviceDetail (231) 0aea0b0150000441 LOCALE=ara HW=11 VER=11 class=CMDeviceSIPTrunk type=0 number=5 channel=1 features=0x0 rx_gain=32 tx_gain=32
ep_callid=1342178369 ipaddr=10.234.11.1 apps=0 loc=999 em_a_loc=999 em_d_loc=0 features2=0x0 is_spcall=1 ignores_dtmf=0
avgsid=<>
15:05:48 9636487mS CMCallEvt: 0aea0b0150000441 5.1342178369.0 27 SIPTrunk Endpoint: StateChange: END=B CMCSRinging->CMCSConnReq
15:05:48 9636487mS CMCallEvt: 0aea0b015000043f 357.1342178367.0 27 Control Room.0: StateChange: END=A CMCSRingBack->CMCSOGConnReq
15:05:48 9636488mS CMExtnEvt: v=0 State, new=Connected old=Alerting,0,0,Control Room
15:05:48 9636488mS CMLineTx: v=0
CMFacility
Line: type=SIPLine 5 Call: lid=5 id=1342178369 in=0
15:05:48 9636488mS Sip: 0aea0b0150000441 5.1342178369.0 27 SIPTrunk Endpoint(f5287228) received CMFacility
15:05:48 9636489mS CMExtnTx: v=1846, p1=0
CMFacility
Line: type=SIPLine 360 Call: lid=357 id=1342178367 in=0
IE CMIEFastStartInfoData (6) 2 item(s)
IE CMIEDtmf (209) CMIEDtmf oob 1, txp 101, rxp 101, fmtp = <null>, misc 12 (misc oob 1 misc rfc2833 0 prio oob 0 prio rfc2833 1)
Timed: 15/03/23 15:05
15:05:48 9636489mS Sip: ProcessDtmfFromCM
15:05:48 9636490mS CMExtnTx: v=1846, p1=0
CMConnect
Line: type=SIPLine 360 Call: lid=357 id=1342178367 in=0
Called[Control Room] Type=Default (100) Reason=CMDRdirect Calling[1846] Type=Internal Plan=Default
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=9712444
IE CMIEDeviceDetail (231) 0aea0b0150000441 LOCALE=ara HW=11 VER=11 class=CMDeviceSIPTrunk type=0 number=5 channel=1 features=0x0 rx_gain=32 tx_gain=32
ep_callid=1342178369 ipaddr=10.234.11.1 apps=0 loc=999 em_a_loc=999 em_d_loc=0 features2=0x0 is_spcall=1 ignores_dtmf=0
avgsid=<>
Timed: 15/03/23 15:05
15:05:48 9636490mS CMExtnRx: v=1846, p1=0
CMConnectAck
Line: type=SIPLine 360 Call: lid=357 id=1342178367 in=0
15:05:48 9636490mS CMCallEvt: 0aea0b015000043f 357.1342178367.0 27 Control Room.0: StateChange: END=A CMCSOGConnReq->CMCSConnected
15:05:48 9636490mS CMTARGET: 0aea0b015000043f 357.1342178367.0 27 Control Room.0: ~CMTargetHandler f527e7a0 ep f5283678
15:05:48 9636490mS CMCallEvt: 0aea0b0150000441 5.1342178369.0 27 SIPTrunk Endpoint: StateChange: END=B CMCSConnReq->CMCSConnected
15:05:48 9636491mS CMLineTx: v=0
CMConnectAck
Line: type=SIPLine 5 Call: lid=5 id=1342178369 in=0
IE CMIERespondingPartyName (228)(Type=CMNameInternalUser) name=Control Room
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:101 N:100 R:4) number=1846
IE CMIEDeviceDetail (231) 0aea0b015000043f LOCALE=ara HW=11 VER=11 class=CMDeviceSIPPhone type=180 number=7 channel=0 features=0x20110420 rx_gain=32 tx_gain=32
ep_callid=1342178367 ipaddr=10.234.11.1 apps=0 loc=0 em_a_loc=0 em_d_loc=0 features2=0x20 is_spcall=0 ignores_dtmf=1
avgsid=<>
15:05:48 9636491mS Sip: 0aea0b0150000441 5.1342178369.0 27 SIPTrunk Endpoint(f5287228) received CMConnectAck
15:05:48 9636493mS JadeMapper: Activated media RTP port: 40832, isVMConn: 0 (inUsePorts: 2, activeChannels: 2, freeChannels: 118)
15:05:48 9636493mS CMMap: PCG::MapBChan pcp[137]b0r1 cp_b f528cfd8 other_cp_b 0 type CGTypeSimple
15:05:48 9636494mS JadeMapper: Activated media RTP port: 40830, isVMConn: 0 (inUsePorts: 2, activeChannels: 2, freeChannels: 118)
15:05:48 9636494mS CMMap: PCG::MapBChan pcp[135]b0r1 cp_b f68d98b8 other_cp_b f528cfd8 type CGTypeSimple
15:05:48 9636494mS JadeMapper: Sending Map B Chan: 0x1 0x1f5 0x1 0x1f4 1 2
15:05:48 9636494mS CMMap: PlatformConnectionAudioSAP::ConnectVoice (configure) pcp[135]b0r1 echo_cancellation set to 1
15:05:48 9636494mS CMMap: PlatformConnectionAudioSAP::ConnectVoice pcp[135]b0r1 Configure 1.500
15:05:48 9636494mS CMMap: PlatformConnectionAudioSAP::ConnectVoice pcp[137]b0r1 Configure 1.501
15:05:48 9636494mS CMMap: PlatformConnectionAudioSAP::ConnectVoice pcp[137]b0r1 ConnectIndication 1.501
15:05:48 9636494mS CMMap: a=1.503 b=0.0 Mapper::FreeCodec freed CMRTVocoder(f68a6218) resource busy 2, total 120
15:05:48 9636495mS CMMap: a=1.502 b=0.0 Mapper::FreeCodec freed CMRTVocoder(f51ec6e8) resource busy 2, total 120
15:05:48 9636496mS JadeRemoteMapper: RTP Relay is 1 on port 40832
15:05:48 9636496mS JadeRemoteMapper: RTP Relay is 1 on port 40830
15:05:48 9636574mS SIP Rx: TCP 10.234.8.59:31103 -> 10.234.11.1:5060
SIP/2.0 200 OK

 
Upvote 0 Downvote
It looks like youve prefixed the exten number. 32091846@10.234.11.1

The number you are dialling is 32091846 ? but the exten is 1846 ?

If so create an incoming call route line group 30 with an incoming number as 32091846 and a destination of 1846 (the extension)
 
Upvote 0 Downvote
@21G: I try it, with no results.

Actually, there is nothing left that I have not tested, and they all return with the same result. What is the probability that there is something from Cisco?
 
Upvote 0 Downvote
Hi ...

Below is Cisco’s feedback as well, with the conclusion in the last line in red.

1- The CUCM sends the sip:32091846@10.234.11.1:5060 SIP/2.0 to the AVAYA server.


INVITE sip:32091846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2d119759fb4dc4
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=29264673~a3e24dc8-8444-4488-bc75-cbe3658de430-35285859
To: <sip:32091846@10.234.11.1>
Date: Mon, 20 Mar 2023 10:58:43 GMT
Call-ID: 2c917900-41813c63-20f56d-156514ac@172.20.101.21
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP;x-cisco-qos-tcl=true
Session-ID: 55aa935f00105000a0007064823698aa;remote=00000000000000000000000000000000
Cisco-Guid: 0747731200-0000065536-0000065185-0358945964
Session-Expires: 1800
P-Asserted-Identity: "jabber Test" <sip:9712222@172.20.101.21>
Remote-Party-ID: "jabber Test" <sip:9712700@172.20.101.21>;party=calling;screen=yes;privacy=off
Contact: <sip:9712700@172.20.101.21:5060;transport=tcp>;video;audio;+u.sip!devicename.ccm.cisco.com="BOT2222";bfcp
Max-Forwards: 13
Content-Length: 0

2- Avaya respond to CUCM with 100 trying
....
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2d119759fb4dc4
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=29264673~a3e24dc8-8444-4488-bc75-cbe3658de430-35285859
Call-ID: 2c917900-41813c63-20f56d-156514ac@172.20.101.21
CSeq: 101 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
To: <sip:32091846@10.234.11.1>;tag=ffe4ad8ebbe4dfe2
Content-Length: 0

3- Avaya respond to cucm with 503 Service Unavailable
..
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2d119759fb4dc4
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=29264673~a3e24dc8-8444-4488-bc75-cbe3658de430-35285859
Call-ID: 2c917900-41813c63-20f56d-156514ac@172.20.101.21
CSeq: 101 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.1.2.3.0 build 47
Reason: Q.850;cause=88;text="Incompatible destination"
To: <sip:32091846@10.234.11.1>;tag=ffe4ad8ebbe4dfe2
Content-Length: 0

..................


4- ACK sip form the cucm

ACK sip:32091846@10.234.11.1:5060 SIP/2.0
Via: SIP/2.0/TCP 172.20.101.21:5060;branch=z9hG4bK2d119759fb4dc4
From: "jabber Test" <sip:9712222@172.20.101.21>;tag=29264673~a3e24dc8-8444-4488-bc75-cbe3658de430-35285859
To: <sip:32091846@10.234.11.1>;tag=ffe4ad8ebbe4dfe2
Date: Mon, 20 Mar 2023 10:58:43 GMT
Call-ID: 2c917900-41813c63-20f56d-156514ac@172.20.101.21
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0

We need to investigate from the Avaya server side why its respond with 503 error.
 
Upvote 0 Downvote
Hi,

Which codecs are you using at each end ? The following would suggest the cisco is sending a different codec ? try setting it to G711ALaw at both ends of the trunk ?

Reason: Q.850;cause=88;text="Incompatible destination"


 
Upvote 0 Downvote
Hi ...

@21G: I didn't leave anything I didn't test and I don't know where the problem is
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

somewacko2
  • Question
SIP Trunking and hunt groups
Replies
2
Views
215
Menniss
Menniss
ipcom123
  • Locked
  • Question
Avaya IPO call out
Replies
3
Views
247
Westi
Westi
atcphone
  • Helpful tip
Avaya IPO Virtualization
Replies
1
Views
303
derfloh
derfloh
William C290
  • Locked
  • Question
Migrate Media Manager to Server Edition
Replies
1
Views
396
greggster
greggster
OmegaStar
  • Question
Avaya IPO R11.0 physical server migrate and update to IP0 R12 VMWare
Replies
1
Views
254
JoConnex
JoConnex

Part and Inventory Search

Sponsor

Back
Top