DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
In this section:
Only an Administrator and a Network Operator can access Troubleshooting setting (enabling/disabling). However, Guest User can view the CDR Viewer page and if enabled by the Administrator/Network Operator, Guest User can perform all the operations on the CDR Viewer page. If this option is disabled, the Guest User cannot enable Troubleshooting settings.
The CDR Viewer page is restricted for other User Groups like Security Auditor and Calea Users.
On the SBC main screen, navigate to Troubleshooting > Troubleshooting Tools > CDR Viewer.
CDR Viewer
The following CDR fields are available:
The user can capture and view the CDR event when polling is enabled. Refer to Dashboard - Live Monitor for more information on polling.
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 Troubleshooting page. The CDR records are fetched from ACT records which are generated by the SBC. If Polling is enabled, the CDR records are captured and stored into Database.
Enable-Disable CDR Data Polling
Enabling CDR Viewer on SBC SWe with less than 6 CPUs and less than 16 GB RAM may impact the system performance.
Filter the CDR list based on the following fields:
CDR Filter
Select any CDR record to view the details.
CDR Details
User can also search (case-insensitive) for a specific text within the record details of a selected CDR record.
CDR Search Using Find
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 Administrator and the Operators have the ability to change the settings for the CDR Viewer page.
The purge limits are set by the system and they are not user-configurable.
Peer IP Address
and it must be specified to trace calls. For more information on Level 4 Call Trace Filter, refer to Call Trace and Packet Capture - Call Trace.Message Length Limitation: The SIP Ladder diagram tool displays call messages by parsing message entries recorded in the trace (.TRC) log file. The TRC log has a message-size limit of 1800 bytes per entry, including a header which includes a time-stamp and sequence number. The header normally contributes fewer than 100 bytes. If a message within the call exceeds the 1800-byte limit, the TRC log divides it into two or more blocks and adds a header to each block. The SIP Ladder diagram cannot display the subsequent blocks of a message if it was divided into multiple blocks.
To enable/disable SIP Ladder, click the desired option as shown in the figure Enable-Disable SIP Ladder. By default, it is Disabled for Troubleshooting page. The CDR records are fetched from ACT records which are generated by the SBC. If Polling is enabled, the CDR records are captured and stored into Database.
Enable-Disable SIP Ladder
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.
SIP Ladder Diagram Icon
SIP Ladder Diagram
A SIP Call Ladder Diagram provides the following advantages:
.TRC
logs) for that instance.A SIP Ladder diagram is not displayed if the Call Trace is not running and if the SBC is not processing any calls for a minimum duration of two seconds.
Click the options available in a SIP Ladder Diagram to:
Display a tooltip with the details of each of the SIP Message when hovered over the horizontal line below the respective SIP message in the SIP Ladder diagram.
SIP 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 following information in the complete SIP PDU message:
In 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.
Downloading the Complete SIP PDU
By default, the complete SIP PDU message opens in .txt
format.
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 .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.
SIP PDU Pop-up Window
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. These log information is downloaded by clicking the Download button in 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.
Log Information
Log Information Pop-up Window Showing the Search Box
The following table lists SIP Ladder performance test results on the SBC ERE based on the following conditions.
The SBC 5xxx logs store approximately 1200 EVENTS per second combined for CDR viewer and SIP ladder functionality. These EVENTS includes CDR START, STOP, INTERMEDIATE, ATTEMPT records from the CDR viewer and all the SIP Requests and response messages from the SIP Ladder Diagram.
For example, on the SBC 5200 platform, when the traffic is running @ 400 cps, the number of CDR EVENTs generated per second = 800 (400 START + 400 STOP records).
Out of the 1200 supported EVENTS, the SBC receives 800 EVENTS per second for the CDR viewer. Thus, the SBC may log another 400 EVENTS per second for the SIP Ladder Diagram, which includes all the SIP requests and responses.
The basic SIP call contains seven EVENTS (INVITE, 100 Trying, 180, 200, ACK, BYE, 200). With the remaining 400 EVENTS logging available for SIP Ladder Diagram, the SBC supports approximately 50 simultaneous calls per second.
Key: E - Enabled D - Disabled |
Load Duration/SPAM values are updated once the load is executed.
SIP Ladder Performance Test Results
SBC Platform | RAM (GB) | Live Monitor | Troubleshooting | SIP Ladder | CPS | CHT (seconds) | Load Duration (hours) |
---|---|---|---|---|---|---|---|
5110 | 24 | E | E | E | 150 (SIP Ladder - 50) | 35 | 90 |
5210 | 24 | E | E | E | 450 (SIP Ladder - 50) | 70 | 72 |
5400 | 32 | E | E | E | 435 | 100 | 48 |
7000 | 128 | E | E | E | 200 (SIP Ladder - 50) | 30 | 12 |
7000 | 128 | D | E | E | 950 (SIP Ladder - 50) | 30 | 60 |
7000 | 128 | E | E | D | 1350 | 110 | 18 |
SWe (4vCPU) | 14 | E | E | E | 30 (SIP Ladder - 15) | 45 | 73 |
SWe (8vCPU) | 14 | E | E | E | 70 (SIP Ladder - 40) | 26 | 77 |
Column Descriptions
SBC Platform | Platform on which performance tests was done. |
RAM | Total RAM available in the SBC. |
Live Monitor | Indicates whether Live Monitor feature was enabled (E) or disabled (D). |
Troubleshooting | Indicates whether CDR Viewer feature was enabled (E) or disabled (D). |
SIP Ladder | Indicates whether SIP Ladder feature was enabled (E) or disabled (D). |
CPS | Indicates Calls Per seconds used. The number in the bracket indicates the calls for which SIP ladder was enabled. For example 150 (SIP Ladder - 50) indicates 150 calls per seconds out of which 50 calls were being traced for SIP ladder diagram. i.e. For 100 calls there were no matching call filter and for 50 of them there were matching call filter and SIP ladder was displayed for these 50 calls. |
CHT (seconds) | Indicates call hold time in seconds of each call. |
Load Duration | Indicates duration in hours for which the calls at the specified cps were run. |