Routing Policies

Last Updated : Feb 26, 2015 |
Use the Routing Policies page to create and modify routing policies.
All Routing Policies together form the Enterprise wide dial plan.
Routing Policies can include the Origination of the caller, the Dialed digits of the called party, the Domain of the called party and the actual time the call occurs.
Optionally, you can define a Regular Expression in place of the Dialed digits and the Domain of the called party.
Session Manager determines the destination of the call depending on one or more inputs as mentioned above.
If you qualify the destination using the Deny option, Session Manager does not route the call.
Session Manager uses the data configured in the routing policy to find the best match against the number or address of the called party.
Note:
If Session Manager cannot match any dial patterns, Session Manager then attempts to find a matching regular expression. Session Manager examines each regular expression in the administered Rank Order and determines if the expression matches the request-URI. During this comparison, user parameters are not stripped; however, the request-URI is compared against each regular expression twice. The first time, the entire request-URI is compared. The second time, if there is no match, only user@host is compared, that is the URI scheme, sip:, sips:, tel:, and any URI parameters appearing after the host-part of the request-URI are stripped. If there is a match, Session Manager selects routing policies according to the administered regular expressions.