cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
885
Views
0
Helpful
6
Replies

Cisco IP phone unable to dial (787) area code number. CUCM 12.0.1 ver.

adw8
Level 1
Level 1

Cisco IP phone unable to dial (787) area code number. CUCM version 12.0.1.

787 is PR area code

User tried to dial 81-and then the complete number.

Please advise

1 Accepted Solution

Accepted Solutions

Looks clear enough that you’re not hitting a dial peer. Would you please mind to share the complete running configuration and the output of these two debugs running simultaneously, debug ccsip message and debug voip ccapi inout? Please attach the this as separate files, not as text directly in a response.



Response Signature


View solution in original post

6 Replies 6

b.winter
VIP
VIP

If you cannot dial a number, you need to check the dial-plan in CUCM and also the CSS of the phone / line.

I check through Route Plan report and there is a route plan for 787 area

I did test calls from my phone and checked the cube logs and it showed me 

InternalErrorCode=1.1.128.11.5.0

sh voice iec des 1.1.128.11.5.0
IEC Version: 1
Entity: 1 (Gateway)
Category: 128 (Destination address resolution failure)
Subsystem: 11 (C SCRIPTS)
Error: 5 (No dialpeer match)
Diagnostic Code: 0

Looks clear enough that you’re not hitting a dial peer. Would you please mind to share the complete running configuration and the output of these two debugs running simultaneously, debug ccsip message and debug voip ccapi inout? Please attach the this as separate files, not as text directly in a response.



Response Signature


Yes, you were correct. Any calls made to the 787 area code were not hitting the dial peer groups in the CUBE. The outbound calls were being rejected by "404 Not Found" Error because there is no matching outbound dial-peer on the CUBE for 1787xxxxxxx. There is a dial peer configured on the CUBE for calls to the PSTN which was using e1164 pattern map 2 to route the calls. 

The call that arrives from the CUCM using 1787xxxxxxx and not 81787xxxxxxx.

Fixed the Route pattern error in CUCM which resolved the issue.

Thankyou and Appreciate all your support.

Recommend you to use DNA to see what the number analysis in CM states when making the call to the number.



Response Signature