11-21-2012 01:53 AM - edited 03-16-2019 02:18 PM
Here dial-peer for matching outgoing calls WITHOUT translation:
dial-peer voice 9999 voip
destination-pattern 9999
session target ipv4:10.125.0.24
voice-class codec 1
voice-class h323 1
ip qos dscp cs3 signaling
When I run: csim start 9999 - CUCM got 9999
It's OK.
Here dial-peer for matching outgoing calls WITH translation:
voice translation-rule 9000
rule 1 /^00/ //
dial-peer voice 9000 voip
destination-pattern 009...
translate-outgoing called 9000
session target ipv4:10.125.0.24
voice-class codec 1
voice-class h323 1
ip qos dscp cs3 signaling
When I run: csim start 009999 - CUCM got 009999.
It's wrong - must be 9999.
Solved! Go to Solution.
11-21-2012 04:37 AM
Csim does not apply translation profiles at all.
11-21-2012 04:37 AM
Csim does not apply translation profiles at all.
11-21-2012 08:39 AM
Hi Sergey,
To add to Paulo's and Bruno's response, are you sure the correct dialpeer is getting matched?
Also, from the config snips you provided, it doesnt look like you created a voice translation-profile?
Example:
voice translation-rule 9000
rule 1 /^00/ //
voice translation-profile outgoing
translate called 9000
dial-peer voice 9000 voip
destination-pattern 009...
translate-outgoing called outgoing
session target ipv4:10.125.0.24
voice-class codec 1
voice-class h323 1
ip qos dscp cs3 signaling
HTH.
Regards,
Harmit.
11-21-2012 11:28 PM
I use translation-rule.
The correct sintaksis for translation-rule:
dial-peer ...
translate-outgoing called {Rule Number}
For translation-profile:
dial-peer ...
translation-profile outgoing {Profile Name}
All thanks.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: