![]() This can reduce the number of required translation rules and the time it takes to write them.Īssociating one or more translation rules with an Enterprise Voice trunk configuration should be used as an alternative to configuring translation rules on the trunk peer. When you plan which gateways, and how many gateways, to associate with a specific Mediation Server cluster, it may be useful to group trunk peers with similar local dialing requirements. For example, you could write a translation rule to remove +44 from the beginning of a dial string and replace it with 0144.īy performing outbound route translation on the server, you can reduce the configuration requirements on each individual trunk peer in order to translate phone numbers into a local dialing format. To translate numbers from E.164 format to a local dialing format, you can define one or more translation rules to manipulate the request URI before you route it to the trunk peer. ![]() Thetrunk peer (that is, the associated gateway, private branch exchange (PBX), or SIP trunk) may require that numbers be in a local dialing format. Translation rules are supported for both called numbers and calling numbers. Learn about translation rules and dial string normalization in Skype for Business Server Enterprise Voice.Įnterprise Voice requires that all dial strings be normalized to E.164 format for the purpose of performing reverse number lookup (RNL).
0 Comments
Leave a Reply. |