MST Trace

[ahartoch]

Hi,

I'm trying to monitor a problem with an One-X mobile and I need to activate the traces for 2 trunks groups at the same time. One for the SIP trunks from the One-X mobile and the other for the BRI trunk group. Is it possible to view both traces at the same time? If not what is the best approach?

Thanks in advance,
Alex

[risuaan]

Hi Alex,

In response to your query about MST traces both for SIP trunk and BRI Trunk, my answer is Yes you can both set them up in the MST form in Communication Manager.
You may need to enable both ISDN-BRI? y and SIP Trunks? y. After enabling them, on page 2 of the MST form, you will find the options you want to set for BRI tracing and on page 15 of the MST form, you can check the options you want to enable for SIP tracing. I have screenshots for your reference below. Once you enabled both MST (enable mst) in SAT after you have configured BRI and SIP MST forms, you may already make test calls or capture calls through BRI and SIP trunks while the MST trace is running. Once done capturing the calls, you need to "disable mst" in SAT.

You may also need to enable Trace Analyzer in the MST form before taking the trace for you to be able to get the raw file in the Communication Manager Web Maintenance window. MST raw file (.M file format) means that the traces are encoded in hexadecimal formats. You can save them in notepad and decode them afterwards for you to analyze.

Hope this helps...

change mst Page 1 of 17
MESSAGE SEQUENCE TRACE
Run Time Limit: 99 days Disable On Buffer Full? n Generic Filters? n
Store Timestamp? y Start Trigger? n Log Mst? y
Message Storage: entire Stop Trigger? n Trace Analyzer? y
Stop Count:
Retrigger? n
X.25? n GATEWAY? n EWT? n DEBUG BUTTON? n HW ERROR LOG? n
ISDN-PRI? n CCMS? y SIP Trunks? y PRECs? n PROC ERRORS? y
ISDN-BRI? y PACKET? n CALL TRACE? y BSR? n IP? n
ASAI? n VECTORS? n CDR? n DENIAL EVENTS? y BASM? n
CMS? n VECTOR EVENTS? n PMS? n FW ERROR LOG? n
IP Stations/LSPs/ESSs? y
X.25 Filter Data
Processor Channel: 1 Link Control: all
Application Data: none Session Timers? y
Confirmations? n Application Errors? y
Session Control: all Unrecognized Messages? y
Processor Channel Control: all


change mst Page 15 of 17
MESSAGE SEQUENCE TRACE
SIP Filter Data
Signaling Group:
Message Bodies? n
Calling User:
Called User:


change mst Page 2 of 17
MESSAGE SEQUENCE TRACE
ISDN-PRI Filter Data:
Port Type: b-channel Port:
Call Control? y Incoming Calling Number:
Maintenance? y Incoming Called Number:
Outgoing Calling Number:
Outgoing Called Number:
ISDN-BRI Filter Data:
Port Selection: specific-ports Bri Ports:
Call Control? y
Maintenance? y
Unrecognized? y
Level 2 Primitives? y