01-24-2013 09:38 AM - edited 03-16-2019 03:21 PM
A CME running 9.1 has a number of 79xx IP phones and some SCCP 8945 IP phones. For some reason the 8945 phones cannot dial international numbers. There is no COR configured on any of the phones or extensions. The dial-peer is as follows;
dial-peer voice 32 pots
trunkgroup ALL_T1E1
corlist outgoing call-International
description International
translation-profile outgoing PSTN_ACCESS_DIGIT_PROFILE
destination-pattern 900[1-9]T
forward-digits all
!
Can't think there's any problem with the dial-peer as all the 79xx IP phones work fine. Does anyone know of any issues with the 8945s on CME that might explain this?
Thanks.
Solved! Go to Solution.
01-25-2013 04:45 AM
Hi
A common fix for this issue is to apply 'bearer-cap speech' as per this example (for CUVA, but it's possibly the same issue as I think those phones are video capable):
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080569b65.shtml
Regards
Aaron
01-24-2013 09:56 AM
I am not aware of anything specific to the 8945 that would cause this type of issue. Maybe someone else has a nugget on this one. In lieu of that, can you provide a more robust description of what you mean by "8945 phones cannot dial international numbers"? What are the visual and audio cues that coincide with the issue.
Also, can you provide output from debug isdn q931 when you place the call from a 8945?
Can you post config for
ephone: known good 79xx phone
ephone: bad 8945
ephone-dn: known good 79xx phone extension
ephone: bad 8945 phone extension
-Bill
Please remember to rate helpful responses and identify
01-25-2013 01:18 AM
Thanks for your reply Bill. Here's the config you requested (I've removed speed-dials and snr info) - as you can see there's really nothing out of the ordinary. I'll capture the isdn debug as soon as I can and post it if I can't spot anything myself. Thanks.
ephone-dn 18 dual-line
number 2088
pickup-group 1
label Peter
description Peter
name Peter
call-forward busy 2980
call-forward noan 2980 timeout 15
hold-alert 30 originator
!
ephone-dn 27 dual-line
number 2101
pickup-group 1
label Mohamed
description Mohamed
call-forward busy 2980
call-forward noan 2980 timeout 15
hold-alert 30 originator
!
ephone 18
device-security-mode none
video
mac-address 0023.5E1A.7EC0
ephone-template 2
username "PL"
paging-dn 442
type 7975
missed-calls all
button 1:18
!
ephone 27
device-security-mode none
video
mac-address 203A.0782.3CF9
ephone-template 2
username "MB3"
type 8945
missed-calls all
button 1c27,227
!
01-25-2013 04:33 AM
Here also is some Q931 output - the first 2 are failed calls from the 8945, the last one is successful from an 8961 SIP phone and I can confirm that output from a 79xx phone is successful and looks the same. I notice the output from the 8945 shows 'Transfer Capability = Unrestricted Digital' and 'Interface=0xB9178E8, Progress Indication=NULL(0)'.
031868: Jan 25 11:40:28.329: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x086F
Bearer Capability i = 0x8890
Standard = CCITT
Transfer Capability = Unrestricted Digital
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98383
Exclusive, Channel 3
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0180, '00180'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '009611826900'
Plan:ISDN, Type:Unknown
031869: Jan 25 11:40:28.521: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x886F
Channel ID i = 0xA98383
Exclusive, Channel 3
Interface=0xB9178E8, Progress Indication=NULL(0)
031873: Jan 25 11:40:28.541: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x886F
Cause i = 0x8281 - Unallocated/unassigned number
032162: Jan 25 11:40:50.829: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0870
Bearer Capability i = 0x8890
Standard = CCITT
Transfer Capability = Unrestricted Digital
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98385
Exclusive, Channel 5
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0180, '00180'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '009611826900'
Plan:ISDN, Type:Unknown
032163: Jan 25 11:40:51.017: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8870
Channel ID i = 0xA98385
Exclusive, Channel 5
Interface=0xB9178E8, Progress Indication=NULL(0)
032167: Jan 25 11:40:51.037: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x8870
Cause i = 0x8281 - Unallocated/unassigned number
032611: Jan 25 11:42:11.525: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0872
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98384
Exclusive, Channel 4
Calling Party Number i = 0x0181, '00180'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '009611826900'
Plan:ISDN, Type:Unknown
032612: Jan 25 11:42:11.741: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x8872
Channel ID i = 0xA98384
Exclusive, Channel 4
Progress Ind i = 0x8288 - In-band info or appropriate now available
032653: Jan 25 11:42:22.037: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x8872
Progress Ind i = 0x8488 - In-band info or appropriate now available
Progress Ind i = 0x8482 - Destination address is non-ISDN
032661: Jan 25 11:42:28.733: ISDN Se0/0/0:15 Q931: RX <- CONNECT pd = 8 callref = 0x8872
Connected Number i = '0', 0xC3
032662: Jan 25 11:42:28.733: ISDN Se0/0/0:15 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0872
01-25-2013 04:45 AM
Hi
A common fix for this issue is to apply 'bearer-cap speech' as per this example (for CUVA, but it's possibly the same issue as I think those phones are video capable):
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080569b65.shtml
Regards
Aaron
01-25-2013 04:50 AM
I was just searching for 'Transfer Capability = Unrestricted Digital' and found the same Tech Note, have just applied bearer-cap speech to the ISDN interface and am waiting for the end-user to test, but thank you for your prompt suggestion Aaron, hopefully that wil do the trick. The really annoying thing is, bearer-cap speech is part of my standard config, for some reason I've missed it off in this case.
Thanks again to Aaron & Bill both for your assistance in this matter, much appreciated.
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