Wildcard in Dial-peer, not being read

[livi9003]

Is there any reason why the (.) wildcard would network on a CME?

I get a fast busy after the 4. If I change the dial-peer to 2541... I get the fast busy after the 1

dial-peer voice 1 voip
description OUTbound to CUCM
destination-pattern 254....
session protocol sipv2
session target ipv4:148.x..zzz
voice-class sip bind control source-interface GigabitEthernet0/0/0.59
voice-class sip bind media source-interface GigabitEthernet0/0/0.59
dtmf-relay rtp-nte
codec g711ulaw
no vad

[Spooster IT Services]

Hello @livi9003, they are working good for me on more than 100s of CME deployed.

1. What IOS version you are running on CME? Try upgrading to the Cisco recommended version if not already.

2. Collect the following debugs and see what is happening.

debug ccsip messages

debug voip ccapi inout 

***Please rate all helpful posts***

[Nithin Eluvathingal]

What setup is this, you said its  a CME, but the dial peer description says Oubound to CUCM, Your session target start with a public IP range.

[VON CLAWSON]

I agree with Spooster above. You need to get the output from

debug ccsip messages

debug voip ccapi inout 

and post it here. We should be able to help you figure out what is happening. Also, is this an inbound or outbound call?

[livi9003 · Accepted solution]

Looks like updating the iOS fixed the issue.

Thanks

[Nithin Eluvathingal]

Out of Curiosity what version of CME was this and to which version did you upgraded ?