Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

ILBC Codec issue

Hi ALL

 

We have 3 sites . I have 2 X cisco cluster v 9.0  and one remote CME. Our solution to do intercluster using SIP trunk between 2X cluster + one remote CME using CUBE. My problem that i am trying to use ilbc codec but i am enable to see codec and got call fails . for information as below:-

1- cluster A                   ext:4XXX

2-Cluster B                  ext:5XXX

3-SiteC Remote CUCME   ext: 6XXX

 

When i dial a call from 4XXX to 5XXX the call ring and connected sometimes and some time call dropped but shows me codec g729 when connected . when i dial  from 6XXX to 4XXX or 5XXX call is ringing but when i tried to answer i got fast busy tone.

*on CUCM clusters , i configured regions to use ILBC codec and assign it to Device pool which is used under SIP trunk to my CUBE..

*Same on SiteC i used

voice class codec 1

codec preference 1 ilbc

video codec h264

*on my CUBE i used codec transparent .

dila-peer voice 2000 voip
destination-pattern 2...
sesion target ipv4:X.X.X.X
dtmf-relay rtp-nte
codec trasnparent
incoming called-number 2...
seesion protocl sipv2
no vad

--------------------------------------------------------------------------------------------------------

Site A to Site B

 

Jul 19 02:47:11.921: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
INVITE sip:3001@142.102.64.254:5060 SIP/2.0
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK637e13f0f
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=131~975fe57b-1bdc-4d18-9107-3613d98b733a-19352256
To: <sip:3001@142.102.64.254>
Date: Sat, 19 Jul 2014 02:47:11 GMT
Call-ID: fa22e700-3c91dc2f-59-b40648e@142.100.64.11
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:142.100.64.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 4196591360-0000065536-0000000033-0188769422
Session-Expires:  1800
P-Asserted-Identity: "HQ Phone 1" <sip:2001@142.100.64.11>
Remote-Party-ID: "HQ Phone 1" <sip:2001@142.100.64.11>;party=calling;screen=yes;privacy=off
Contact: <sip:2001@142.100.64.11:5060;transport=tcp>
Max-Forwards: 70
Content-Length: 0


Jul 19 02:47:11.929: //93/FA22E7000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:3001@142.100.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 142.211.64.1:5060;branch=z9hG4bK38BFB
Remote-Party-ID: "HQ Phone 1" <sip:2001@142.211.64.1>;party=calling;screen=yes;privacy=off
From: "HQ Phone 1" <sip:2001@142.211.64.1>;tag=1C33BA0-1427
To: <sip:3001@142.100.65.11>
Date: Sat, 19 Jul 2014 02:47:11 GMT
Call-ID: D17EF6C5-E2511E4-80E2EBFA-E1B87722@142.211.64.1
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 4196591360-0000065536-0000000033-0188769422
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M2
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1405738031
Contact: <sip:2001@142.211.64.1:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires:  1800
Content-Length: 0


Jul 19 02:47:11.929: //92/FA22E7000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK637e13f0f
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=131~975fe57b-1bdc-4d18-9107-3613d98b733a-19352256
To: <sip:3001@142.102.64.254>
Date: Sat, 19 Jul 2014 02:47:11 GMT
Call-ID: fa22e700-3c91dc2f-59-b40648e@142.100.64.11
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Content-Length: 0


Jul 19 02:47:11.941: //93/FA22E7000000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 142.211.64.1:5060;branch=z9hG4bK38BFB
From: "HQ Phone 1" <sip:2001@142.211.64.1>;tag=1C33BA0-1427
To: <sip:3001@142.100.65.11>
Date: Sat, 19 Jul 2014 02:47:11 GMT
Call-ID: D17EF6C5-E2511E4-80E2EBFA-E1B87722@142.211.64.1
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0


Jul 19 02:47:11.945: //93/FA22E7000000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 142.211.64.1:5060;branch=z9hG4bK38BFB
From: "HQ Phone 1" <sip:2001@142.211.64.1>;tag=1C33BA0-1427
To: <sip:3001@142.100.65.11>;tag=113375252
Date: Sat, 19 Jul 2014 02:47:11 GMT
Call-ID: D17EF6C5-E2511E4-80E2EBFA-E1B87722@142.211.64.1
CSeq: 101 INVITE
Allow-Events: presence
Warning: 399 SB-PUB "Unable to find a device handler for the request received on port 59406 from 142.211.64.1"
Content-Length: 0


