04-13-2017 01:05 AM - edited 03-18-2019 12:13 PM
my system is
CUCM---- SIP TRUNK -------CUBE--------NON CİSCO GATEWAY
When there is call outbound to my system there is no problem but when I try to call outbound call ,I couldn't and teher is no ccsişp message on the debug
04-13-2017 02:45 AM
Hi Ozden,
The description is not clear, are the outbound calls failing or the inbound calls? Do you get the debugs for any of the inbound or outbound calls or do you not see any debugs for any type of call?
Manish
04-13-2017 03:28 AM
when I call local to outside .there is no debug message in ths router and when outside call to local there is no problem
MS2_VG#
*Apr 13 10:33:08.050: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:1201@172.23.1.77:5060 SIP/2.0
Via: SIP/2.0/UDP 172.23.1.78:5060;branch=z9hG4bK49452d15a
Max-Forwards: 70
Content-Length: 193
To: sip:1201@172.23.1.77:5060
From: sip:8@172.23.1.78:5060;tag=3a07abf8a0105d1
Call-ID: 7120fc2b8deb3af44a4505b0514b00f5@172.23.1.78
CSeq: 1487300946 INVITE
Supported: timer
Content-Type: application/sdp
Contact: sip:8@172.23.1.78:5060
Supported: replaces
User-Agent: Patton SN4634 3BIS MxSF v3.2.7.44 00A0BA0BE6FE
v=0
o=MxSIP 0 90 IN IP4 172.23.1.78
s=SIP Call
c=IN IP4 172.23.1.78
t=0 0
m=audio 5042 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
*Apr 13 10:33:08.060: //328/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:1201@172.23.23.10:5060 SIP/2.0
Via: SIP/2.0/TCP 172.23.98.4:5060;branch=z9hG4bKBA12AA
Remote-Party-ID: <sip:8@172.23.98.4>;party=calling;screen=no;privacy=off
From: <sip:8@172.23.98.4>;tag=AA667AF-1530
To: <sip:1201@172.23.23.10>
Date: Thu, 13 Apr 2017 10:33:08 GMT
Call-ID: 6B51E374-1F6B11E7-82A4FE6A-A90FAAC2@172.23.98.4
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1800448652-0527110631-2191457898-2836376258
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S2
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1492079588
Contact: <sip:8@172.23.98.4:5060;transport=tcp>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 211
v=0
o=CiscoSystemsSIP-GW-UserAgent 7817 3556 IN IP4 172.23.98.4
s=SIP Call
c=IN IP4 172.23.98.4
t=0 0
m=audio 8246 RTP/AVP 0 19
c=IN IP4 172.23.98.4
a=rtpmap:0 PCMU/8000
a=rtpmap:19 CN/8000
a=ptime:20
*Apr 13 10:33:08.061: //327/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.23.1.78:5060;branch=z9hG4bK49452d15a
From: sip:8@172.23.1.78:5060;tag=3a07abf8a0105d1
To: sip:1201@172.23.1.77:5060
Date: Thu, 13 Apr 2017 10:33:08 GMT
Call-ID: 7120fc2b8deb3af44a4505b0514b00f5@172.23.1.78
CSeq: 1487300946 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.5.3.S2
Content-Length: 0
*Apr 13 10:33:08.063: //328/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.23.98.4:5060;branch=z9hG4bKBA12AA
From: <sip:8@172.23.98.4>;tag=AA667AF-1530
To: <sip:1201@172.23.23.10>
Date: Thu, 13 Apr 2017 10:27:13 GMT
Call-ID: 6B51E374-1F6B11E7-82A4FE6A-A90FAAC2@172.23.98.4
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0
*Apr 13 10:33:08.116: //328/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 172.23.98.4:5060;branch=z9hG4bKBA12AA
From: <sip:8@172.23.98.4>;tag=AA667AF-1530
To: <sip:1201@172.23.23.10>;tag=1837748~8a6cc906-57da-4ec7-813c-f6a08adcaf62-23884583
Date: Thu, 13 Apr 2017 10:27:13 GMT
Call-ID: 6B51E374-1F6B11E7-82A4FE6A-A90FAAC2@172.23.98.4
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Server: Cisco-CUCM11.5
Call-Info: <sip:172.23.23.10:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP;x-cisco-qos-tcl=true
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-ID: 212fca1b00105000a00094d4690c269e;remote=bd13e3c2a120ab256686c41ab1837748
P-Asserted-Identity: "BCC TEST1" <sip:1201@172.23.23.10>
Remote-Party-ID: "BCC TEST1" <sip:1201@172.23.23.10>;party=called;screen=yes;privacy=off
Contact: <sip:1201@172.23.23.10:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP94D4690C269E";video
Content-Length: 0
*Apr 13 10:33:08.117: //327/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.23.1.78:5060;branch=z9hG4bK49452d15a
From: sip:8@172.23.1.78:5060;tag=3a07abf8a0105d1
To: sip:1201@172.23.1.77:5060;tag=AA667E9-10D3
Date: Thu, 13 Apr 2017 10:33:08 GMT
Call-ID: 7120fc2b8deb3af44a4505b0514b00f5@172.23.1.78
CSeq: 1487300946 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "BCC TEST1" <sip:1201@172.23.1.77>;party=called;screen=yes;privacy=off
Contact: <sip:1201@172.23.1.77:5060>
Server: Cisco-SIPGateway/IOS-15.5.3.S2
Content-Length: 0
*Apr 13 10:33:11.179: //328/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.23.98.4:5060;branch=z9hG4bKBA12AA
From: <sip:8@172.23.98.4>;tag=AA667AF-1530
To: <sip:1201@172.23.23.10>;tag=1837748~8a6cc906-57da-4ec7-813c-f6a08adcaf62-23884583
Date: Thu, 13 Apr 2017 10:27:13 GMT
Call-ID: 6B51E374-1F6B11E7-82A4FE6A-A90FAAC2@172.23.98.4
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence, kpml
Supported: replaces
Server: Cisco-CUCM11.5
Call-Info: <sip:172.23.23.10:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP;x-cisco-qos-tcl=true
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uas
Require: timer
Session-ID: 212fca1b00105000a00094d4690c269e;remote=bd13e3c2a120ab256686c41ab1837748
P-Asserted-Identity: "BCC TEST1" <sip:1201@172.23.23.10>
Remote-Party-ID: "BCC TEST1" <sip:1201@172.23.23.10>;party=called;screen=yes;privacy=off
Contact: <sip:1201@172.23.23.10:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEP94D4690C269E";video
Content-Type: application/sdp
Content-Length: 287
v=0
o=CiscoSystemsCCM-SIP 1837748 1 IN IP4 172.23.23.10
s=SIP Call
c=IN IP4 172.23.18.46
b=TIAS:64000
b=AS:64
t=0 0
m=audio 17980 RTP/AVP 0 101
a=ptime:20
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=trafficclass:conversational.audio.aq:admitted
*Apr 13 10:33:11.182: //328/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:1201@172.23.23.10:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.23.98.4:5060;branch=z9hG4bKBB15C1
From: <sip:8@172.23.98.4>;tag=AA667AF-1530
To: <sip:1201@172.23.23.10>;tag=1837748~8a6cc906-57da-4ec7-813c-f6a08adcaf62-23884583
Date: Thu, 13 Apr 2017 10:33:08 GMT
Call-ID: 6B51E374-1F6B11E7-82A4FE6A-A90FAAC2@172.23.98.4
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0
*Apr 13 10:33:11.186: //327/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.23.1.78:5060;branch=z9hG4bK49452d15a
From: sip:8@172.23.1.78:5060;tag=3a07abf8a0105d1
To: sip:1201@172.23.1.77:5060;tag=AA667E9-10D3
Date: Thu, 13 Apr 2017 10:33:08 GMT
Call-ID: 7120fc2b8deb3af44a4505b0514b00f5@172.23.1.78
CSeq: 1487300946 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "BCC TEST1" <sip:1201@172.23.1.77>;party=called;screen=yes;privacy=off
Contact: <sip:1201@172.23.1.77:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.5.3.S2
Session-Expires: 1800;refresher=uas
Require: timer
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 187
v=0
o=CiscoSystemsSIP-GW-UserAgent 4091 8866 IN IP4 172.23.1.77
s=SIP Call
c=IN IP4 172.23.1.77
t=0 0
m=audio 8244 RTP/AVP 0
c=IN IP4 172.23.1.77
a=rtpmap:0 PCMU/8000
a=ptime:20
*Apr 13 10:33:11.218: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:1201@172.23.1.77:5060 SIP/2.0
Via: SIP/2.0/UDP 172.23.1.78:5060;branch=z9hG4bKebc0a62d1
Max-Forwards: 70
Content-Length: 0
To: sip:1201@172.23.1.77:5060;tag=AA667E9-10D3
From: sip:8@172.23.1.78:5060;tag=3a07abf8a0105d1
Call-ID: 7120fc2b8deb3af44a4505b0514b00f5@172.23.1.78
CSeq: 1487300946 ACK
Contact: sip:8@172.23.1.78:5060
User-Agent: Patton SN4634 3BIS MxSF v3.2.7.44 00A0BA0BE6FE
*Apr 13 10:33:17.875: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:1201@172.23.1.77:5060 SIP/2.0
Via: SIP/2.0/UDP 172.23.1.78:5060;branch=z9hG4bKf4f28c00c
Max-Forwards: 70
Content-Length: 0
To: sip:1201@172.23.1.77:5060;tag=AA667E9-10D3
From: sip:8@172.23.1.78:5060;tag=3a07abf8a0105d1
Call-ID: 7120fc2b8deb3af44a4505b0514b00f5@172.23.1.78
CSeq: 1487300947 BYE
Supported: timer
Supported: replaces
User-Agent: Patton SN4634 3BIS MxSF v3.2.7.44 00A0BA0BE6FE
*Apr 13 10:33:17.878: //327/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.23.1.78:5060;branch=z9hG4bKf4f28c00c
From: sip:8@172.23.1.78:5060;tag=3a07abf8a0105d1
To: sip:1201@172.23.1.77:5060;tag=AA667E9-10D3
Date: Thu, 13 Apr 2017 10:33:17 GMT
Call-ID: 7120fc2b8deb3af44a4505b0514b00f5@172.23.1.78
Server: Cisco-SIPGateway/IOS-15.5.3.S2
CSeq: 1487300947 BYE
Reason: Q.850;cause=16
Content-Length: 0
*Apr 13 10:33:17.879: //328/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:1201@172.23.23.10:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.23.98.4:5060;branch=z9hG4bKBC971
From: <sip:8@172.23.98.4>;tag=AA667AF-1530
To: <sip:1201@172.23.23.10>;tag=1837748~8a6cc906-57da-4ec7-813c-f6a08adcaf62-23884583
Date: Thu, 13 Apr 2017 10:33:08 GMT
Call-ID: 6B51E374-1F6B11E7-82A4FE6A-A90FAAC2@172.23.98.4
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S2
Max-Forwards: 70
Timestamp: 1492079597
CSeq: 102 BYE
Reason: Q.850;cause=16
Content-Length: 0
*Apr 13 10:33:17.884: //328/6B50AA8C829E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.23.98.4:5060;branch=z9hG4bKBC971
From: <sip:8@172.23.98.4>;tag=AA667AF-1530
To: <sip:1201@172.23.23.10>;tag=1837748~8a6cc906-57da-4ec7-813c-f6a08adcaf62-23884583
Date: Thu, 13 Apr 2017 10:27:23 GMT
Call-ID: 6B51E374-1F6B11E7-82A4FE6A-A90FAAC2@172.23.98.4
Server: Cisco-CUCM11.5
CSeq: 102 BYE
Content-Length: 0
this outside to local ,working debug
04-13-2017 03:32 AM
SO, for the outbound call from the IP phone to PSTN, does the call work, is it only that the debugs do not appear but the call works or the call also does not work outbound? In case the outbound call is not working and no debugs appear on the router it would mean that the call is being disconnected on CUCM itself, so you will need to check the CSS on phone has the partition of route pattern and also that route pattern has the correct router in the route list.
HTH
Manish
04-13-2017 03:35 AM
Hi Ozden,
If you are calling from internal extension in CUCM to outside and you do not see any debugs on CUBE, then you are not hitting the CUBE at all.
You need to check in CUCM traces to see whats happening and verify configuration to route calls to CUBE is correct.
HTH
Rajan
04-13-2017 05:28 AM
Hi,
Verify step by step
- Your DN/Device's CSS, does it reach the RP that points to the trunk ?
- The trunk IP (this should be fine since incoming calls work)
- Cube trust address list ?
- Cube source address for SIP process
HTH
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide