Troubleshooting Tools - CDR Viewer

EMA UI Menu

On the

The following figure represents the CDR Viewer screen:

The following CDR fields are available:

• • Record Type
  • Record Date/Time
  • Calling Number
  • Called Number
  • GCID
  • Call Disconnect Reason
    
  • Sip Ladder
    
  • Call Duration 

The user can capture and view the CDR event when polling is enabled. Refer to Dashboard - Live Monitor for more information on polling.

Enabling or Disabling CDR Data Polling

1. On the
   Unable to show "metadata-from": No such page "_space_variables"
    main screen, navigate to Troubleshooting > Troubleshooting Tools > CDR Viewer.
    

2. To enable/disable CDR Data Polling, click the desired option as shown in the figure Enable-Disable CDR Data Polling. By default, it is Disabled for the Troubleshooting page. The CDR records are fetched from ACT records, which are generated by the

   Unable to show "metadata-from": No such page "_space_variables"
   . If Polling is enabled, the CDR records are captured and stored in the Database. The following figure represents Enable-Disable CDR Data Polling in the CDR Viewer screen:
   

   

   Note

   Enabling CDR Viewer on SBC SWe with less than 6 CPUs and less than 16 GB RAM may impact the system performance.

Filtering the CDR List

Filter the CDR list based on the following fields:

• Record Type
• Record Start Date/Time range
• Call Duration
• Calling Number
• Called Number
• GCID
• Call Disconnect Reason

The following figure represents CDR Filters:

Viewing CDR Records

Select any CDR record to view the details. The following figure represents CDR details:

Search for Specific Text

Users can also search (case-insensitive) for a specific text within the record details of a selected CDR record. The following figure represents the CDR search using Find:

CDR Data Purge

CDR data is purged either on a Disk or Age basis. The Disk-based purging occurs when the database reaches 20 percent of the evlog partition. The Age-based purging occurs for data older than one week. The user cannot view CDR records (including CDR details) and the SIP Ladder Diagram that are older than one week.

The Disk-based purging always takes precedence over Age-based purging. All users have the ability to view the CDR Viewer page, but only the Administrator and the Operators have the ability to change the settings for the CDR Viewer page.

SIP Ladder

Enabling or Disabling the SIP Ladder Tool

1. On the
   Unable to show "metadata-from": No such page "_space_variables"
    main screen, navigate to Troubleshooting > Troubleshooting Tools > CDR Viewer.  

2. To enable/disable SIP Ladder, click the desired option as shown in the figure Enable-Disable SIP Ladder. By default, it is Disabled for the Troubleshooting page. The CDR records are fetched from ACT records, which are generated by the

   Unable to show "metadata-from": No such page "_space_variables"
   . If Polling is enabled, the CDR records are captured and stored in the Database. The following figure represents the Enable-Disable SIP Ladder in the CDR Viewer screen:
   

   

SIP Ladder Diagram 

The SIP Call Ladder Diagram is a tool used to identify faults in calls. Calls are analyzed at a higher level first, and then at lower levels within the components using the SIP Ladder Diagram. To view the SIP Ladder diagram, click the SIP Ladder icon in the Sip Ladder column for a CDR entry in the CDR Call List. The following figure represents SIP Ladder diagram icons:

A SIP Call Ladder Diagram provides the following advantages:

• Viewing the high level signaling path that includes the Originator, Intermediate Destination and Final Destination of calls to know the complete call path.
• Viewing the SIP Protocol Data Unit (PDU) details either by hovering the mouse on message types or by clicking the message types (INVITE, PRACK, 200 OK, and so on) to further analyze the calls. Users can search within the PDU pop-up window.
• Viewing the signaling call ladder diagram to narrow down any issues in the call.
• Performing a drill down analysis of a failed call by further extracting the log details that occurred around that instance. These log details are viewed either on a pop-up window for a quick analysis or downloaded as call logs (.TRC logs) for that instance.
• Viewing Error Messages, Possible Root Causes and Recommendations. 

A SIP Ladder diagram is not displayed if the Call Trace is not running and if the

Click the options available in a SIP Ladder Diagram to:

