AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 571 / 1248

Version 7.2 571 Mediant 500 MSBR
User's Manual 30. Configuring Supplementary Services

BellcoreCallerIDTypeOneSubStandard: Defines the Bellcore Caller ID sub-
standard.

ETSICallerIDTypeOneSubStandard: Defines the ETSI FSK Caller ID sub-standard.

EnableCallerIDTypeTwo: Enables generation of Caller ID type 2 when the phone is
off-hooked (used for call waiting).

RingsBeforeCallerID: (FXO interfaces only) Defines the number of rings before the
device starts detection of Caller ID. By default, the device detects Caller ID between
the first and second rings.

AnalogCallerIDTimimgMode: (FXS interfaces only) Defines the time period when a
Caller ID signal is generated. By default, Caller ID is generated between the first two
rings.

PolarityReversalType: (FXS interfaces only) Defines reversal polarity and/or wink
signals for Caller ID signals. It is recommended to configure the parameter to 1 (Hard).

UseSourceNumberAsDisplayName and UseDisplayNameAsSourceNumber:
Defines Caller ID interworking.
30.9.2 Debugging a Caller ID Detection on FXO
The following procedure describes how to debug caller ID detection on FXO interfaces.

To debug a Caller ID detection on an FXO interface:
1. Verify that the parameter EnableCallerID is set to 1.
2. Verify that the caller ID standard (and substandard) of the device matches the
standard of the PBX (using the parameters CallerIDType,
BellcoreCallerIDTypeOneSubStandard, and ETSICallerIDTypeOneSubStandard).
3. Define the number of rings before the device starts the detection of caller ID (using the
parameter RingsBeforeCallerID).
4. Verify that the correct FXO coefficient type is configured (see the CountryCoefficients
parameter in Configuring FXS/FXO Coefficient Types on page 613), as the device is
unable to recognize caller ID signals that are distorted.
5. Connect a phone to the analog line of the PBX (instead of to the device's FXO
interface) and verify that it displays the caller ID.
If the above does not solve the problem, you need to record the caller ID signal (and send
it to AudioCodes), as described below.

To record the caller ID signal using the debug recording mechanism:
1. Access the FAE page (by appending "FAE" to the device's IP address in the Web
browser's URL, for example, http://10.13.4.13/FAE).
2. Press the Cmd Shell link.
3. Enter the following commands:
dr
ait <IP address of PC to collect the debug traces sent from
the device>
AddChannelIdTrace ALL-WITH-PCM <port number, which starts from
0>
Start
4. Make a call to the FXO.
5. To stop the DR recording, at the CLI prompt, type STOP .