Avaya S8700 Maintenance Manual page 139

For multi-connect configurations
Hide thumbs Also See for S8700:
Table of Contents

Advertisement

Multimedia Call Handling (MMCH)
PRI D-Channel Backup
A somewhat unlikely source of call-stability problems can be incorrectly translated
PRI D-channel backup between two non-MCU systems. As an example:
System A's DS1 1A10 is assigned as the primary source
System B's corresponding DS1 is assigned as the secondary source
Then (when scheduled maintenance runs on either system with its backup
D channel active), an audit disconnects some calls using the link. This problem is
corrected by assigning matching primary/secondary D channels for the two
systems.
Processor Duplication in the System
Do not enable the PI link switch during scheduled maintenance. This can cause
link-stability problems on the Accunet Bandwidth Controller (ABC).
Voice-Activated Switching Problems
Voice-activated switching on the S8700 Multi-Connect Multimedia Call Handler
(MMCH) does not follow the loudest talker. The MMCH queues every speaking
party and selects a new video broadcaster (the second-oldest speaking party)
when the oldest speaking party has stopped talking. The new broadcaster will
see the last speaker as its video. The system can also "learn" about the noise
coming from an endpoint to help prevent false switches, adapting both to noise
level and repetitive sounds such as a fan. This adaptation occurs over
approximately 10 seconds.
No Switching, Full Motion Video
If a room is excessively noisy:
The S8700 Multi-Connect MMCH may receive sufficient audio signal to
conclude that there is a speaker present. Use the Status Conference x
form to determine whether the MMCH thinks an endpoint is talking. The
MMCH sets the Ts field to t for each endpoint if there is voice energy
detected. This endpoint may have to mute when nobody at the site is
speaking to allow the conference to proceed normally.
Remind the customer that it may be necessary to mute if a side
conversation is going on in the background, just as one would do in an
audio conference.
If the system does not switch broadcasters even after the current
broadcaster has muted, check the conference administration using the
display conference X command to ensure that the conference is in
voice-activated mode. Also verify that parties who were speaking are valid
video sources as described in
4-63.
555-233-143
''Calls Terminate with No Video'' on page
Issue 1 May 2002
4-65

Advertisement

Table of Contents
loading

Table of Contents