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) |
|||
(2 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | + | {{Breadcrumb|0|0|{{dev-en}}|optiPoint|optiPoint 410/420 S}} | |
− | {{ | ||
− | |||
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 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. | ||
Line 7: | Line 5: | ||
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 get this trace | + | To get this trace: |
− | :* 1. Log-in to the [[WBM]] as administrator | + | :* 1. Log-in to the [[WBM]] as administrator and select "Fault Investigation"-menu |
: [[Image:optiPoint_SIP_Admin_FaultInvestigation.JPG|none|thumb|Select Fault Investigation]] | : [[Image:optiPoint_SIP_Admin_FaultInvestigation.JPG|none|thumb|Select Fault Investigation]] | ||
− | :* 2. | + | :* 2. Following page will be loaded - select "SIP UDP Trace" |
: [[Image:optiPoint_SIP_FaultInvestigation.JPG|none|thumb|Select SIP UDP Trace]] | : [[Image:optiPoint_SIP_FaultInvestigation.JPG|none|thumb|Select SIP UDP Trace]] | ||
− | :* 3. Enable the SIP UDP Trace - set the check box and | + | :* 3. Enable the SIP UDP Trace (till V7 R5.6.0 - later on the trace is automatically enabled): set the check box flag and push "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]] | ||
:* 4. 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]] | ||
− | |||
[[Category:optiPoint]] | [[Category:optiPoint]] | ||
[[Category:Configuration]] | [[Category:Configuration]] |
Latest revision as of 09:59, 19 November 2013
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:
- 1. Log-in to the WBM as administrator and select "Fault Investigation"-menu
-
- 2. Following page will be loaded - select "SIP UDP Trace"
-
- 3. Enable the SIP UDP Trace (till V7 R5.6.0 - later on the trace is automatically enabled): set the check box flag and push "Submit"
-
- 4. After desired trace period, follow the link to the message log