Solved: Appending Digits to Dialed Numbers

vgioia5090 · ‎12-16-2008

I have been trying to get my ccme to append 1772(1+area code)on my 7 digit calls but have been unable to get it to work. I ahve included my config, can anyone give me an example of how to make that work?

voice translation-rule 1

rule 1 /9911/ /911/

rule 2 /9411/ /411/

!

voice translation-rule 2

rule 1 /9772+/ /1772/

!

voice translation-rule 3

rule 1 /9+/ /1772/

!

voice translation-rule 4

rule 1 /91+/ /1/

!

voice translation-rule 5

rule 1 /1777250XXXX/ /101/

!

voice translation-rule 7

rule 1 /1../ /1777250XXXX/

!

voice translation-profile CALLCENTRIC_Incoming

translate called 1

!

voice translation-profile Incoming

translate called 5

!

voice translation-profile Local10

translate calling 7

translate called 2

!

voice translation-profile Local7

translate calling 7

translate called 3

!

voice translation-profile LongDistance

translate calling 7

translate called 4

!

voice translation-profile Services

translate calling 7

translate called 1

dial-peer voice 1 voip

translation-profile outgoing services

destination-pattern [49]11

session protocol sipv2

session target dns:callcentric.com

dtmf-relay rtp-nte

codec g711ulaw

!

dial-peer voice 2 voip

translation-profile outgoing Local10

destination-pattern [2-9]......

session protocol sipv2

session target dns:callcentric.com

dtmf-relay rtp-nte

codec g711ulaw

!

dial-peer voice 3 voip

translation-profile outgoing Local7

destination-pattern [2-9]......

session protocol sipv2

session target dns:callcentric.com

incoming called-number .

dtmf-relay rtp-nte

codec g711ulaw

!

dial-peer voice 4 voip

translation-profile outgoing LongDistance

destination-pattern 1[2-9]..[2-9]......

session protocol sipv2

session target dns:callcentric.com

dtmf-relay rtp-nte

codec g711ulaw

Nicholas Matthews · ‎12-16-2008

It's probably because dial peer 2 and 3 are overlapping.

In these cases you really should do something like 'debug voip dialpeer' and make sure you're hitting the right dial peer, along with test voice translation

Delete dial peer 2, and I think this will work.

View solution in original post

Nicholas Matthews · ‎12-16-2008

voice translation-rule 3

rule 1 /9+/ /1772/

If you're trying to add 1772 to a 7 digit number that has a 9 before it, it would look like this:

voice translation-rule 3

rule 1 /^9$.......$$/ /1722\1/

vgioia5090 · ‎12-16-2008

hi, i tried this and it didnt make any difference, did i miss something. would you mind giving an example config? at this time i dont dial a 9 and dont want to. my provider wants the 1772 in front of the number or the calls wont go through. any ideas?

Nicholas Matthews · ‎12-16-2008

This is supposed to be an example.

If you don't have a 9, it would look like this:

voice translation-rule 3

rule 1 /^$.......$$/ /1722\1/

vgioia5090 · ‎12-16-2008

i added this and tried it, but its still not working. i did a debug ccsip calls and it shows the only 7 digits being dialed. any ideas, maybe something else is overiding this entry?

Nicholas Matthews · ‎12-16-2008

It's probably because dial peer 2 and 3 are overlapping.

In these cases you really should do something like 'debug voip dialpeer' and make sure you're hitting the right dial peer, along with test voice translation

Delete dial peer 2, and I think this will work.

vgioia5090 · ‎12-16-2008

awesome thank you! that worked!

Marwan ALshawi · ‎12-16-2008

do the following

voice-translation rule 1

rule 1 /$^9.*$/ /1772\1/

voice translation-profile p1

trnslate called 1

dial-peer voice 2 voip

translation-profile outgoing p1

this will work

also with pots u can use prefix digits

by the way the above will translate any called number start with 9

u can cahne this part based on what number u wanna match

/$^9.*$/

for example

/$^[2-9].+$/ /1772\1/

this will match any number start with any number between 2 to 9 and prepend 1772 to it

good luck

hope this helps