Avaya Media Processing Server 1000 Hardware Installation And Maintenance page 179

• DCC
• TMS
The TMS spans can generate alarms due to the following conditions:
1. cabling problem
2. network equipment (for example, the far end is out of service)
3. hardware problem
4. protocols are incompatible
5. spans are not enabled or are taken out of service
Troubleshooting
Check the System alarm report which detects any span not in service (green).
TMS Memory
TMS supports two types of memory: CPU memory and Voice memory. CPU memory is allocated
and freed in the normal processing of a call. Voice memory is used by player, recorder, and FAX
resources.
Any memory allocation alarm indicates that a request made on the part of an application is not
completed. Under certain load scenarios a TMS can temporarily run out of memory but recover with
no adverse side affect. Applications can cycle then recover on the next call instance. Situations that
can have a temporary affect on memory are system failover and Ethernet problems.
The following modules can be affected:
• TMS run time image Resources used: Player, Recorder, or FAX.
The TMS memory can generate alarms due to the following conditions:
• faulty hardware
• undetected software error causing memory leak
• hardware software race condition causing memory leak
• insufficient memory configuration for software load
• system load
• Ethernet problem
• system failover
Troubleshooting
Use the following procedure to troubleshoot memory allocation alarms.
1. If the problem occurred after updating packages or applications, a software issue exists with
the new load or there is insufficient memory on the TMS to support the new images.
2. Use a web interface to the TMS to determine which processes are consuming memory on
the TMS.
3. Check for Ethernet problems on the network.
October 2014 Avaya Media Processing Server 1000 Hardware Installation and Maintenance
Comments? infodev@avaya.com
TMS Spans
179