Difference between revisions of "SIP trace"
From Zenitel Wiki
(→AlphaCom XE) |
|||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{AI}}The ICX-AlphaCom 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-AlphaCom== | ||
| + | Log on to the [[Linux Console]] via SSH (user: '''alpha'''; password: '''alphacom'''), and type: | ||
| + | |||
| + | {{code|tst-sipd}} | ||
| + | |||
| + | A few simple input commands are implemented, type single letters; | ||
| + | |||
| + | <pre> | ||
| + | 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 | ||
| + | </pre> | ||
| + | |||
| + | 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. | ||
| + | |||
| + | See video: | ||
| + | <div style="text-align:left;"> <youtube width="300" height="180">BrzxXa4OrIs</youtube> </div> | ||
| + | |||
| + | ==AlphaCom XE== | ||
Log on to the [[Linux Console]] via SSH (or telnet on AMC 10) (user: '''alpha'''; password: '''com'''), and type: | Log on to the [[Linux Console]] via SSH (or telnet on AMC 10) (user: '''alpha'''; password: '''com'''), and type: | ||
| Line 17: | Line 39: | ||
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). | 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). | ||
| + | |||
| + | See video: | ||
| + | <div style="text-align:left;"> <youtube width="300" height="180">GyPkw73KEFE</youtube> </div> | ||
| + | |||
== Related articles == | == Related articles == | ||
* [[SIP]] | * [[SIP]] | ||
* [[AlphaCom SIP interface]] | * [[AlphaCom SIP interface]] | ||
| − | [[Category:AlphaCom - SIP Integration]] | + | [[Category: ICX-AlphaCom - SIP Integration]] |
| + | [[Category: AlphaCom - SIP Integration]] | ||
[[Category: AlphaCom Troubleshooting]] | [[Category: AlphaCom Troubleshooting]] | ||
| + | [[Category: ICX-AlphaCom Platform]] | ||
Latest revision as of 12:10, 24 October 2023
The ICX-AlphaCom 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-AlphaCom
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.
See video:
AlphaCom XE
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).
See video: