traceSM is a real-time capture tool located on Session Manager, you should be able to access by simply typing traceSM from the command line otherwise it is located in /opt/Avaya/contrib/bin.
Starting traceSM …
From the Session Manager command line type;
traceSM -m (for multiple instances)
Keys for traceSM …
s – start / stop capture
f – filters
c – clear screen
a – switch between SM & SM100.
i – switch between names or IP addresses.
d – switch between SIP calls or display.
r – switch between RTP simulation or not.
w – write the display filtered packet to new file
q – quit
Write the displayed (filtered) packets to a new file
aSwitch between SM and SM-100 perspectiveiSwitch between displaying Names or IPs in the column headersrSwitch between displaying RTP simulation or notdSwitch between SIP calls and display mode
Filters for traceSM …
Press f to display the filter window.
-u – extension
-nr – registrations
-ns – subscriptions
-no – option messages
-na – session manager call routing
To clear filters type f without any options.
Error traceSM doesnt run …
If you see this error type the command traceSM -k
ERROR: traceSM is already running. Only one instance is allowed.
Some additional tips from Roger (http://rogerthephoneguy.com/) thank you ….
By the way, the engineer I worked with always uses the -uni option when he starts traceSM or traceSBC. It uses unicode characters for the lines and arrows and looks MUCH cleaner on the screen. He also typically adds the filters -no -na -u xxxx at the command line when he starts the trace. And lastly, when analysing a saved trace file, he uses the -dt option. He said it “disables data throttling” and saves a few cycles.
When you write a file during a trace, you have to untar it. There will be what looks like a pcap file (It’s a pcapng). He said it’s close to a pcap, but it’s not readable within wireshark.