
Managing MultiMedia Calling
Multimedia Call Handling
Administrator’s Guide for Avaya Communication Manager
261
November 2003
Hospitality features
•
Do Not Disturb — MASI terminals cannot activate Do Not Disturb.
Multimedia features
•
Multimedia Call Handling — Avaya MMCH users are not able to make H.320 calls to MASI
terminals over the MASI link. Calls between MMCX terminals and MMCH terminals are voice
only.
Troubleshooting
Verify proper operation using the following commands and follow normal escalation procedures to
resolve any failures detected by the demand test.
1
Verify the DS1 trunk using the
test board <board location> long
command.
2
Verify the ISDN Signaling Group using the
test signaling-group <group number>
command.
Also verify proper administration.
3
Verify the temporary signaling connection using the
test tsc-administered <group number>
command. Also verify proper administration.
Common error conditions
If the cable from an Avaya DEFINITY Server to the MMCX becomes disconnected, you should see
alarms raised against ISDN-SGRP and UDS1-BD. In particular, you should observe ISDN-SGRP errors
such as 769, 1793, and 257. To resolve, reconnect the cable and follow normal test procedures.
If the far-end path termination number is incorrect, you should observe MASI-PTH error 513. To resolve,
correct administration using the MASI Path Parameters screen.
If the Layer 3 TSC is not administered properly or is out of service, you should observe errors (but no
alarms) raised against TSC-ADM. Verify the signaling group administration and follow normal
escalation procedures for TSC-ADM. See the appropriate Avaya Communication Manager Maintenance
manual for your server for more information.
If the TSC fails to come up even through Layer 2 Signaling Group and below pass tests, you may run
test
tsc-administered <group number>
to force a server heartbeat test, or simply wait 5–10 minutes for the
link to recover. This situation may happen if the server running Communication Manager is rebooted or if
the MASI interface is administered before the MMCX is properly administered.
You may want to use busy port and release port commands to unlock things if features are not working.
Multimedia Call Handling
Multimedia Call Handling (MMCH) enables users to control voice, video, and data transmissions using a
telephone and PC. Users can conduct video conferences and route calls like a standard voice call. They
can also share PC applications to collaborate with others working from remote sites.
Содержание Communication Manager
Страница 320: ...Setting Up Telecommuting Training Users 320 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 416: ...Managing Group Communications Observing Calls 416 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 502: ...Administering Media Servers SNMP Agents 502 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 602: ...Phone Reference Internet Protocol IP Softphones 602 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 1338: ...Screen Reference Vector Directory Number 1338 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 1832: ...Glossary and Abbreviations Z 1832 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 1854: ...Index X 1854 Administrator s Guide for Avaya Communication Manager November 2003...