In this section:
After you implement your configuration, you will want to test it out. The
Logs may be viewed from either user interface:
From the EMA GUI:
The Call Trace function allows you to get the SIP message trace and RTP packets for a very specific call. This is helpful when you are testing a particular call scenario. You can trace on called number, calling number, trunk group, IP Peer.
The SIP messaging (and SBC-specific logs related to the call) are stored in a text file ending in ".TRC".
In addition to the .TRC file, the SIP signaling and RTP traffic can also be captured in a ".PKT" file. To view the ".PKT" file, you download it to your PC, and then open it with Wireshark interface (referred to as "TShark" in EMA Troubleshooting tab). You can see what trace filters are set up using "show configuration global callTrace
" command.
Below is an example usage for call trace "toBLUECARRIER" that traces all calls to and from trunk group BLUECARRIER:
admin@SBC01a> show configuration global callTrace callFilter toBLUECARRIER { state enabled; level level1; key trunkGroup; match { trunkGroup BLUECARRIER; } mediaPacketCapture enable; }
Since a large amount of data is captured for each call, it is advisable to:
See Troubleshooting Tools - TShark for additional details of using TShark from the EMA.
To save a text file containing the CLI commands used to configure your system, see System Administration - Configuration Template Import (EMA).