Question when configuring translation in VoIP Gateway

[sethplate10]

I had the carrier send me the last 2 digits of our DID numbers.Although we are not using a Gatekeeper, a guy before me configuredthe VoIP Port with a tech-prefix 68.

At present I am doing translation in the CallManager, translating 68XX to 779XX.

1) I would like to do the translation in the VoIP

Gateway, is this possible?

2) Can you suggest any sample translation

configuration ?

3) If I do the translation in the VoIP Gateway

router, do I need to do any configuration in the

Router so that the DID number for each IP Phone

will be displayed instead of the representative

number ?

Please advise.

Note :

VoIP Gateway : Cisco 1700

IOS Version : Version 12.3(4)T8

CallManager Version : 3.3.3

Thanks

[nmilojevic · Accepted solution]

Hi!

Well, you can configure prefix 779 instead of 68.

Or, you can try this:

-turn off tech prefix 68

-enable voice translation profile on incoming (POTS) dial-peer:

translation-profile incoming example1

-create profile and rule:

conf t

voice translation-profile example1

translate called 100

voice translation-rule 100

rule 1 /^/ /779/

This should do the trick. If you want, you can also do it on the outgoing (VoIP) peer. As for your question number 3, I really don't know, what will come up on the IP phone.

Regards,

Nikola

[sethplate10]

Thanks Nikola. I really appreciate it.

Bsically the wild cards you used meant to put 779 at the beginning of the received digits from the carrier right ?

rule 1 /^/ /779/

Thanks.

[nmilojevic]

Correct.

Have a look at this documents, once you get a grip, it is a powerfull tool.

There are two sets of translation rules - old and new.

Old rules are simple and don't allow wildcards;

http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a0080080aec.html#wp1244453

New rules (profiles) are more powerfull;

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a0080325e8e.shtml

Regards,

Nikola

[mcotrone]

It depends on what kind of gateway signaling is currently being used between your 1700 and the CCM. Are you using MGCP or H323? If you are using H.323 then the MOST easiest way to manipulate your digits is by use of either the num-exp command or translation patterns. There is no need to use a tech prefix when you aren't using a gatekeeper by the way. See example:

!

num-exp 68.. 779,,

The only thing I hate about the Num-exp command is that is it bi-directional. Some people may only wnat to xlate in one direction. I prefer the translation patterns since you have control on a per call leg scenario.

!

voice class codec 1

codec preference 1 g711ulaw

codec preference 2 g729br8

!

translation-rule 1

Rule 1 68 779

!

dial-peer voice 199 voip

desintation-pattern 68..

session target ipv4:10.1.1.1 (ex IP)

translate-outgoing called 1

preference 0 <-- Use if you are going to have more than one DP pointing to other CCM's

voice-class codec 1 <-- If you don't specify then G729 is used

Now anything that hits Dialpeer 199 starting with 68 will then be translated to 799.

You can test this config with the global "test translation-rule 1 682323" and you will see "7792323"

Just make sure that the Call Manager is looking for the digits starting with 779 now instead of 68.

Does this help?

Mike

[nmilojevic]

Mike,

I am affraid the guy before him configured tech-prefix ON the outgoing voip dial-peer, so with the "destination-pattern 68.." he won't catch calls on this same peer.

Regards,

Nikola

[mcotrone · Accepted solution]

Right, I would un-configure the tech-prefix since it is not a good place to use it outside of RAS.

Mike

(BUT ALWAYS TRY THIS OFFLINE FIRST SO YOU DON"T TAKE DOWN YOUR PRODUCTION NETWORK) :)

Mike

[sethplate10]

Thank you for your help, I learned a lot!

Best Regards

[mcotrone]

Anytime.