2 Time Division Multiplexing Configuration
To perform Time Division Multiplexing (TDM) operations on the Oracle® Enterprise Session Border Controller (E-SBC), you must enable TDM, specify the parameters for the interface in use, run the TDM configuration wizard, and create local policies for routing TDM traffic.
- Configure the
tdm-config element and its corresponding sub-elements. The
tdm-config element, located under
system, contains the parameters that are common to all TDM configurations. The sub-elements contain the particular parameters for the interface that the system detects in use on the
E-SBC. The system displays the sub-elements, as follows:
- When the E-SBC detects either the Primary Rate Interface (PRI) or the Basic Rate Interface (BRI) interface, tdm-config displays the tdm-profile sub-element with the parameters that correspond to the interface. See "Primary Rate Interface Support" and "Basic Rate Interface Support."
- When the E-SBC detects the Analog interface, tdm-config displays both the fxo-profile and the fxs-profile sub-elements with the parameters that correspond to the interface. See "Foreign Exchange Office-Foreign Exchange Subscriber Support."
- Run the TDM configuration wizard to complete the configuration. The wizard creates the realm, SIP interface, steering pools, and other necessary configuration elements including the network interface and the phy-interface for SIP call routing. With SRTP enabled (default), the wizard also creates the
media-sec-policy object, enables the
secured-network attribute for the
sip-interface
object, and configures the
media-sec-policy attribute for
realm-config. You can run the wizard from either the Web GUI (Set TDM Configuration) or the ACLI (setup tdm).
The Oracle® Enterprise Session Border Controller (E-SBC) requires running the TDM configuration wizard only after the initial TDM configuration. The system does not require you to run the wizard after you make changes to the existing configuration.
Note:
When the Oracle Session Delivery Manager (SDM) manages the E-SBC, you configure TDM from the SDM and you do not need to run the TDM configuration wizard. See "Time Division Multiplexing (TDM) Settings on the Session Delivery Manager (SDM)" for the required settings. - Configure the local policy for routing traffic through the TDM interface. For unidirectional TDM call routing, the system requires a local policy only for the call direction that you want. For example, inbound-only or outbound-only. For bi-directional TDM call routing, create both inbound and outbound local policies. See "Local Policy Configuration for Time Division Multiplexing."
- ACLI—Use the tdm-config, tdm-profile, fxo-profile, and fxs-profile elements located under system.
- Web GUI—Basic mode. Double-click the TDM icon in the network diagram to display the TDM configuration dialog.
- Web GUI—Expert mode. Use the tdm-config, tdm-profile, fxo-profile, and fxs-profile elements located under system.
- Session Delivery Manager (SDM)—Launch the Web GUI from SDM and use the tdm-config, tdm-profile, fxo-profile, and fxs-profile elements located under system.
TDM Configuration Restart Guidelines
The Oracle® Enterprise Session Border Controller (E-SBC) uses the Digium Asterisk Hardware Device Interface (DAHDI) to support Time Division Multiplexing (TDM) operations. In certain situations, the DAHDI requires a restart to apply changes to any tdm-config, tdm-profile, fxo-profile, or fso-profile configuration parameter that the system cannot update by simply reloading the configuration. When you attempt to activate configuration changes, the system detects any change that requires a restart and issues the dahdi restart command. Oracle recommends making changes to parameters that require a restart during a maintenance window because the system terminates all active TDM calls during the restart process.
tdm-config
Use the information in the following tables to know which parameters cause the system to restart or reload when they are changed.
| State | Restart |
| Logging | No configuration change required for resetting logging |
| Line mode | Restart. The PRI also requires a reboot. |
| Tone zone | Restart |
| Calling pres | Reload |
| Caller ID |
|
tdm-profile
| Name | Restart |
| Signaling | Restart |
| Switch type | Restart |
| B-channel | Restart |
| D-channel | Restart |
| Span number | Restart |
| Route group | Restart |
| Line build out | Restart |
| Framing value | Restart |
| Coding value | Restart |
| Term resistance | Restart |
| Timing source | Restart |
| Rx gain | Reload |
| tx gain | Reload |
| Echo cancellation | Reload |
| Overlap dial | Restart |
| Incoming pattern | Reload |
| Options | Reload |
fxo-profile, fso-profile
| Name | Restart |
| Channels | Restart |
| Rx gain | Reload |
| Tx gain | Reload |
| Echo cancellation | Reload |
| Fax detect | Reload |
| Route group | Reload |
| Call group | Reload |
| Pickup group | Reload |
| Immediate answer | Reload |
| Signaling | Reload |
| Phone number | Reload |
| Full name | Reload |
| CID signaling | Reload |
| Options | Reload |
Incoming Call Pattern Guidelines
When you configure either the Primary Rate Interface (PRI) or Basic Rate Interface (BRI) interface for Time Division Multiplexing (TDM), you can set a list of extension numbers and match patterns for routing incoming calls. You can specify exact matches as well as patterns that route to a range of destinations.
For example, suppose that a company with 300 employees deploys the Oracle® Enterprise Session Border Controller (E-SBC) and connects to the PSTN network by way of an ISDN interface. The company allocates 300 extension numbers: numbers 7100 - 7399 for employee desk phones, and number 70 for the reception desk so that it is easy to remember.
The service provider assigns the prefix 49331200 to the company, so the reception desk PSTN number becomes 4933120070 and the employee numbers become 493312007100 , 493312007101-493312007399.
The incoming pattern in this example will match either the reception desk number or one of the other extensions. When the match is successful, the received number is complete and the call setup can proceed. You can configure TDM to match the reception desk number as a whole: "4933120070," and to match any of the other extensions through a single pattern: "_493312007[1-3]XX". To put these rules together, set the incoming-pattern parameter to the following value: "4933120070|_493312007[1-3]XX".
In match patterns, separate single extension numbers with the vertical bar (|) character. Start a match pattern with the underscore (_) character preceding the first number of the pattern. Do not use the underscore with an exact match. Type the exact match, starting with the first number. An exact match does not use In an extension pattern, note the meaning of the following characters:
X matches any digit from 0-9
Z matches any digit from 1-9
N matches any digit from 2-9
[1237-9] matches any digit in the brackets (in this example, 1,2,3,7,8,9).
. wildcard, matches one or more characters
! wildcard, matches zero or more characters immediately