Net-Net 3810
 
Acme Packet 4500
 
Acme Packet 3820
 

PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
 

In this Document

Goal

Solution

Applies to:

Goal

Describe what log files are required when opening a ticket with Acme Packet regarding call flow issues.

Solution

These files are needed for first level of analysis and troubleshooting. Providing these files upfront speeds up in resolving the issues.

Call Flow /Audio Related issues :

#Show support-info output

#show running config output

#Packet Capture from ingress /egress side of SD under question (unfiltered)
If there is not high call volume during a maintenance window, enable debug

########################################################
Debug logging levels will take considerable CPU usage so ensure that this is done in a maintenance window or low call traffic period.
########################################################

1) Turn on debug
notify sipd siplog
log-level sipd debug
log-level mbcd debug
Run the command "show nat by-index 1 63488" and capture the output to a file

2) Make the test call
Run the command "show nat by-index 1 63488" again once the call is established and RTP is OK. Capture the output to a file.
Run the command "show nat by-index 1 63488" again once the RTP is going to the wrong IP address and capture the output to a file

3) Turn off debug
notify sipd nosiplog
log-level sipd notice
log-level mbcd notice

4) Download all the logs, zip them up and attach them to the ticket or upload them to the SFTP server.

#Details on the latest configuration changes, if any

Non-Call /Audio Related issue :

#Show support-info output

#show running config output

#Details on the latest configuration changes, if any

This solution has no attachment