Difference between revisions of "SIP trace"
From Zenitel Wiki
| Line 1: | Line 1: | ||
{{A}}The AlphaCom XE offers runtime trace and debug logging via the [[Linux Console]]. This is intended for debug and on-site trouble shooting. | {{A}}The AlphaCom XE offers runtime trace and debug logging via the [[Linux Console]]. This is intended for debug and on-site trouble shooting. | ||
| − | The trace-interface is found as an internal unix-socket in AMC: “/tmp/sipd_trace”. Log in via SSH (or telnet on AMC 10) (user: alpha; password: com), and type: | + | The trace-interface is found as an internal unix-socket in AMC: “/tmp/sipd_trace”. Log in via SSH (or telnet on AMC 10) (user: '''alpha'''; password: '''com'''), and type: |
tst -s /tmp/sipd_trace | tst -s /tmp/sipd_trace | ||
Revision as of 15:44, 28 March 2017
The AlphaCom XE offers runtime trace and debug logging via the Linux Console. This is intended for debug and on-site trouble shooting.
The trace-interface is found as an internal unix-socket in AMC: “/tmp/sipd_trace”. Log in 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).