Avaya Aura® Media Server Instructions for creating a JIRA John Muller Design Lead Avaya Aura® Media Server muller1@avaya.com

Enable Debug Tracing Disabled by default and needs to be enabled prior to capturing logs. Captured logs must capture the reported issue. Set Debug Logging to “Enabled” under System Configuration-> Debug Tracing->General and click “Save”.

Capturing AMS Debug Tracing Using Element Manager In EM locate Tools->Log Capture, ensure “Include Trace Logs” is checked, and click download. Will be prompted for a location on your desktop to save the zip, which contains AMS debugging information.

Capturing AMS Debug Tracing Using CLI Linux SSH to server and run the command logcapture -t Windows Remote Desktop to server, open command prompt and run the command logcapture –t Transfer file log.zip off the server

Core Media Server Issues (Audio or QoS) Set Components to “Media Server” JIRA must include the following information: High level description of the call flow Steps on how to reproduce (if known) Log Archive that includes traces before, during and after the issue occurred SIP Call-ID and/or the GSLID that identifies the session(s) experiencing issue Appropriate analysis of why this is a AMS issue and not application or network related Wireshark packet trace

Documentation Issues Set Components to “Documentation” JIRA must include the following information: Description of issue Documentation number and title Revision and publication date Page, table or figure numbers where the issue occurs For usability issues suggestions to how to improve

Element Manager Issues Set Components to “Media Server” JIRA must include the following information: High level description of problems Log Archive that includes traces before, during and after the issue occurred Steps on how to reproduce (if known) Detailed error message (screenshots preferred)

Installer Issues Set Components to “Media Server” JIRA must include the following information: PVI checker output Linux located in /root/maspviresult.xml Windows located in C:\Users\Administrator\maspviresult.xml Installer logs Linux located in /var/log/mas/install Windows located in C:\MA_Logs Detailed error message (screenshots preferred)

AAMS EM Issues on SMGR Log File /var/log/Avaya/mgmt/mediaserver/ams_debug.log Debug log level configurable in Jboss log4j ($JBOSS_HOME/server/avmgmt/conf/log4j.xml) and update lines that contain com.avaya.ams.em. For example: <logger name="com.avaya.ams.em.avmgmt.debug" additivity="false">