Avaya DEFINITY Server CSI, Руководство по обслуживанию, Страница: 117 / 1930

Multimedia Call Handling
Issue 5 October 2002
117
555-233-119
Before troubleshooting any problems associated with the Avaya Definity Server
CSI MMCH, always be sure that the endpoint is operating correctly (audio, video,
and data) by making point-to-point test calls. If possible, make the test calls over
the network to test the connectivity and routing of network calls from the endpoint.
This eliminates problems such as disconnected audio or video cables and
network troubles.
64 Kbps Calls Terminate but Far End Receives
56 Kbps Indication
Description
Some 2x64 Kbps conferences on the Avaya Definity Server CSI MMCH do not
establish because of framing, audio, or video problems.
For calls that are routed in the network through an Avaya/LEC interface, the
originating equipment may launch a 64 Kbps call attempt, and the far end
receives either a 56 Kbps or 64 Kbps indication. If the far end receives a 64 Kbps
indication, the call may have used 56 Kbps facilities. If so, the call may exhibit any
of the following conditions:
■
No handshaking in one direction or both (call disconnects after timeouts)
■
Call connects, but audio or video is corrupted (audio noise or no video)
■
Call succeeds without disruption (this is the least likely since one endpoint
must be aware that the call is really 56 Kbps to connect)
If any of the above conditions occur, then 64 Kbps calls from the site are blocked.
Solution
Administer the conference for connection at 56 Kbps.
Calls Terminate with No Audio
Description
To support endpoints that do not support Multipoint Command Conference (MCC),
the Avaya Definity Server CSI MMCH changes its capability set and initiates a
capability set exchange with the endpoint when the Selected Communications
Mode (SCM) changes. If the endpoint does not follow the SCM audio mode, the
MCU may include the endpoint as a secondary (audio only) endpoint. If the
endpoint sends an unknown or unsupported audio mode, then the TN788B
decoder port mutes the endpoint from the conference. The user may hear the
conference but may not be heard by other parties in the conference.