Dial-peer Overlaps

[Leonardo Santana]

Hello,

I have one issue about one implementation

I have CUCM integrated with one PBX.

When i receive the call from PSTN the gateway i receive three digits
Example:

403 is send to gateway and the CUCM prefix 0 inside the H323 Gateway, 0403 because the extension is 4 digit

dial-peer voice 1 pots
description *** Incoming POTS Dial Peer ***
incoming called-number .
direct-inward-dial

dial-peer voice 2 voip
description *** PSTN -> CUCM (Sub) ***
translation-profile outgoing ISDNType
destination-pattern [1-6]..$
session target ipv4:192.168.1.3
incoming called-number .
voice-class codec 1
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

dial-peer voice 3 voip
description *** PSTN -> CUCM (Pub) ***
translation-profile outgoing ISDNType
preference 2
destination-pattern [1-6]..$
session target ipv4:192.168.1.2
voice-class codec 1
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

I have another site with extension 69xx, and from the PBX we need to dial to this site but if i create the dial-peer bellow its conflicts with the dial-peer 2

dial-peer voice 100 voip
description *** PBX -> CUCM (Sub) ***
destination-pattern 69..
session target ipv4:192.168.1.3
incoming called-number .
voice-class codec 1
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

How can i configure this dial-peer without affecting the dial plan at the PBX Side?

Regards

[Chris Deren]

Instead of prefixing 0 on the outbound dial peer prefix it on the inbound dial peer or voice port from the telco company, then adjust the destination-pattern to 0[1-6]..$ on dial peer 2 and 3 and your overlap will be gone.

[Leonardo Santana]

Hello Chris,

Like this:

dial-peer voice 2 voip
description *** PSTN -> CUCM (Sub) ***
translation-profile outgoing ISDNType
destination-pattern 0[1-6]..$
session target ipv4:192.168.1.3
incoming called-number .
voice-class codec 1
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

dial-peer voice 3 voip
description *** PSTN -> CUCM (Pub) ***
translation-profile outgoing ISDNType
preference 2
destination-pattern 0[1-6]..$
session target ipv4:192.168.1.2
voice-class codec 1
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

dial-peer voice 69 voip
description *** PBX -> CUCM (Sub) ***
destination-pattern 69..$
session target ipv4:192.168.1.3
incoming called-number .
voice-class codec 1
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

dial-peer voice 70 voip
description *** PBX -> CUCM (Pub) ***
preference 2
destination-pattern 69..$
session target ipv4:192.168.1.2
voice-class codec 1
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

voice-port 0/0/0:0
translation-profile incoming Incoming
cptone BR

voice translation-rule 50
rule 1 /^[1-6]..$/ /0&/ type any unknown

voice translation-profile Incoming
translate callled 50

[Chris Deren]

More like this:

voice translation-rule 50
rule 1 /^\([1-6]..\)$/ /0\1/ type any unknown

voice translation-profile IncomingProfile
translate callled 50

voice-port 0/0/0:0
translation-profile incoming IncomingProfile
cptone BR

dial-peer voice 2 voip
description *** PSTN -> CUCM (Sub) ***
destination-pattern 0[1-6]..$
session target ipv4:192.168.1.3
incoming called-number .
voice-class codec 1 
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

dial-peer voice 3 voip
description *** PSTN -> CUCM (Pub) ***
preference 2
destination-pattern 0[1-6]..$
session target ipv4:192.168.1.2
voice-class codec 1 
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

dial-peer voice 69 voip
description *** PBX -> CUCM (Sub) ***
destination-pattern 69..$
session target ipv4:192.168.1.3
incoming called-number .
voice-class codec 1 
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

dial-peer voice 70 voip
description *** PBX -> CUCM (Pub) ***
preference 2
destination-pattern 69..$
session target ipv4:192.168.1.2
voice-class codec 1 
voice-class h323 1
dtmf-relay h245-alphanumeric
no vad

[Samuel T Mathai]

yes. this looks works.