05-14-2019 02:28 PM
Recently we have added toll-free from our SIP provider and they are giving us steering digits '00000' to differentiate from normal voice calls. As such I'm trying to strip off the digits at our CUBE so our CUCM can handle appropriately.
Have a 2901 running CUBE with version 15.4(3)M4. I've written a translation-rule to strip these steering digits:
!
voice translation-rule 1
rule 1 /^00000\(..........\)/ /\1/
!
voice translation-profile toll-free-with-steering
translate called 1
!
Testing this, it works fine:
test voice translation-rule 1 000008001234567
Matched with rule 1
Original number: 000008001234567 Translated number: 8001234567
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none
If I try the same rule on a 4331 CUBE with version 15.5(3)S2, it loses part of the string after entering into config prompt. If look at in the running-config:
rule 1 /^00000\(..........\)/ /\1/
Becomes:
rule 1 /^00000\(..........\)/ /1/ <---missing \
And the translation rule does not match at all anymore (first part won't function).
test voice translation-rule 1 000008001234567
000008001234567 Didn't match with any of rules
A very basic match rule for example will work on our 4331 cube:
rule 1 /000008001234567/ /8001234567/
But this isn't very extensible as I would need to build a rule per number. Is there are different way to configure translation rules between these platforms?
Solved! Go to Solution.
05-15-2019 12:36 AM
05-14-2019 06:16 PM
That has to be a bug. I have the character group references in many translation rules on IOS XE without issue. I’m staring at one right now on 16.6(3) for example.
05-14-2019 11:04 PM
I would agree with Jonathan, this may be a bug. Have you tried to upgrade the IOS on your CUBE?
G
05-15-2019 12:36 AM
05-17-2019 01:02 PM
I moved the 4331 to "Cisco IOS Software [Everest], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 16.6.6, RELEASE SOFTWARE (fc1)" and it still has the issue of not accepting the character into the running-config, it just strips it out and so the translation won't work.
The workaround I'm going to consider my solution. It does appear to be a bug, but the following Haris provided works fine for me, the steering digits are properly stripped:
voice translation-rule 1
rule 1 /^00000/ //
Thank you!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide