In this section:

Modified: for 9.0.3

The SBC SWe Lite and SBC 1000/2000 reports Voice Quality related information to the EdgeView SCC (Service Control Center) for operator reporting. The voice quality information is present in the media statistics of the stop CDR record; these reports are stored locally in the SBC and sent periodically (every 60 seconds) to EdgeView. When the SBC fails to log a Voice Quality CDR in a local file, an alarm is raised. The alarm is cleared when the Voice Quality CDRs are written to a local file.

When the Voice Quality data is received, EdgeView displays specific CDR fields for Voice Quality reporting for each leg of the call (such as latency, delay, jitter, packet loss, call duration, etc). EdgeView also offers the option to display the complete CDR and all call legs.

For additional information, see below.

Where to find Voice Quality Information

Voice Quality TopicWhere to Find
EdgeView DocumentationEdgeView 16.0.x Documentation.
SBC Edge AlarmsAlarms and Events Reference
SBC Edge CDR FieldsVendor Specific Attributes Reference

CDR Record Storage

The information below details how the SBC SWe Lite, SBC 1000 and SBC 2000 stores the CDR records

SBC SWe Lite

The CDR reports are stored locally in the SBC and sent periodically (every 60 seconds) to EdgeView. When the SBC fails to log a Voice Quality CDR in a local file, an alarm is raised. The alarm is cleared when the Voice Quality CDRs are written to a local file.

SBC 1000

The SBC 1000 checks for the presence of three areas in the priority order below. If there is any storage in the first URL, it is saved there. If not, the system checks the the 2nd URL, etc.  

  • /mnt/eusb
  • /mnt/ext
  • /mnt/core/asm

If there is storage found, the Voice Quality feature is enabled and the CDR reports are stored.  If none of the storage types are available, the CDR reports cannot be stored and the feature is not enabled on the SBC 1000.

The EVAgent periodically pings the radius process for any CDR reports; if storage is unavailable, the radius process does not return anything. In the case where storage is attached (i.e, external USB), the radius process detects it dynamically and responds with reports to the EVAgent.

SBC 2000

For SBC 2000 /mnt/eusb is used to store CDR files.

Example CDR Record in EdgeView

Below is an example of a CDR reported to EdgeView, both ingress and egress. These fields depend on the call scenario. 

Example SBC SWe Lite CDR Record in EdgeView

INGRESS Record

Egress Record

timestamp: "1594808934000",

timestamp: "1594808934000",

Acct-Status-Type: "2",

Acct-Status-Type: "2",

Acct-Session-Id: "15948088620000000000",

Acct-Session-Id: "15948088620000000001",

NET-Session-CallId: "0",

NET-Session-CallId: "1",

NET-Session-Generic-Id: "1",

NET-Session-Generic-Id: "1",

Acct-Multi-Session-Id: "15948089161",

Acct-Multi-Session-Id: "15948089161",

NET-Signaling-Group: "1",

NET-Signaling-Group: "2",

NET-Channel-Number: "1",

NET-Channel-Number: "1",

NET-Call-Origin: "1",

NET-Call-Origin: "2",

NET-Call-Type: "1",

NET-Call-Type: "1",

NET-Routing-Table-Number: "2",

NET-Routing-Table-Number: "0",

NET-Primary-Routing-Number: "+14000400001",

NET-Primary-Routing-Number: "+14000400001",

NET-Disconnect-Cause: "16",

NET-Disconnect-Cause: "16",

NET-Abort-Cause: "0",

NET-Abort-Cause: "0",

Acct-Terminate-Cause: "1",

Acct-Terminate-Cause: "1",

NET-Egress-Final-Routing-Num: "+14000400001",

NET-Egress-Final-Routing-Num: " ",

NET-Calling-Number: "+17069980467",

NET-Calling-Number: "+17069980467",

NET-Called-Number: "+14000400001",

NET-Called-Number: "+14000400001",

NET-Calling-Name: "5000500001",

NET-Calling-Name: "5000500001",

NET-Channel-Id: "0:1:1",

NET-Channel-Id: "0:2:1",

Acct-Output-Packets: "0",

Acct-Output-Packets: "0",

Acct-Output-Octets: "0",

Acct-Output-Octets: "0",

Acct-Input-Packets: "0",

Acct-Input-Packets: "0",

Acct-Input-Octets: "0",

Acct-Input-Octets: "0",

NET-Fwd-Flow-In-Src-Addr: "10.32.106.1",

NET-Fwd-Flow-In-Src-Addr: "10.33.5.61",

NET-Bwd-Flow-Out-Dst-Addr: "10.32.106.1",

NET-Bwd-Flow-Out-Dst-Addr: "10.33.5.61",

NET-Fwd-Flow-Out-Dst-Addr: "10.32.241.5",

NET-Fwd-Flow-Out-Dst-Addr: "10.33.5.5",

NET-Bwd-Flow-In-Src-Addr: "10.32.241.5",

NET-Bwd-Flow-In-Src-Addr: "10.33.5.5",

NET-Fwd-Flow-In-Dst-Addr: "10.32.106.1",

NET-Fwd-Flow-In-Dst-Addr: "10.32.106.1",

NET-Fwd-Flow-Out-Src-Addr: "10.32.106.1",

NET-Fwd-Flow-Out-Src-Addr: "10.32.106.1",

NET-Bwd-Flow-In-Dst-Addr: "10.32.106.1",

NET-Bwd-Flow-In-Dst-Addr: "10.32.106.1",

NET-Bwd-Flow-Out-Src-Addr: "10.32.106.1",

NET-Bwd-Flow-Out-Src-Addr: "10.32.106.1",

NET-Fwd-Flow-In-Src-Port: "16384",

NET-Bwd-Flow-In-Src-Port: "1090",

NET-Bwd-Flow-Out-Dst-Port: "1062",

NET-Fwd-Flow-Out-Src-Port: "16384",

NET-Bwd-Flow-Out-Src-Port: "16384",

NET-Bwd-Flow-In-Dst-Port: "1090",

NET-Fwd-Flow-Media-Type: "0",

NET-Fwd-Flow-Media-Type: "0",

NET-Fwd-Flow-PTime: "0",

NET-Fwd-Flow-PTime: "0",

NET-RTP-Avg-Latency: "0",

NET-RTP-Avg-Latency: "0",

NET-RTP-MaxLatency: "0",

NET-RTP-MaxLatency: "0",

NET-RTP-Avg-Jitter: "0",

NET-RTP-Avg-Jitter: "0",

NET-RTP-Avg-Remote-Jitter: "0",

NET-RTP-Avg-Remote-Jitter: "0",

NET-RTP-MaxJitter: "0",

NET-RTP-MaxJitter: "0",

NET-RTP-Packets-Lost: "0",

NET-RTP-Packets-Lost: "0",

NET-Fwd-Octets: "0",

NET-Bwd-Octets: "0",

NET-Fwd-Flow-In-Dst-Port: "1062",

NET-Fwd-Flow-Out-Dst-Port: "1090",

NET-Fwd-Packets: "0",

NET-Bwd-Packets: "0",

NET-Bwd-Max-Packet-Outage: "0",

NET-Bwd-Max-Packet-Outage: "0",

NET-Setup-Time: "1594808916000",

NET-Setup-Time: "1594808916000",

Acct-Session-Time: "3000",

Acct-Session-Time: "3000",

NET-Inbound-Seize-Time: "1594808917000",

NET-Outbound-Seize-Time: "1594808917000",

NET-Alert-Time: "1594808917000",

NET-Alert-Time: "1594808917000",

NET-Connect-Time: "1594808918000",

NET-Connect-Time: "1594808918000",

NET-Disconnect-Time: "1594808921000",

NET-Disconnect-Time: "1594808921000",

NET-Call-Duration: "3000",

NET-Call-Duration: "3000",

NET-Disconnect-Initiator: "1",

NET-Disconnect-Initiator: "0",

NET-Post-Dial-Delay: "615",

NET-Post-Dial-Delay: "94156",

NET-P-Preferred-ID: " ",

NET-P-Preferred-ID: " ",

NET-Replaced-Header: " ",

NET-Replaced-Header: " ",

NET-P-Asserted-ID: "<sip:+17069980467;oli=62;rn=+14043530000@one.att.net;user=phone>",

NET-P-Asserted-ID: "<sip:+17069980467;oli=62;rn=+14043530000@one.att.net;user=phone>",

NET-SIP-Diversion: " ",

NET-SIP-Diversion: " ",

NET-Local-Addr: "10.32.106.1",

NET-Local-Addr: "10.33.5.61",

NET-Remote-Addr: "10.32.241.5",

NET-Remote-Addr: "10.33.5.5",

NET-Net-Interface-Id: "37",

NET-Net-Interface-Id: "38",

NET-Refer-Call-Transfer-Id: " ",

NET-Refer-Call-Transfer-Id: " ",

NET-Session-Forked-Call-Id: " ",

NET-Session-Forked-Call-Id: "call-71280200-0000-0010-0312-1",

NET-Redirect-Number: " ",

NET-Redirect-Number: " ",

NET-Redirect-Ip-Address: " ",

NET-Redirect-Ip-Address: " ",

NET-Session-Realm: " ",

NET-Session-Realm: " ",

NET-Signaling-Port-Num: "5060",

NET-Signaling-Port-Num: "5060",

NET-Transport-Type: "1",

NET-Transport-Type: "1",

NET-Signaling-Remote-Port-Num: "10602",

NET-Signaling-Remote-Port-Num: "10606",

NET-SIP-Call-Id: "1-29320@10.32.241.5",

NET-SIP-Call-Id: "call-71280200-0000-0010-0312-1@10.33.5.61",

NET-Firmware-Version: "9.0.0v237",

NET-Firmware-Version: "9.0.0v237",

NET-Local-Time-Zone: "GMT0BST",

NET-Local-Time-Zone: "GMT0BST",

NET-Gw-Id: "2E09A05631BF9E27393F682B1ED60B42"

NET-Gw-Id: "2E09A05631BF9E27393F682B1ED60B42"