• View the exact timestamp next to each message (for example, INVITE, 200 OK, ACK and so on) in the SIP Ladder Diagram.
• View the IP Address and the Port for each leg of the call.
• View the request type for each message in the call.
• View and search the SIP PDU for each message in the call. The SIP PDU is shown as a tooltip when you hover the mouse pointer over the horizontal lines of the SIP Ladder diagram.
• View multiple SIP PDUs on the SIP ladder diagram at the same time.
• View the log information as a pop-up message when you click the horizontal lines in the SIP Ladder diagram. This log information is downloaded by clicking the Download button in the SIP Message detail pop-up window.
• View and search the log details from the TRC, DBG, and SYS logs for an individual message.
  • The log details will only be displayed for log lines that contain the GCID of the selected call within the selected time period.
  • For the first message, log details are displayed for the time between the message itself and the next message.
  • For the last message, log details are displayed for the time between the previous message and the message itself.
  • For all other messages, log details are displayed for the time between the previous message and the next.
• Download the log details from the TRC, DBG, and SYS logs for an individual message to a file.
  • The log details will only be displayed all log lines within the selected time period.
  • For the first message, log details are displayed for the time between the message itself and the next message.
  • For the last message, log details are displayed for the time between the previous message and the message itself.
  • For all other messages, log details are displayed for the time between the previous message and the next.
• Downloaded log contains all log lines. The complete log data can be sent to
  Unable to show "metadata-from": No such page "_space_variables"
   for evaluation if required.

• Display a tooltip with the details of each SIP Message when hover over the horizontal line below the respective SIP message in the SIP Ladder diagram. The following figure represents SIPing Ladder Tooltip:

   

  
  

• The user can download all the messages or the complete SIP PDU, which belong to the same call as presented in the SIP Ladder Diagram in a single file. The SBC provides the following information in the complete SIP PDU message:

  • CDRs at the beginning of the file
  • Directions of the messages (ingress/egress or received/sent)
  • Transport protocol (UDP/TCP/TLS/SCTP)
  • Date next to the time (part of timestamp)
  • IP addresses with the port numbers of the senders and receivers

  In the SIP Ladder Diagram, Select Download All to download all the messages in a single file. A pop-up window is displayed to download the complete SIP PDU. The following figure represents downloading the complete SIP PDU:

  

  
  By default, the complete SIP PDU message opens in .txt format. The following figure represents the Complete SIP PDU message:

  

• Displays a pop-up window with the SIP PDU when you click the SIP Message. SIP PDU can be downloaded as a .text file by clicking the Download button within the pop-up window. The SIP PDU pop-up window contains a search box, which is used to search and highlight the text present in the pop-up window. The following figure represents the SIP PDU pop-up window:
  

  

  The following figure represents the SIP PDU pop-up window showing the search box:
  
  

• Displays the log information as a pop-up message when you click the horizontal lines in the SIP Ladder diagram. This log information is downloaded by clicking the Download button in the SIP Message detail pop-up window. The log information pop-up window contains a search box, which is used to search and highlight the text present in the pop-up window.  The following figure represents log information:
   

  The following figure represents the log information pop-up window showing the search box:
  
  

    

  
  

SIP Ladder Performance Tests

The following table lists SIP Ladder performance test results on the 

• The data in the table below was generated from tests performed by the
  Unable to show "metadata-from": No such page "_space_variables"
   internal testing organization.
• Testing was done using the SIPP call simulator with simple calls.
• The tests measured CPU utilization, memory utilization and call failures. There was no system degradation for each test condition, and call failures were well within the acceptable limit.
• The SIP ladder diagram was verified to ensure that it was generated correctly under different test conditions.
• As of release 5.0,  call processing is separated from SIP ladder processing by allocating dedicated CPUs for each process. If the 50 cps limit for call trace is surpassed, SIP ladder processing may be affected with a delay in generating the SIP ladder diagram.
  

Load Duration/SPAM values are updated once the load is in use. The following table represents the SIP Ladder performance test results:

How to Increase CDR Repopulation Speed Post-Upgrade

After an upgrade, CDRs can take a lengthy amount of time (60+ minutes) to repopulate. Please note the following to resolve the issue:

• Repopulating CDRs is a CPU-intensive task. The CDR viewer and SIP ladder are not able to present all of the old information until the old ACT/TRC files are reprocessed and stored internally.
• Therefore, if the user does not require the old ACT/TRC files, then the user can delete those files prior to re-enabling the troubleshooting tools so there is less data to re-import. Deleting the ACT/TRC files will significantly increase CDR repopulation speed.
• The user must re-enable the troubleshooting tools post-upgrade. Also, the user is advised to re-enable the troubleshooting tools only during a maintenance window.