Reference12r1:Maintenance/Diagnostics/Tracing

From innovaphone-wiki

Jump to: navigation, search
There are other versions of this article: Reference | Reference7 | Reference9 | Reference12r1 (this version)

Using the trace(buffer) link, the trace information of the VoIP device can be viewed and saved. In the process, a text file log.txt is generated, which displays the current trace in a new browser window.

Using the trace(continuous) link, the continuous trace information of the device can be viewed and saved. In the process, a text file clog.txt is generated, which displays the current trace in a new browser window. As already mentioned, the messages are continuously automatically updated and are scrolled upwards, out of the window.

Using the trace(crash-dump) link (only for IPVA), the trap trace information of the IPVA since last crash can be viewed and saved. In the process, a text file crash_dump.txt is generated, which displays the last trap trace in a new browser window.


For both trace variants, only messages that were enabled in this menu are displayed. Not every section and not every setting is visible, this will depend on which device is being used.

  • TEL1-n: Information on the TEL1-n interface.
  • BRI1-n: Information on the BRI1-n interface.
  • PRI1-n: Information on the PRI1-n interface.
  • PPP: Information on the PPP interface.
  • H.323/Signaling: Information on H.323 signaling.
  • SIP/UDP Signaling: Information on SIP/UDP signaling.
  • SIP/TCP Signaling: Information on SIP/TCP signaling.
  • SIP/TLS Signaling: Information on SIP/TLS signaling.
  • PBX: Information on PBX application.
  • Gateway: Information on Gateway application.
  • DECT Master: Information on DECT Master application.
  • DECT Master/PP-Manag.: Information on DECT Master management.
  • DECT Radio: Information on DECT Radio application.
  • DECT Radio/PP-Manag.: Information on DECT Radio management.
  • NAT: Information on Network Address Translation.
  • H.323-NAT: Information on H.323 specific Network Address Translation.
  • All TCP/UDP Traffic: Information on all TCP/UDP data (may fill up trace buffer quickly).
  • Enable RPCAP: Enable Remote PCAP access in order to get continuous trace information using Wireshark (Howto:Pcap).
  • Write PCAP to URL: Write PCAP trace to specified URL
URL is expected to be the URL for a folder on a WebDAV drive like http://172.16.0.1/DRIVE/CF0/
A new file will be created each 20MB. The files will be called like <mac>-<sequential-number>.pcap (e.g. 0090332f3364-0000003837.pcap).
Don't use local DIR starting with "/" in the field. This causes a non-wellformed XML file.
Personal tools