Page History
...
Panel | |
---|---|
In this section:
|
Call Routing Logic Overview
...
The query should return results similar to those shown below.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Pagebreak |
---|
Telephony Routing Setup
...
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to Transformation.
- In the left navigation pane, select the Transformation Table created in the previous step.
First Entry: Input Field - Called Address/Number Output Field - User Value 1
- Second Entry: Input Field - User Value 1 Output Field - Called Address/Number
Panel borderStyle none Caption 0 Figure 1 AD-based Routing via Transformation Table
Tip |
---|
Include tel: in a msRTCSIP-Line AD search if the SBC's Active Directory Configuration Operating Mode is configured to either Online, or Updates with the Normalization Cache set to False. Do not include tel: if the Normalization Cache is set to True. See Configuring SBC for Active Directory for more information. |
...
Note SBC supports the use of wild cards. This means that you can do partial matching in AD fields. The following is an example of how the =telephoneNumber= field is used to forward an inbound call to the user's new extension.
...
| ||||
Caption | ||||
---|---|---|---|---|
| ||||
Scenario
Someone dials extension 3633, the four digits are added to the Area Code and prefix as well as the wildcard character, the result (User Value 1) is used in an AD query against the =telephoneNumber= field. The contents of the first =telephoneNumber= field containing the match string is then parsed for the last four digits, which are output from the transformation.
...
You can see the AD usage in action via the WebUI log as shown below:
...
Caption | ||||
---|---|---|---|---|
| ||||
Pagebreak |
---|