beautypg.com

Configuring an fxo interface, Configuring cid, Enabling cid receiving for an fxo interface – H3C Technologies H3C MSR 5600 User Manual

Page 16: Enabling cid sending for an fxo interface, Configuring busy tone detection

background image

6

Configuring an FXO interface

This section covers the procedures for configuring an FXO interface.

Configuring CID

The CID function must be configured on both the FXS and FXO interfaces. For information about
configuring this function on the FXS interface, see "

Configuring CID

."

For the CID function to work correctly, enable both CID receiving and CID sending.

Enabling CID receiving for an FXO interface

The FXO interface receives the CID. By default, it detects the CID from the PBX between the first and

second rings.
To enable CID receiving:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter FXO interface view.

subscriber-line line-number N/A

3.

Configure the time for CID detection

and after the CID detection, the
number of rings the FXO interface

receives before going off-hook.

cid ring { 0 | 1 | 2 } [ times ]

By default, CID detection is
performed between the first and

second rings, and the FXO

interface goes off-hook as soon
as the detection is complete (cid

ring 1 0).

4.

Enable CID receiving for the FXO

interface.

cid receive

By default, this function is
enabled.

Enabling CID sending for an FXO interface

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter FXO interface view.

subscriber-line line-number N/A

3.

Enable CID sending for the FXO

interface.

cid send

By default, this function is
enabled.

Configuring busy tone detection

PBX switches might use different busy tone standards. If a user on the PBX side hangs up, the router knows

the on-hook operation by detecting a busy tone.
As shown in

Figure 1

, Telephone A establishes a call to Telephone B, and then Telephone A goes on-hook.

The PBX plays the busy tone to Router A after detecting the on-hook condition of Telephone A. If Router
A cannot identify the played busy tone, the FXO interface on Router A will remain seized or fault

detection occurs. To solve this problem, you can configure busy tone detection for the FXO interface.