We want to route a fax ph# over our PTP into a right fax server. My question is, is this ok to do? Any concerns or things to watch out for? Here is the dial peer Im going to use (keep in mind this is a fax dial-peer)
Thanks for the help. One last question. I've noticed that this first number I'm trying to route is already in use on that network, so I assume I have to translate it. I looked on my GW and there was already a translation rule setup
voice translation-rule 1
rule 1 /^193[0-7]$/ /8517/
rule 2 /^688[1-9]$/ /8517/
rule 3 /^689[0-9]$/ /8517/
rule 4 /^6990$/ /8517/
rule 5 /^191[0-2,5,9]$/ /8517/
rule 6 /^8518$/ /8517/
rule 7 /^852[3,6]$/ /8517/
rule 8 /^1909$/ /8517/
rule 9 /^6610$/ /8610/ <<<<<<< (Number i'm trying to translate)
Then I created a dial peer 8610, but I don't see it hitting this dialpeer I see it hitting a default dialpeer and it's not getting translated?????? Here is my dialpeer
The router will match the call to the peer, then do translations. So you need a peer with a 6610 destination, then the far end will get a call setup for called number 8610.
One other minor point that probably won't cause a problem. You probably don't need the incoming called-number statement in your VOIP peer. That would only apply to inbound voip calls. By default, inbound calls with a calling number matching the VOIP peer destination will match. If you do need to match on inbound called number this should be the number sent (before any translation).
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...