Jul 19 02:47:11.945: //92/FA22E7000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK637e13f0f
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=131~975fe57b-1bdc-4d18-9107-3613d98b733a-19352256
To: <sip:3001@142.102.64.254>;tag=1C33BB0-1DC6
Date: Sat, 19 Jul 2014 02:47:11 GMT
Call-ID: fa22e700-3c91dc2f-59-b40648e@142.100.64.11
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Reason: Q.850;cause=63
Content-Length: 0


Jul 19 02:47:11.945: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent: 
ACK sip:3001@142.100.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 142.211.64.1:5060;branch=z9hG4bK38BFB
From: "HQ Phone 1" <sip:2001@142.211.64.1>;tag=1C33BA0-1427
To: <sip:3001@142.100.65.11>;tag=113375252
Date: Sat, 19 Jul 2014 02:47:11 GMT
Call-ID: D17EF6C5-E2511E4-80E2EBFA-E1B87722@142.211.64.1
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


Jul 19 02:47:11.953: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
ACK sip:3001@142.102.64.254:5060 SIP/2.0
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK637e13f0f
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=131~975fe57b-1bdc-4d18-9107-3613d98b733a-19352256
To: <sip:3001@142.102.64.254>;tag=1C33BB0-1DC6
Date: Sat, 19 Jul 2014 02:47:11 GMT
Call-ID: fa22e700-3c91dc2f-59-b40648e@142.100.64.11
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0

 

-------------------------------------------------------------------------------------------------------------------

Site A to Site C


Jul 19 02:48:12.557: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
INVITE sip:4003@142.102.64.254:5060 SIP/2.0
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK66f65023e
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=134~975fe57b-1bdc-4d18-9107-3613d98b733a-19352258
To: <sip:4003@142.102.64.254>
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: 1e7ec380-3c91dc6c-5c-b40648e@142.100.64.11
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:142.100.64.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 0511624064-0000065536-0000000034-0188769422
Session-Expires:  1800
P-Asserted-Identity: "HQ Phone 1" <sip:2001@142.100.64.11>
Remote-Party-ID: "HQ Phone 1" <sip:2001@142.100.64.11>;party=calling;screen=yes;privacy=off
Contact: <sip:2001@142.100.64.11:5060;transport=tcp>
Max-Forwards: 70
Content-Length: 0


Jul 19 02:48:12.565: //95/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:4003@142.102.66.254:5060 SIP/2.0
Via: SIP/2.0/UDP 142.222.64.1:5060;branch=z9hG4bK3924D8
Remote-Party-ID: "HQ Phone 1" <sip:2001@142.222.64.1>;party=calling;screen=yes;privacy=off
From: "HQ Phone 1" <sip:2001@142.222.64.1>;tag=1C42878-2479
To: <sip:4003@142.102.66.254>
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: F5A2AD29-E2511E4-80E8EBFA-E1B87722@142.222.64.1
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 0511624064-0000065536-0000000034-0188769422
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M2
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1405738092
Contact: <sip:2001@142.222.64.1:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires:  1800
Content-Length: 0


Jul 19 02:48:12.565: //94/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK66f65023e
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=134~975fe57b-1bdc-4d18-9107-3613d98b733a-19352258
To: <sip:4003@142.102.64.254>
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: 1e7ec380-3c91dc6c-5c-b40648e@142.100.64.11
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Content-Length: 0


Jul 19 02:48:12.589: //95/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 142.222.64.1:5060;branch=z9hG4bK3924D8
From: "HQ Phone 1" <sip:2001@142.222.64.1>;tag=1C42878-2479
To: <sip:4003@142.102.66.254>
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: F5A2AD29-E2511E4-80E8EBFA-E1B87722@142.222.64.1
Timestamp: 1405738092
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.3.3.M2
Content-Length: 0


Jul 19 02:48:12.593: //95/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 142.222.64.1:5060;branch=z9hG4bK3924D8
From: "HQ Phone 1" <sip:2001@142.222.64.1>;tag=1C42878-2479
To: <sip:4003@142.102.66.254>;tag=1C56A90-2346
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: F5A2AD29-E2511E4-80E8EBFA-E1B87722@142.222.64.1
Timestamp: 1405738092
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:4003@142.102.66.254>;party=called;screen=no;privacy=off
Contact: <sip:4003@142.102.66.254:5060>
Server: Cisco-SIPGateway/IOS-15.3.3.M2
Content-Length: 0


Jul 19 02:48:12.597: //94/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK66f65023e
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=134~975fe57b-1bdc-4d18-9107-3613d98b733a-19352258
To: <sip:4003@142.102.64.254>;tag=1C4289C-105
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: 1e7ec380-3c91dc6c-5c-b40648e@142.100.64.11
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:4003@142.100.64.254>;party=called;screen=no;privacy=off
Contact: <sip:4003@142.100.64.254:5060;transport=tcp>
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Content-Length: 0


