Avaya Aura Media Server Instructions for creating a

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

Enable Debug Tracing 4 Disabled by default and needs to be enabled prior to capturing logs. Captured logs must capture the reported issue. 4 Set Debug Logging to “Enabled” under System Configuration-> Debug Tracing->General and click “Save”. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 2

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

Capturing AMS Debug Tracing Using CLI 4 Linux – SSH to server and run the command logcapture -t 4 Windows – Remote Desktop to server, open command prompt and run the command logcapture –t 4 Transfer file log. zip off the server Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 4

Core Media Server Issues (Audio or Qo. S) 4 Set Components to “Media Server” 4 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 Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 5

Documentation Issues 4 Set Components to “Documentation” 4 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 Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 6

Element Manager Issues 4 Set Components to “Media Server” 4 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) Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 7

Installer Issues 4 Set Components to “Media Server” 4 JIRA must include the following information: – PVI checker output – Linux located in /root/maspviresult. xml – Windows located in C: UsersAdministratormaspviresult. xml – Installer logs – Linux located in /var/log/mas/install – Windows located in C: MA_Logs – Detailed error message (screenshots preferred) Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 8

AAMS EM Issues on SMGR 4 Log File – /var/log/Avaya/mgmt/mediaserver/ams_debug. log 4 Debug log level configurable in Jboss log 4 j ($JBOSS_HOME/server/avmgmt/conf/log 4 j. xml) and update lines that contain com. avaya. ams. em. For example: <logger name="com. avaya. ams. em. avmgmt. debug" additivity="false"> Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy. 9