We have a special need in which are phones who have different extensions that DIDs coming in should work seeminglessly in SRST as well. When the callmanager is up, it does the translation, but in SRST mode the router should the translation. I was reading on CCO that this feature is supported in SRST but it did not seem to work. Here is the config.
voice translation-rule 10
rule 1 /\(.*\)/ /6590/
voice translation-profile voice
translate called 10
max-conferences 8 gain -6
limit-dn 7940 2
limit-dn 7960 6
ip source-address x.x.x.x port 2000
system message primary Circuit down fallback enabled
system message secondary Fallback Mode
translation-profile outgoing voice
When i run a debug voice translation this is what i get while in SRST mode
When I place the same translation pattern under a dial-peer associated with the PRI port everything works fine,but, I am not sure of this is the right way to do as CCO does have have any example of applying the translation profile under a dialpeer.
Many thanks for the response. Did you try putting the translation pattern under the call-manager-fallback command, just like cisco recommends it. it did not seem to work for me. Here is the URL for a sample config:
You need to apply the translation-profile to the incoming direction of the call. For example
translation-profile incoming voice
This is because from the router's perspective, it is an incoming call to the router (eventhough it is an outgoing call for the IP Phone). Hence you need to use the incoming keyword on the translation-profile.
Can you please explain in detail what exactly you want to achieve.
Cause I was going through your configuration and something doesnt seem right.
In SRST router operates in H323, its not MGCP anymore so if you place the traslation profile in the mgcp dial-peer it is not suppose to work during SRST. In SRST you need to build separate dial-peers without any "application mgcp" commands in there. If you can explain your requirement I can try to set it up in my lab and test.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...