• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 285
  • Last Modified:

Can't get my CME dial-peers right

Experts, no matter what I do, I can't seem to lock down the correct configuration for my CME dial-peers.

I have the following setup:
     SIP Provider --> Cisco 2801 CME --> CUCM

I have the CUCM configured perfectly.  The problem is with the CME dial-peers.  No matter how hard I try, I can't get the thing to send everything the way it's supposed to go.

dial-peer voice 5000 voip
 description CUCM Trunk
 destination-pattern [1-5]...
 session target ipv4:1.1.1.1
 dtmf-relay h245-alphanumeric h245-signal rtp-nte
 codec g711ulaw
 no vad
dial-peer voice 99 voip
 description Outbound SIP
 translation-profile outgoing SIP_Outbound
 destination-pattern 99.T
 voice-class codec 1
 session protocol sipv2
 session target dns:<SIP Provider>
 incoming called-number ....
 dtmf-relay rtp-nte
 no vad
dial-peer voice 100 voip
 description Inbound SIP
 translation-profile incoming SIP_Inbound
 session protocol sipv2

voice translation-rule 1
 rule 1 /^.*/ /<SIP Phone #>/
voice translation-rule 2
 rule 1 /^.*/ /5555/
voice translation-rule 3
 rule 1 /^99\(.......\)$/ /1<Area Code>\1/
 rule 2 /^99\(..........\)$/ /1\1/
 rule 3 /^99\(.*\)/ /\1/
voice translation-profile SIP_Inbound
 translate called 2
voice translation-profile SIP_Outbound
 translate calling 1
 translate called 3

Open in new window


Basically, I just want the thing to grab all calls from the SIP provider, and force it down the CUCM trunk (# 5555).   And vice-versa, taking all CUCM originated calls (prefaced by 99) and shoot them out to the SIP provider [stripping 99 of course]

Debugging the dial-peer, It's looking as my inbound calls get shot right back out the same dial-peer they came in on.

Can somebody please hit me where I'm going wrong here?  Thanks.
0
usslindstrom
Asked:
usslindstrom
1 Solution
 
agonza07Commented:
Your "incoming called number ." needs to be on your 100 dial peer.
0
 
usslindstromAuthor Commented:
That was it.  Thanks.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now