TDM Configuration Restart Guidelines
The Oracle® Enterprise Session Border Controller (Enterprise 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
The following tables show which parameters cause the system to restart or reload after you change them.
State | Restart |
Logging | No configuration change required for resetting logging |
Line mode | Restart. The PRI interface 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 |