Difference between revisions of "optiPoint 410/420 S UDP Trace"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
(added hint that the trace is activated as default/removed the warning because the internal sip udp trace has no longer an influence on the performance) |
|||
Line 3: | Line 3: | ||
</div> | </div> | ||
− | If problems in operating the [[optiPoint 410/420 S]] phones are encountered, showing a display message like "no server" or "Registering..." for a longer time, then these problems are likely to be related to the signalling with the SIP proxy or registrar. It is often helpful to capture the messages with a network '''hub''' and display these data with one of the well known tools to examine the problem in more detail. | + | If problems in operating the [[optiPoint 410/420 S]] phones are encountered, showing a display message like "no server" or "Registering..." for a longer time, then these problems are likely to be related to the signalling with the SIP proxy or registrar. It is often helpful to capture the messages with a network '''hub''' and display these data with one of the well known tools (e.g. Wireshark) to examine the problem in more detail. |
If no hub is available or a PC trace tool cannot be used for some reason, the '''build in SIP UDP trace''' of the optiPoint can be used as well. | If no hub is available or a PC trace tool cannot be used for some reason, the '''build in SIP UDP trace''' of the optiPoint can be used as well. | ||
− | To | + | To get this trace (steps 1. - 3. are no longer necessary after upgrading to an optiPoint 4x0 SIP version >= V7 R5.6.0, because the internal SIP UDP trace is activated as default since V7 R5.6.0): |
− | :* | + | |
+ | :* 1. Log-in to the [[WBM]] as administrator to activate the trace | ||
: [[Image:optiPoint_SIP_Admin_FaultInvestigation.JPG|none|thumb|Select Fault Investigation]] | : [[Image:optiPoint_SIP_Admin_FaultInvestigation.JPG|none|thumb|Select Fault Investigation]] | ||
− | :* Select the fault investigation menu | + | :* 2. Select the fault investigation menu |
: [[Image:optiPoint_SIP_FaultInvestigation.JPG|none|thumb|Select SIP UDP Trace]] | : [[Image:optiPoint_SIP_FaultInvestigation.JPG|none|thumb|Select SIP UDP Trace]] | ||
− | :* Enable the SIP UDP Trace - set the check box and submit | + | :* 3. Enable the SIP UDP Trace - set the check box and submit |
: [[Image:optiPoint_SIP_SIP_UDP_Trace.jpg|none|thumb|Activate the trace]] | : [[Image:optiPoint_SIP_SIP_UDP_Trace.jpg|none|thumb|Activate the trace]] | ||
− | :* After desired trace period, follow the link to the message log | + | :* 4. After desired trace period, follow the link to the message log |
: [[Image:optiPoint_SIP_Message_Log.jpg|none|thumb|SIP UDP Message log]] | : [[Image:optiPoint_SIP_Message_Log.jpg|none|thumb|SIP UDP Message log]] | ||
− | : The message log can be deleted afterwards | + | :* 5. The message log can be deleted afterwards |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
[[Category:optiPoint]] | [[Category:optiPoint]] | ||
[[Category:Configuration]] | [[Category:Configuration]] |
Revision as of 18:49, 21 July 2010
If problems in operating the optiPoint 410/420 S phones are encountered, showing a display message like "no server" or "Registering..." for a longer time, then these problems are likely to be related to the signalling with the SIP proxy or registrar. It is often helpful to capture the messages with a network hub and display these data with one of the well known tools (e.g. Wireshark) to examine the problem in more detail.
If no hub is available or a PC trace tool cannot be used for some reason, the build in SIP UDP trace of the optiPoint can be used as well.
To get this trace (steps 1. - 3. are no longer necessary after upgrading to an optiPoint 4x0 SIP version >= V7 R5.6.0, because the internal SIP UDP trace is activated as default since V7 R5.6.0):
- 1. Log-in to the WBM as administrator to activate the trace
-
- 2. Select the fault investigation menu
-
- 3. Enable the SIP UDP Trace - set the check box and submit
-
- 4. After desired trace period, follow the link to the message log
-
- 5. The message log can be deleted afterwards