Jul 19 02:48:17.069: //95/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 142.222.64.1:5060;branch=z9hG4bK3924D8
From: "HQ Phone 1" <sip:2001@142.222.64.1>;tag=1C42878-2479
To: <sip:4003@142.102.66.254>;tag=1C56A90-2346
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: F5A2AD29-E2511E4-80E8EBFA-E1B87722@142.222.64.1
Timestamp: 1405738092
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:4003@142.102.66.254>;party=called;screen=no;privacy=off
Contact: <sip:4003@142.102.66.254:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.3.3.M2
Require: timer
Session-Expires:  1800;refresher=uac
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 292

v=0
o=CiscoSystemsSIP-GW-UserAgent 8705 4796 IN IP4 142.102.66.254
s=SIP Call
c=IN IP4 142.102.66.254
t=0 0
m=audio 16448 RTP/AVP 116 101
c=IN IP4 142.102.66.254
a=rtpmap:116 iLBC/8000
a=fmtp:116 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:20

Jul 19 02:48:17.073: //94/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK66f65023e
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=134~975fe57b-1bdc-4d18-9107-3613d98b733a-19352258
To: <sip:4003@142.102.64.254>;tag=1C4289C-105
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: 1e7ec380-3c91dc6c-5c-b40648e@142.100.64.11
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:4003@142.100.64.254>;party=called;screen=no;privacy=off
Contact: <sip:4003@142.100.64.254:5060;transport=tcp>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Session-Expires:  1800;refresher=uac
Require: timer
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 283

v=0
o=CiscoSystemsSIP-GW-UserAgent 4486 2843 IN IP4 142.100.64.254
s=SIP Call
c=IN IP4 142.100.64.254
t=0 0
m=audio 16480 RTP/AVP 116 101
c=IN IP4 142.100.64.254
a=rtpmap:116 iLBC/8000
a=fmtp:116 
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:0
a=maxptime:0

Jul 19 02:48:17.093: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
ACK sip:4003@142.100.64.254:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK67e52d24a
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=134~975fe57b-1bdc-4d18-9107-3613d98b733a-19352258
To: <sip:4003@142.102.64.254>;tag=1C4289C-105
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: 1e7ec380-3c91dc6c-5c-b40648e@142.100.64.11
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0


Jul 19 02:48:17.097: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
BYE sip:4003@142.100.64.254:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 142.100.64.11:5060;branch=z9hG4bK683d77233f
From: "HQ Phone 1" <sip:2001@142.100.64.11>;tag=134~975fe57b-1bdc-4d18-9107-3613d98b733a-19352258
To: <sip:4003@142.102.64.254>;tag=1C4289C-105
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: 1e7ec380-3c91dc6c-5c-b40648e@142.100.64.11
User-Agent: Cisco-CUCM9.1
Max-Forwards: 70
P-Asserted-Identity: "HQ Phone 1" <sip:2001@142.100.64.11>
CSeq: 102 BYE
Reason: Q.850;cause=47
Content-Length: 0


Jul 19 02:48:17.101: //95/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
ACK sip:4003@142.102.66.254:5060 SIP/2.0
Via: SIP/2.0/UDP 142.222.64.1:5060;branch=z9hG4bK3B142F
From: "HQ Phone 1" <sip:2001@142.222.64.1>;tag=1C42878-2479
To: <sip:4003@142.102.66.254>;tag=1C56A90-2346
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: F5A2AD29-E2511E4-80E8EBFA-E1B87722@142.222.64.1
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Reason: Q.850;cause=96
Content-Length: 0


Jul 19 02:48:17.101: //95/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
BYE sip:4003@142.102.66.254:5060 SIP/2.0
Via: SIP/2.0/UDP 142.222.64.1:5060;branch=z9hG4bK3C18AC
From: "HQ Phone 1" <sip:2001@142.222.64.1>;tag=1C42878-2479
To: <sip:4003@142.102.66.254>;tag=1C56A90-2346
Date: Sat, 19 Jul 2014 02:48:12 GMT
Call-ID: F5A2AD29-E2511E4-80E8EBFA-E1B87722@142.222.64.1
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M2
Max-Forwards: 70
Timestamp: 1405738097
CSeq: 102 BYE
Reason: Q.850;cause=96
P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0,JI=0,LA=0,DU=0
Content-Length: 0


Jul 19 02:48:17.113: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
BYE sip:2001@142.222.64.1:5060 SIP/2.0
Via: SIP/2.0/UDP 142.102.66.254:5060;branch=z9hG4bK2415EF
From: <sip:4003@142.102.66.254>;tag=1C56A90-2346
To: "HQ Phone 1" <sip:2001@142.222.64.1>;tag=1C42878-2479
Date: Sat, 19 Jul 2014 02:48:17 GMT
Call-ID: F5A2AD29-E2511E4-80E8EBFA-E1B87722@142.222.64.1
User-Agent: Cisco-SIPGateway/IOS-15.3.3.M2
Max-Forwards: 70
Timestamp: 1405738097
CSeq: 101 BYE
Reason: Q.850;cause=86
P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0,JI=0,LA=0,DU=0
Content-Length: 0


Jul 19 02:48:17.113: //95/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 142.102.66.254:5060;branch=z9hG4bK2415EF
From: <sip:4003@142.102.66.254>;tag=1C56A90-2346
To: "HQ Phone 1" <sip:2001@142.222.64.1>;tag=1C42878-2479
Date: Sat, 19 Jul 2014 02:48:17 GMT
Call-ID: F5A2AD29-E2511E4-80E8EBFA-E1B87722@142.222.64.1
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Timestamp: 1405738097
CSeq: 101 BYE
P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0,JI=0,LA=0,DU=0
Content-Length: 0


Jul 19 02:48:17.121: //95/1E7EC3800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 142.222.64.1:5060;branch=z9hG4bK3C18AC
From: "HQ Phone 1" <sip:2001@142.222.64.1>;tag=1C42878-2479
To: <sip:4003@142.102.66.254>;tag=1C56A90-2346
Date: Sat, 19 Jul 2014 02:48:17 GMT
Call-ID: F5A2AD29-E2511E4-80E8EBFA-E1B87722@142.222.64.1
Server: Cisco-SIPGateway/IOS-15.3.3.M2
Timestamp: 1405738097
CSeq: 102 BYE
Reason: Q.850;cause=96
P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0,JI=0,LA=0,DU=0
Content-Length: 0

Any help.

 

thanks

5 REPLIES
Cisco Employee

Hi,It seems that are running

Hi,

It seems that are running into two different issues for these two different call flows.

When calling from Site A to Site B, we are getting the error 503 Service Unavailable with Warning: 399 SB-PUB "Unable to find a device handler for the request received on port 59406 from 142.211.64.1"
Check if you have a bind command added to the running config for the sip signalling and it should be binded to the interface which is specified in the destination's IP address of the call manager on Site B.
If you have mulitple interfaces, please add the bind command under the dial peer towards Site B cucm.


For the issue with calling from Site A to site C, we see that OK was received with iLBC codec from Site C. However, Site A responded back with a BYE with reason code 47.

Can you please share call manager traces for the same with the calling and called party details?
Also check if the phone that you are using on site A supports iLBC codec as a part of its caps.


HTH,
Jagpreet Singh Barmi

HI+5 for Jagpret  , really

HI

+5 for Jagpret  , really what a great explanation!. Kindly find the below:-

1- Check the phone model , not all phones support ilbc , for example like 7960 or 7961 not support .

2- Kindly go to cucm - service parameters "search for audio" then 

Default inter region MAX audio Bit rate: 16 KBPS (ILBC,G728).

3-Configure new region "Reg_ILBC".

ILBC -ILBC                             MAX audio bit rate:16 KBPS (ilbc,G728)

ILBC_-Default                       MAX audio bit rate:16 KBPS (ilbc,G728)

 

 

Thanks

please rate all useful information

 

Thanks

please rate all useful information 

New Member

helloyes my phones 7960 ,7961

hello

yes my phones 7960 ,7961 and 7945 .which phones are supported ILBC codec to put in our plan?.I think the problem from the phone types.

 

Thanks

Cisco Employee

Hi, As mentioned by Islam

Hi,

 

As mentioned by Islam.Kamal, Cisco 7960 and 7961 do not support iLBC codec. However, 7945 should support iLBC. Please test with Cisco 7945 phones.

 

You can visit the following thread with the list of phones and supporting codec. This thread is quite old, so please refer the latest datasheet of the model to get the current codec support. However, it should give you an good overview.

https://supportforums.cisco.com/discussion/10486016/what-ip-phone-models-support-ilbc-codec

 

In case the issue is still experienced, please provide CM traces for a test call using the following steps.

https://supportforums.cisco.com/document/126666/collecting-cucm-traces-cucm-862-tac-sr

Also provide the status of the other issue (calling from site A to site B), throwing 503 service unavailable message.

 

HTH,

Jagpreet Singh Barmi

 

 

Add voice-class sip pass

Add voice-class sip pass-through  content spd to your Dila-peers pointing to CUCM's and try

274
Views
15
Helpful
5
Replies
CreatePlease login to create content