Avaya Logo

Previous Topic

Next Topic

Book Contents

Book Index

Voice system not answering

The voice system will not take calls. The voice system rings but does not answer, or the voice system is busy.

Note:
If host interaction is involved, refer to Host interaction not working right.

Investigating the problem

To check on possible causes of the problem:

  1. Enter display card all or go to the Display Equipment screen to check the status of cards.
  2. All NMS cards should be in the in service (INSERV) state.

  3. If cards are not in service, you may try to restore them or contact your Avaya support representative.
  4. See Restoring cards and channels for procedures that may bring cards back into service.

  5. Make sure PLAY/CODE, TTS, or both, are assigned to an INSERV NMS card.
  6. Make sure that the voice response application is properly assigned to the channel or channels.
  7. Make sure the voice response application contains an action to answer the phone.
  8. Check the Message Log report for messages indicating that Transaction State Machine process (TSM) is respawning because there are too many channels in the system.
  9. If TSM is respawning, change NCHANNELS and NCALLS.

Changing NCHANNELS and NCALLS, if necessary.

To tune the NCHANNELS parameter:

  1. Use /etc/conf/bin/idtune NCHANNELS value to increase the NCHANNELS tunable parameter to the value you require.
  2. The maximum value of NCHANNELS is 448, which is the factory default beginning December 2001.

  3. Use /etc/conf/bin/idbuild -B to rebuild the kernel.
  4. Reboot the system.

To set NCALLS:

  1. Execute /etc/conf/bin/idtune NCALLS 400
  2. Use /etc/conf/bin/idbuild -B to rebuild the kernel.
  3. Reboot the system.

� 2002 Avaya Inc. All Rights Reserved.