This article describes the steps necessary to configure the SBC Edge (SBC) to fork calls using User attributes stored in Active Directory by employing the SBC's Transformation and Call Forking features.
In this example we use a PSTN - SBC - Lync/SBA environment, and we want to route all calls from PSTN to Lync clients to a Lync user, and we want them forked to the same Lync user's mobile and IP phone numbers using attributes from the user's AD record.
A PBX phone 6222 dials the Lync/SBA user's extension number 1005, resulting in the call landing on the inbound ISDN Signaling Group on the SBC. The call is then routed using the relevant Call Route Table triggering the relevant sequence of events:
Before you begin, you'll need to verify the following:
Before you begin, make sure the SBC is configured and integrated with Lync/SBA as described in Call Routing Based on Active Directory User Attributes. In addition to this, verify the SBC Active Directory settings:
Please note: this article ONLY describes the steps necessary to configure the call forking feature.
Active Directory Configuration
Active Directory Domain Controller Configuration
In this section, we provide a step-by-step configuration walk-through enabling the use of Call Forking on the SBC:
We will need three Transformation Tables created as shown below:
Configure the "Calling Address/Number" and "Called Address/Number" translations
Configure the "User Value" translation to another AD attribute format "ipPhone"
Configure the "User Value" translation to another AD attribute format "mobile"
We create three entries in a Call Route used for ISDN to Lync calls, as shown below:
ISDN to Lync/SBA client route entry
Note that Fork Call is set to Enabled, so for a particular call will continue.
ISDN to Lync/SBA client's ipPhone route entry
Note that Fork Call is set to Enabled, so routing for a particular call will continue.
ISDN to Lync/SBA client's mobile device route entry
Note that Fork Call is set to Disabled, so routing for a particular call will stop at this entry.
The ISDN signaling group for inbound calls is configured to use the relevant Call Routing Table (configured in the previous section):
See Call Routing Based on Active Directory User Attributes for more information on call routing via Active Directory.