Difference between revisions of "SIP trace"
From Zenitel Wiki
| Line 43: | Line 43: | ||
[[Category:AlphaCom - SIP Integration]] | [[Category:AlphaCom - SIP Integration]] | ||
[[Category: AlphaCom Troubleshooting]] | [[Category: AlphaCom Troubleshooting]] | ||
| − | [[Category: ICX | + | [[Category: ICX-AlphaCom Platform]] |
Revision as of 11:22, 30 January 2020
The ICX and AlphaCom XE offers runtime trace and debug logging via the Linux Console. This is intended for debug and on-site trouble shooting of SIP communication between an ICX or AlphaCom, and a SIP device.
ICX
Log on to the Linux Console via SSH (user: alpha; password: alphacom), and type:
tst-sipd
|
A few simple input commands are implemented, type single letters;
0,1,2,3,4,5,6,7: Set tracelevel.
0: Fatal errors only
4: SIP/AlphaNet message trace (default)
7: All internal debug trace also
l: list active calls
h: This text
To do a SIP trace you normally choose level 4. You will see all SIP messages on the SIP trunk, as well as the internal messages between the SIPd (the internal SIP server running on the ICX) and the intercom application.
AlphaCom
Log on to the Linux Console via SSH (or telnet on AMC 10) (user: alpha; password: com), and type:
tst -s /tmp/sipd_trace
|
A few simple input commands are implemented, type single letters;
0,1,2,3,4,5,6,7: Set tracelevel.
0: Fatal errors only
4: SIP/AlphaNet message trace (default)
7: All internal debug trace also
l: list active calls
h: This text
To do a SIP trace you normally choose level 4. You will see all SIP messages on the SIP trunk, as well as the internal messages between the SIPd (the internal SIP server running on the AMC-IP card) and the AMCd (the intercom application).