06-07-2021 04:25 AM
hiVOIP Traces
Reading through the IOS XE 17.4.x release notes there is a new feature for ASR and ISR around VOIP trace writing the call information to 10% of the memory. Can anyone tell me if the log information that is created can be sent via syslog to another systems of or accessed via SNMP queries. it is not clear if you can only access the data by running the cli commands.
Many thanks
Richard
Solved! Go to Solution.
06-07-2021 10:46 PM
In the very first section of your shared link it mentions syslog.
“VoIP Trace is a Cisco Unified Border Element (CUBE) serviceability framework, which provides a binary trace facility for troubleshooting SIP call issues. The VoIP Trace framework records both successful and failed calls. All call trace data is stored in system memory. In addition, data for calls with IEC errors is also written to the logging location configured at the system level which includes logging to a buffer or a syslog server.“
Based on this it should write the trace data to the defined syslog destination.
06-07-2021 10:46 PM
In the very first section of your shared link it mentions syslog.
“VoIP Trace is a Cisco Unified Border Element (CUBE) serviceability framework, which provides a binary trace facility for troubleshooting SIP call issues. The VoIP Trace framework records both successful and failed calls. All call trace data is stored in system memory. In addition, data for calls with IEC errors is also written to the logging location configured at the system level which includes logging to a buffer or a syslog server.“
Based on this it should write the trace data to the defined syslog destination.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide