I had a config with a bunch of E164-formatted numbers that were matched after translation, and I couldn't get them to match until I put a $ at the end of the string. So try changing the dial-peer to "destination-pattern +4412345678$"
Let us know what happens.
Maren
-----------------
Just for reference, I am including one of my all time favorite graphics from a Cisco class with the order of operations on digit manipulation on a router. I have this posted in my office for reference and look at it anytime I'm thinking about the topic.
Not very likely, but it could be because you use the same dial peer as inbound as you use for outbound. I would recommend you to split it into two dial peers with something like this.
dial-peer voice 1 voip
description IN: CUCM
incoming uri via 1
no destination-pattern .T
translation-profile incoming TP-ToE164
session protocol sipv2
no session server-group 1
voice-class codec 1
no voice-class sip options-keepalive profile 1
voice-class sip bind control source-interface Loopback1
voice-class sip bind media source-interface Loopback1
dtmf-relay rtp-nte sip-kpml
no vad
!
dial-peer voice 2 voip
description OUT: CUCM
destination-pattern +T
session protocol sipv2
session server-group 1
voice-class codec 1
voice-class sip options-keepalive profile 1
voice-class sip bind control source-interface Loopback1
voice-class sip bind media source-interface Loopback1
dtmf-relay rtp-nte sip-kpml
no vad
In general it’s a bad idea to use .T as a match on a dial peer as that opens up for call loop situations and that should be avoided at all cost. Can you not be a little more specific in the destination pattern towards CM? For example use an e164 dial plan map instead of a destination pattern on the dial peer as that gives you a better option to be more specific and have multiple different destinations.
Saw that after my post. However I still recommend to not use the same DP for both directions, it's a messy thing to do IMHO.
The error message you get seems to match this post. https://community.cisco.com/t5/ip-telephony-and-phones/as5350xm-voice-gateway-error-message/td-p/747708
Also this defect seems to match what you see. https://quickview.cloudapps.cisco.com/quickview/bug/CSCva30873
To get a little bit more detailed information can you please enable these debugs.
- debug ccsip message
- debug voip ccapi inout
- debug voip translation
- debug isdn q931
