H3C Technologies H3C MSR 5600 - Manual (Page 18)

8
2. Telephone A first goes on-hook. The PBX plays busy tones to Router A after detecting the on-hook
condition.
3. Execute the busytone-detect auto command on Router A to detect the busy tone. To make sure the
FXO interface can capture the busy tone sent by the PBX, H3C recommends that you execute this
command two seconds after Telephone A goes on-hook.
4. The console prompts that busy tone detection is in progress and prompts detection success when
the detection is complete.
5. Check whether the detected busy tone parameters are valid by repeating steps 1 and 2.
After Telephone A goes on-hook, the PBX plays a busy tone to Router A. If Router A detects the busy
tone, it shuts down the FXO interface.
To configure automatic busy tone detection:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter voice view. voice-setup N/A
3. Configure automatic busy
tone detection. busytone-detect auto index
line-number
N/A
4. Return to system view. quit N/A
5. Enter FXO interface view. subscriber-line line-number N/A
6. Configure the number of busy
tone detection periods.
busytone-detect period value
The default is 2.
Test multiple values to select the
value that can ensure normal
on-hook.
Configuring busy tone sending
If the PBX does not play busy tones, configure the FXO interface to send busy tones.
To configure busy tone sending:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter FXO interface view. subscriber-line line-number N/A
3. Enable busy tone sending. send-busytone enable By default, this function is disabled.
4. Set the busy tone duration. send-busytone time seconds The default is 3 seconds.
Configuring silence detection-based automatic on-hook
If the device fails to detect busy tones or the PBX does not play busy tones, you can configure this feature
to implement automatic on-hook.
When the duration of silence (whose volume is smaller than the configured threshold) exceeds the
configured silence duration, the FXO interface automatically disconnects the call.
Improper configuration of this function can lead to false on-hook. A good practice is to configure multiple
sets of parameters and select the set of parameters that can quickly release the FXO interface and does
not causes false on-hook.