Table Of Contents

show platform hardware qfp active feature sbc sfx

show sbc dbe addresses

show sbc dbe controllers

show sbc dbe flow-stats

show sbc dbe forwarder-stats

show sbc dbe h248-profile

show sbc dbe media-flow-stats

show sbc dbe media-stats

show sbc dbe signaling-flow-stats

show sbc rsrcmon

show sbc sbe aaa

show sbc sbe addresses

show sbc sbe adjacencies

show sbc sbe adjacencies authentication-realms

show sbc sbe all-authentication-realms

show sbc sbe billing remote

show sbc sbe blacklist configured-limits

show sbc sbe blacklist critical

show sbc sbe blacklist current-blacklisting

show sbc sbe blacklist ipv4

show sbc sbe cac-policy-set

show sbc sbe call branches

show sbc sbe call-policy-set

show sbc sbe call-policy-set tables

show sbc sbe call-policy-sets

show sbc sbe call-policy-set table entries

show sbc sbe call-policy-set table entry

show sbc sbe call-rate-stats

show sbc sbe calls

show sbc sbe call-stats

show sbc sbe codec-list

show sbc sbe gates

show sbc sbe h323 timers

show sbc sbe hold-media-timeout

show sbc sbe hunting-trigger

show sbc sbe media-gateway-associations

show sbc sbe media-gateways

show sbc sbe mib

show platform hardware qfp active feature sbc sfx

To display the Cisco QuantumFlow Processor SIP Fast-Register (SFX) counters, use the show platform hardware qfp active feature sbc sfx command in Privileged EXEC mode.

show platform hardware qfp active feature sbc sfx [global]

Syntax Description

global

Specifies SIP Fast-Register (SFX) global state information.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Usage Guidelines

Information about how SIP fast-register (SFX) messages are processed, that is, which SIP REGISTER request packets are punted to the Route Processor (RP) or dropped, may help explain why call rates are low and why the RP CPU load is high.

Examples

The following example shows information about the parsing of SIP fast-register (SFX) messages in the Cisco QuantumFlow Processor (QFP):

Router# show platform hardware qfp active feature sbc sfx global

SBC QFP SIP Fast Register Dataplane Information

-----------------------------------------------

  SIP 200 OK Replies generated                  = 0

  SIP REGISTER punts :

    No table entry                              = 0

    Fast Timer expiry                           = 0

    Expires=0                                   = 0

    SIP Syntax Error                            = 0

    QFP Out of Resources                        = 0

    QFP Internal Error                          = 0

  SIP REGISTER drops :

    QFP Internal Error                          = 0

    UDP Length Error                            = 0

    UDP Checksum Error                          = 0

Table 1 lists field descriptions for the show platform hardware qfp active feature sbc sfx command:

Table 1 show platform qfp active feature sbc sfx Field Descriptions 

Field	Description
SIP 200 OK Replies generated	A SIP REGISTER request was replied to in the QFP fast path using a 200 OK success reply.
SIP REGISTER punts
No table entry	A SIP REGISTER request could not be matched with a programmed SIP Fast-Register entry. This means that the combination of AoR (Address of Record, the To: field) and the Contact URI did not match any entry. The SIP REGISTER request is then punted to the Route Processor (RP).
Fast Timer expiry	When a SIP Fast-Register entry is added for fast-pathing the SIP REGISTER requests for the combination of AoR and Contact URI, a time limit for fast-pathing the re-REGISTER requests is set. When that time limit is exceeded, then the next SIP REGISTER request is punted to the RP.
Expires=0	A SIP REGISTER request was received with either an individual Contact specifying "expires=0" or with a SIP request global "Expires: 0" message header. The SIP REGISTER request is then punted to the RP.
SIP Syntax Error	A field in a SIP REGISTER message could not be parsed in the QFP fast path. The request is then punted to the RP.
QFP Out of Resources	A resource on the QFP could not be allocated to process a SIP REGISTER request. The request is then punted to the RP.
QFP Internal Error	An internal inconsistency in processing a SIP REGISTER request was encountered. The request is then punted to the RP for processing.
SIP REGISTER drops
QFP Internal Error	A failure to format the reply packet or to send the reply packet back was encountered. The request packet is dropped.
UDP Length Error	A packet's UDP length did not match the IP total length and is dropped.
UDP Checksum Error	The UDP checksum was incorrect in the SIP REGISTER packet. The packet is dropped.

Related Commands

Command	Description
clear platform hardware qfp active feature sbc sfx	Clears information about SIP fast-register (SFX) messages in the Cisco QuantumFlow Processor (QFP).

show sbc dbe addresses

To list the H.248 control addresses and media addresses configured on data border elements (DBEs), use the show sbc dbe addresses command in user EXEC or privileged EXEC mode.

show sbc {sbc-name} dbe addresses

Syntax Description

sbc-name

Name of the session border controller (SBC) service.

Command Default

No default behavior or values

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.1	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows the H.248 control and media addresses, VRF name, port ranges, and service class configured on a DBE that is on an SBC called "mySbc":

Router# show sbc mySbc dbe addresses

SBC Service "mySbc"

  H.248 control address:	10.0.0.1

Media-Address                    VRF                Port-Range   Service-Class

1.1.1.1                          Global             5-6          signaling

                                                    16384-20000  any

1.1.1.2-1.1.1.3                  Global             

1.1.1.5-1.1.1.6                  Global             

6::2-6::3                        Global             4-6          signaling

6::5                             Global             

1111:2222:3333:4444::1-1111:2222:3333:4444::5

                                 Global             2-6          signaling

1111:2222:3333:4444::8           Global             

Related Commands

Command	Description
show sbc dbe controllers	Displays the media gateway controllers and the controller address configured on each DBE.
show sbc dbe forwarder-stats	Displays the global list of statistics for the DBE forwarding process.
show sbc dbe media-stats	Displays general DBE statistics. These statistics do not include data from active calls.
show sbc dbe media-flow-stats	Displays the statistics about one or more media flows collected on the DBE.
show sbc dbe signaling-flow-stats	Displays the statistics about one or more signaling flows collected on the DBE.
unexpected-source-alerting	Enables the generation of alerts when media packets for a call are received from an unexpected source address and port.

show sbc dbe controllers

To list the media gateway controllers (MGCs) and the controller address configured on each data border element (DBE), use the show sbc dbe controllers command in user EXEC or privileged EXEC mode.

show sbc {sbc-name} dbe controllers

Syntax Description

sbc-name

Name of the session border controller (SBC) service.

Command Default

No default behavior or values

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.1	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Cisco IOS XE Release 2.2	Output was modified to add Session Establishment Time, Transaction Long Timer, and TMAX Timeout fields.
Cisco IOS XE Release 2.4	This command was modified for distributed SBC—output was modified to show Service Change Cold Boot delay timer information.

Examples

The following example shows that the controller is detached and a new field indicating that a delay timer is set to delay generation of a Service Change Cold Boot for 112 seconds was added in Cisco IOS XE Release 2.4 for distributed SBC:

Router# show sbc global dbe controllers

SBC Service "global"

  vDBE in DBE location 1

   DBE Admin Status:    Activation Delayed 112 seconds

    Media gateway controller in use:

      H.248 controller address

        200.50.1.254:2970

      Status:   Detached

                  Sent        Received    Failed      Retried

      Requests    1           0           0           1

      Replies     0           0                       0

    Segmentation:

      MGC PDU Size:  N/A

      MG PDU Size:   N/A

      MGC Seg timer: N/A

      MG Seg timer:  N/A

      Segments Sent: N/A

      Segments Rcvd: N/A

    Configured controllers:

      H.248 controller 2:

The following example shows that the controller is attached and a new field displaying the Session Establishment Time ("since 2008/02/19 13:56:30")that was added in Cisco IOS XE Release 2.2:

Router# show clock

*09:06:03.135 UTC Mon Feb 18 2008

Router# show sbc global dbe controllers

SBC Service "global"

  vDBE in DBE location 1

   DBE Admin Status:    Active

    Media gateway controller in use:

      H.248 controller address

        200.50.1.254:2970

      Status:   Attached, since 2008/02/19 13:56:30

                  Sent        Received    Failed      Retried

      Requests    1           0           0           1

      Replies     0           1                       0

    Segmentation:

      MGC PDU Size:  N/A

      MG PDU Size:   N/A

      MGC Seg timer: N/A

      MG Seg timer:  N/A

      Segments Sent: N/A

      Segments Rcvd: N/A

    Configured controllers:

      H.248 controller 2:

The following example establishes controller connection prior to the TMAX timeout being changed:

Router# show sbc global dbe controller

SBC Service "global"

  vDBE in DBE location 1

   DBE Admin Status:    Active

   DBE Transaction Long Timer 15000 (ms)

   DBE TMAX Timeout 10000 (ms)

    Media gateway controller in use:

      H.248 controller address

        200.50.1.254:2970

      Status:   Attached, since 2008/02/22 17:35:43

                  Sent        Received    Failed      Retried

      Requests    1           0           0           3

      Replies     0           1                       0

    Segmentation:

      MGC PDU Size:  N/A

      MG PDU Size:   N/A

      MGC Seg timer: N/A

      MG Seg timer:  N/A

      Segments Sent: N/A

      Segments Rcvd: N/A

    Configured controllers:

      H.248 controller 2:

        Remote address:    200.50.1.254:2970

        Transport:         UDP

The following example shows that the Tmax timeout has been changed to 20 seconds and entering the show controller command again displays the new fields, Transaction Long Timer and TMAX Timeout, added in Cisco IOS XE Release 2.2:

Router# show sbc global dbe controllers

SBC Service "global"

  vDBE in DBE location 1

   DBE Admin Status:    Active

   DBE Transaction Long Timer 25000 (ms)

   DBE TMAX Timeout 20000 (ms)

    Media gateway controller in use:

      H.248 controller address

        200.50.1.254:2970

      Status:   Detached

                  Sent        Received    Failed      Retried

      Requests    1           0           0           2

      Replies     0           0                       0

    Segmentation:

      MGC PDU Size:  N/A

      MG PDU Size:   N/A

      MGC Seg timer: N/A

      MG Seg timer:  N/A

      Segments Sent: N/A

      Segments Rcvd: N/A

    Configured controllers:

      H.248 controller 2:

        Remote address:    200.50.1.254:2970

        Transport:         UDP

The following example shows the H.248 controllers configured on the virtual data border element (vDBE) with a location ID of 1 on an SBC called "mySbc." In this example, the H.248 status is active.

Router# show sbc mySbc dbe controllers

SBC Service "mySbc"

  vDBE in DBE location 1

   DBE Admin Status:   Active

    Media gateway controller in use:

      H.248 controller address

        200.100.1.254:2991

      Status:            Detached

                  Sent        Received    Failed      Retried

      Requests    1           0           0           2

      Replies     0           0                       0

    Segmentation:

      MGC PDU Size:  33 bytes

      MG PDU Size:   N/A

      MGC Seg timer: 44 ms

      MG Seg timer:  N/A

      Segments Sent: N/A

      Segments Rcvd: N/A

    Configured controllers:

      H.248 controller 1:

        Remote address:    200.100.1.254:2991

        Transport:         UDP (with IAH)

The following example shows the H.248 controllers configured on the virtual data border element (vDBE) with a location ID of 1 on an SBC called "mySbc." In this example, the H.248 status is inactive.

Router# show sbc mySbc dbe controllers

SBC Service "mySbc"

  vDBE in DBE location 1

   DBE Admin Status:    Inactive

    Media gateway controller in use:

    Configured controllers:

      H.248 controller 5:

        Remote address:    10.1.1.1:6

        Transport:         UDP

Table 2 describes the significant fields shown in the display.

Table 2 show sbc dbe controllers Field Descriptions 

Field	Description
DBE Admin Status	Possible values are Active and Inactive.
Media gateway controller in use:	Statistics that follow are applicable to the MGC(s) in use.
H.248 controller address	H.248 controller address.
Status:	Status of the controller. Possible values are Attached and Detached.
Requests	Number of H.248 requests sent, received, failed, or retried.
Replies	Number of H.248 replies sent, received, failed, or retried.
Segmentation:	Statistics that follow are applicable to the H.248 Segmentation package.
MGC PDU Size	Maximum protocol data unit (PDU) size, in bytes, that the User Datagram Protocol (UDP) should use for H.248 control signaling.
MG PDU Size	Not applicable.
MGC Seg timer	Time interval, in milliseconds, on the segmentation timer.
MG Seg timer	Not applicable.
Segments Sent:	Number of segments sent.
Segments Rcvd:	Number of segments received.
Configured controllers:	Statistics that follow are applicable to configured H.248 controllers.
Remote address	Remote address of the configured controller.
Transport	Transport in use on the configured controller. Possible values are UDP, UDP (with IAH), TCP, and TCP (with IAH)
Session Establishment Time	This has the format (YY/MM/DD hour/minute/second). If the router time is changed, the operator is expected to detect this from any console log, as the Session Establishment Time is not updated.
Transaction Long Timer	This timer determines the total time the DBE waits (and keep retrying) from initially sending a request until receiving a response. It is set to TMAX + MaxRTT, where TMAX is configurable and MaxRTT is hard coded to 0.5 seconds. The association to the MGC is lost if this timer expires before the transaction reply is received.
TMAX Timeout	This is the maximum delay in seconds. It is a parameter of the TMAX timer that limits the maximum delay of retransmissions by the DBE when sending messages to the MGC. The default is 10 seconds.

Related Commands

Command	Description
show sbc dbe addresses	Displays the H.248 control addresses and media addresses configured on DBEs.
show sbc dbe forwarder-stats	Displays the global list of statistics for the DBE forwarding process.
show sbc dbe media-stats	Displays general DBE statistics. These statistics do not include data from active calls.
show sbc dbe media-flow-stats	Displays the statistics about one or more media flows collected on the DBE.
show sbc dbe signaling-flow-stats	Displays the statistics about one or more signaling flows collected on the DBE.
unexpected-source-alerting	Enables the generation of alerts when media packets for a call are received from an unexpected source address and port.

show sbc dbe flow-stats

To list all flow statistics, both signaling and media flows, collected on the data border element (DBE), use the show sbc dbe flow-stats command in user EXEC or privileged EXEC mode.

show sbc {sbc-name} dbe flow-stats [{summary | detail}] [vrf vrf-name] [ {ipv4 A.B.C.D | ipv6 ipv6-address} [port port-number]] [context {id}| termination {termination substring}]]

Syntax Description

sbc-name	Name of the session border controller (SBC) service.
summary	(Optional) Displays a summary of all flow statistics, including pinhole flows, for the DBE.
detail	(Optional) Displays detailed flow statistics, including pinhole flows, for the DBE.
vrf vrf-name	(Optional) Displays only flows to or from the specified VPN routing and forwarding instance (VRF).
ipv4 A.B.C.D	(Optional) Displays only flows to or from the specified IPv4 media IP address.
ipv6 ipv6-address	(Optional) Displays only flows to or from the specified IPv6 media IP address.
port port-number	(Optional) Displays only flows to or from the specified port number.
context	(Optional) Shows summary or detailed display of all pinhole flows within the context ID.
id	(Optional) Specifies the context ID number.
termination	(Optional) Shows summary or detailed display of pinhole flows that match the termination substring.
termination substring	(Optional) Specifies the termination substring number.

Command Default

No default behavior or values

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.2	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Cisco IOS XE Release 2.4	This command is supported for the unified model.

Usage Guidelines

The flow-stats per-flow counters are updated dynamically.

Not all endpoints report RTP Control Protocol (RTCP) endpoint statistics. In addition, not all endpoints that report RTCP statistics report all the fields shown.

When the "Media Flowing" field is reported as Yes, it either means that media has been observed flowing on the call within the media timeout period, or the call has failed over within the last media timeout period and the SBC has not yet had a chance to observe whether media is flowing or not.

Examples

The following example displays all the active flows, signaling and media flows:

Router# show sbc global dbe flow-stats

SBC Service "global"

Media flow statistics

  Media Flow:

    Context ID:          2

    Stream ID:           2

    State of Media Flow: Allocated

    Call Established Time: 15:27:27 PDT Apr 9 2008

    Flow Priority:       Unspecified

    Side A:

      Name                        mycompany/voice/gn/0/1/0/1/ac/3

      Reserved Bandwidth:         12600 (bytes/second)

      Status                      OutofService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.2.1

      Local Port:                 10002

      Remote Address:             10.10.127.22

      Remote Port:                17384

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      RTCP Packets Sent:          Not known

      RTCP Packets Received:      Not known

      RTCP Packets Lost:          Not known

      DTMF Interworking:          No

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Billing ID:                 000000000000000000000000000000000000000000000000

      Media directions allowed:   inactive

      Max Burst size:             0 (bytes)

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No 

    Side B:

      Name                        mycompany/voice/gn/0/2/0/1/bb/4

      Reserved Bandwidth:         12600 (bytes/second)

      Status                      OutofService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.2.1

      Local Port:                 10004

      Remote Address:             200.0.0.1

      Remote Port:                19384

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      RTCP Packets Sent:          Not known

      RTCP Packets Received:      Not known

      RTCP Packets Lost:          Not known

      DTMF Interworking:          No

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Billing ID:                 000000000000000000000000000000000000000000000000

      Media directions allowed:   inactive

      Max Burst size:             0 (bytes)

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No 

SBC Service "global"

Signaling flow statistics

  Media Flow:

    Context ID:          2

    Stream ID:           1

    State of Signaling Flow: Allocated

    Call Established Time: 15:24:38 PDT Apr 9 2008

    Flow Priority:       Unspecified

    Side A:

      Name                        mycompany/sip4/gn/0/1/0/1/ac/1

      Reserved Bandwidth:         0 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.2.1

      Local Port:                 10000

      Remote Address:             3.0.0.3

      Remote Port:                5000

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Max Burst size:             0 (bytes)

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No 

Side B:

      Name                        mycompany/sip4/gn/0/1/0/1/bb/2

      Reserved Bandwidth:         0 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.2.1

      Local Port:                 10001

      Remote Address:             3.0.0.3

      Remote Port:                5000

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Max Burst size:             0 (bytes)

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        B8

      Media Loss Event:           No

      NAT Latch Event:            No

The following example displays a summary of all flows with context ID number 1:

Router# show sbc global dbe flow-stats summary context 1

SBC Service "global"

Media flow statistics

    Context ID 1                Stream ID 2

    Side A:             Name mycompany/voice/gn/0/1/0/1/ac/3    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10002

      Remote Address/Port: 10.10.127.22/17384

      Status:              OutofService

    Side B:             Name mycompany/voice/gn/0/2/0/1/bb/4    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10004

      Remote Address/Port: 200.0.0.1/19384

      Status:              OutofService

SBC Service "global"

Signaling flow statistics

    Context ID 1                Stream ID 1

    Side A:             Name mycompany/sip4/gn/0/1/0/1/ac/1    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10000

      Remote Address/Port: 3.0.0.3/5000

      Status:              InService

    Side B:             Name mycompany/sip4/gn/0/1/0/1/bb/2    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10001

      Remote Address/Port: 3.0.0.3/5000

      Status:              InService

The following example displays a summary of flows with the termination string, mycompany:

Router# show sbc global dbe flow-stats summary termination mycompany

SBC Service "global"

Media flow statistics

    Context ID 1                Stream ID 2

    Side A:             Name mycompany/voice/gn/0/1/0/1/ac/3    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10002

      Remote Address/Port: 10.10.127.22/17384

      Status:              OutofService

    Side B:             Name mycompany/voice/gn/0/2/0/1/bb/4    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10004

      Remote Address/Port: 200.0.0.1/19384

      Status:              OutofService

SBC Service "global"

Signaling flow statistics

    Context ID 1                Stream ID 1

    Side A:             Name mycompany/sip4/gn/0/1/0/1/ac/1    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10000

      Remote Address/Port: 3.0.0.3/5000

      Status:              InService

    Side B:             Name mycompany/sip4/gn/0/1/0/1/bb/2    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10001

      Remote Address/Port: 3.0.0.3/5000

      Status:              InService

The following example displays a summary of flows with the combination of context ID 1 and the termination string, mycompany:

Router# show sbc global dbe flow-stats summary context 1 termination mycompany

SBC Service "global"

Media flow statistics

    Context ID 1                Stream ID 2

    Side A:             Name mycompany/voice/gn/0/1/0/1/ac/3    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10002

      Remote Address/Port: 10.10.127.22/17384

      Status:              OutofService

    Side B:             Name mycompany/voice/gn/0/2/0/1/bb/4    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10004

      Remote Address/Port: 200.0.0.1/19384

      Status:              OutofService

SBC Service "global"

Signaling flow statistics

    Context ID 1                Stream ID 1

    Side A:             Name mycompany/sip4/gn/0/1/0/1/ac/1    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10000

      Remote Address/Port: 3.0.0.3/5000

      Status:              InService

    Side B:             Name mycompany/sip4/gn/0/1/0/1/bb/2    Media Flowing:  No

      Local Address/Port:  202.50.2.1/10001

      Remote Address/Port: 3.0.0.3/5000

      Status:              InService

Table 3 show sbc dbe flow-stats Field Descriptions 

Field	Description
Context ID	The context ID to which the flow is associated.
Stream ID	Stream ID.
State of Media Flow	Flow (or Termination) state (Active, Allocated, or Unknown). Active—The DBE has programmed the flow pair and media has started flowing in at least one direction. Allocated—The DBE has programmed the flow pair, but no media has started to flow. Unknown—The DBE has not yet been given enough information by the controller to be able to program the flow pair.
State of Signaling Flow	Flow state (Active, Allocated, or Unknown). •Active—DBE has programmed the flow pair and the media has started flowing in at least one direction. •Allocated—DBE has programmed the flow pair, but no media has started to flow. •Unknown—DBE has not yet been given enough information by the controller to be able to program the flow pair.
Call Established Time	Call established time in the format 23:51:29 UTC Jun 21 2007.
Flow Priority	Priority of the call (Routine or Urgent).
Side A	Information for the initiating side of the call.
Side B	Information for the terminating side of the call.
Name	Name of the flow.
Reserved Bandwidth	Bandwidth reserved for the call in bytes per second. (This value maps to the tman/sdr value.)
Status	Status is InService or OutofService. InService—Flow on this side is in service. OutofService—No media is forwarded.
VRF Name	Either the VRF name, or "Global" when there is no VRF.
VLAN Tags (Priorities)	VLAN tags and Ethernet priorities information.
Local Address	Local address on the DBE on which packets are received for this side of the call.
Local Port	Local port on the DBE on which packets are received for this side of the call.
Remote Address	Address of the remote endpoint from which packets are expected to be sent for this side of the call.
Remote Port	Port on the remote endpoint from which packets are expected to be sent for this side of the call.
Remote Source Address Mask	If specified, all packets matching the Remote Source Address Mask are classified as belonging to this flow rather than just those matching the full remote and port. (This value maps to the gm/sam value.)
Packets Received	Number of packets received from the remote endpoint.
Packets Sent	Number of packets forwarded to the remote endpoint.
Packets Discarded	Number of packets dropped (due to bandwidth policing, for example).
Data Received	Number of bytes of data received from the remote endpoint.
Data Sent	Number of bytes of data forwarded to the remote endpoint.
Data Discarded	Number of bytes of data dropped (due to bandwidth policing, for example). (This value maps to the gm/sam value.)
GM Discarded Packets	This counter is always set to zero because it is not currently implemented. It will be the number of data packets received from the remote endpoint that have been discarded locally because of source address/port filtering.
Time To Recovery	The tsc/ttr value from Termination State Control (TSC) package, in milliseconds.
RTCP Packets Sent	If there are RTCP packets flowing in the call, the number of RTP packets (within the most recently received RTCP) that the endpoint reports as being sent.
RTCP Packets Received	If there are RTCP packets flowing in the call, the number of RTP packets (within the most recently received RTCP) that the endpoint reports as being received.
RTCP Packets Lost	If there are RTCP packets flowing in the call, the number of RTP packets (within the most recently received RTCP) that the endpoint reports as being lost.
DTMF Interworking	Indicates whether DTMF interworking is in operation for the flow.
Media Flowing	Indicates whether packets are flowing from the endpoint.
Unexpected SrcAddr Packets	If unexpected-source-alerting is switched on with the unexpected-source-alerting command, this counter records the number of alerts generated for the flow when media packets for a call are received from an unexpected source address and port. An unexpected source event happens when a packet is received, matched to a flow (but not by a full 5-tuple comparison), and found to have come from the wrong remote address.
Delay variation tolerance	The delay variation tolerance (tman/dvt) associated with the Tman package. Defines the delay variation tolerance for the stream in tenths of microseconds when enforcing the PDR value in the first leaky bucket.
SDP string	The SDP string is that present on the H.248 ADD request to provision the call.
Graceful deactivation	Description to be added.
DiffServ Code Point	The Diffserv Code point is the (DSCP value) provided on the H.248 request to mark the media packets. This reflects the ds/dscp parameters.
Media Loss Event	Media Loss Event is "Yes" if the flow has the nt/qualert subscription.
NAT Latch Event	The NAT Latch Event is "Yes" if the flow has adr/rsac subscribed.
Billing ID	Signaling border element (SBE) billing ID for this side of the call.
Media directions allowed	Allowed directions of media flow for this side of the call (inactive, sendonly, recvonly, or sendrecv).

Related Commands

Command	Description
show sbc dbe addresses	Displays the H.248 control addresses and media addresses configured on DBEs.
show sbc dbe controllers	Displays the media gateway controllers and the controller address configured on each DBE.
show sbc dbe forwarder-stats	Displays the global list of statistics for the DBE forwarding process.
show sbc dbe media-stats	Displays general DBE statistics. These statistics do not include data from active calls.
show sbc dbe signaling-flow-stats	Displays the statistics about one or more signaling flows collected on the DBE.
unexpected-source-alerting	Enables the generation of alerts when media packets for a call are received from an unexpected source address and port.

show sbc dbe forwarder-stats

To display the global list of statistics for the DBE forwarding process, use the show sbc dbe forwarder-stats command in user EXEC mode or privileged EXEC mode.

show sbc {sbc-name} dbe forwarder-stats

Syntax Description

sbc-name

Name of the session border controller (SBC) service.

Command Default

No default behavior or values

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.1	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Cisco IOS XE Release 2.4	Added "Packets violated" field.

Usage Guidelines

This command provides a live snapshot of the current state of the DBE forwarding process by showing low-level statistics on the packets processed by the process. This command is intended to be used by Cisco customer support engineers to diagnose media problems.

Because DBE forwarding statistics can overwrite after approximately 4 billion packets, overall packet counts might not be accurate. For more accurate statistics on completed calls, use the show sbc dbe media-stats command. For accurate information on active flows, use the show sbc dbe media-flow-stats command.

Examples

The following example shows the list of statistics for the DBE forwarding process:

Router# show sbc global dbe forwarder-stats

IOSd MPF Stub Message statistics

--------------------------------

Total global PMI messages received         = 1

Total global PMI messages transmitted      = 1

Total call PMI messages received           = 0

Total call PMI messages transmitted        = 0

Total global PMI message handling failures = 0

Total call PMI message handling failures   = 0

Total global TDL messages received         = 1

Total global TDL messages transmitted      = 1

Total call TDL messages received           = 0

Total call TDL messages transmitted        = 0

Total global TDL message handling failures = 0

Total call TDL message handling failures   = 0

Total packets injected                     = 0

Total packets punted                       = 0

Total injected packets dropped             = 0

Total punted packets dropped               = 0

Total global message timeouts              = 0

Total call message timeouts                = 0

Call ID database is NOT Initialised

IOSd MPF Stub Call statistics

-----------------------------

Number of currently in-use Calls           = 0

High-water number of in-use Calls          = 0

Maximum number of in-use Calls supported   = 0

SBC Media Forwarder Statistics

------------------------------

Summary information:

  Total packets received                      = 28416

  Total packets forwarded                     = 14336

  Total packets dropped                       = 14080

  Total packets punted                        = 0

  Incoming packets diverted to SBC subsystem  = 0

  Outgoing packets inserted by SBC subsystem  = 0

Detailed breakdown of statistics:

Dropped packets:

  IP TTL expired                              = 0

  No associated flow                          = 0

  Wrong source for flow                       = 0

  Ingress flow receive disabled               = 0

  Egress flow send disabled                   = 0

  Not conforming to flowspec                  = 14080

  Badly formed RTP                            = 0

  Badly formed RTCP                           = 0

  Excessive RTCP packet rate                  = 0

  Borrowed for outgoing DTMF                  = 0

  Unknown destination address                 = 0

  Misdirected                                 = 0

  Feature disabled                            = 0

  Reprocess limit exceeded                    = 0

Punted packets:

  H.248 control packets                       = not implemented

  Packets containing options                  = 0

  Fragmented packets                          = 0

  Unexpected IP protocol                      = 0

  Packets from invalid port range             = 0

Punted packets dropped through rate limiting  = 0

Packets colored with configured DSCP          = 0

Diverted DTMF packets dropped:

  Excessive DTMF packet rate                  = 0

  Bad UDP checksum                            = 0

  Diverted packet queue full                  = not implemented

  Other                                       = not implemented

Inserted packets dropped:

  Flow inactive or disabled                   = 0

  No outgoing packet buffer available         = 0

  Outgoing Queue full                         = 0

  Other                                       = 0

Generated event information:

  Number of media UP events                   = 0

  Number of media DOWN events                 = 0

  Number of unexpected source events          = 0

Platform specific statistics:

  Packets learn source address                = 0

  Packets Learn source address timed out      = 0

  Packets conformed                           = 1982

  Packets violated                            =   18

  Packets exceed                              = 0

  Packets RTCP receive                        = 0

SBC Media Forwarder statistics can wrap after

approximately 18 quintillion packets.  For more accurate

statistics on completed calls, please use

  show sbc ... dbe media-stats

Table 4 show sbc dbe forwarder-stats Field Descriptions 

Field	Description
IOSd MPF Stub Message statistics
Total global PMI messages received	Total global packet management interface (PMI) messages received by the DBE forwarding process. This counter increments during normal operation.
Total global PMI messages transmitted	Total global packet management interface (PMI) messages transmitted by the DBE forwarding process. This counter increments during normal operation.
Total call PMI messages received	Total packet management interface (PMI) messages related to calls received by the DBE forwarding process. This counter increments during normal operation.
Total call PMI messages transmitted	Total packet management interface (PMI) messages related to calls transmitted by the DBE forwarding process. This counter increments during normal operation.
Total global PMI message handling failures	Failure counters indicating that something has gone wrong with handling total global packet management interface (PMI) messages. The suggested action is to monitor the counters and if they are increasing or are associated with another failure, then call TAC.
Total call PMI message handling failures	Failure counters indicating that something has gone wrong with handling total packet management interface (PMI) messages related to calls. The suggested action is to monitor the counters and if they are increasing or are associated with another failure, then call TAC.
Total global TDL messages received	Total global type definition language (TDL) messages received by the DBE forwarding process. This counter increments during normal operation.
Total global TDL messages transmitted	Total global type definition language (TDL) messages transmitted by the DBE forwarding process. This counter increments during normal operation.
Total call TDL messages received	Total type definition language (TDL) messages related to calls received by the DBE forwarding process. This counter increments during normal operation.
Total call TDL messages transmitted	Total type definition language (TDL) messages related to calls transmitted by the DBE forwarding process. This counter increments during normal operation.
Total global TDL message handling failures	Failure counters indicating that something has gone wrong with handling total global type definition language (TDL) messages. The suggested action is to monitor the counters and if they are increasing or are associated with another failure, then call TAC.
Total call TDL message handling failures	Failure counters indicating that something has gone wrong with handling total type definition language (TDL) messages related to calls. The suggested action is to monitor the counters and if they are increasing or are associated with another failure, then call TAC.
Total packets injected	Total dual-tone multifrequency (DTMF) packets inserted into the Real-time Transport Protocol (RTP) stream. If DTMF interworking is configured, then these counters are expected to increase.
Total packets punted	Total dual-tone multifrequency (DTMF) packets removed from the Real-time Transport Protocol (RTP) streams. If DTMF interworking is configured, then these counters are expected to increase.
Total injected packets dropped	Failure counters indicating that something has gone wrong—total DTMF packets inserted into RTP streams that have dropped. The suggested action is to monitor the counters and if they are increasing or are associated with another failure, then call TAC.
Total punted packets dropped	Failure counters indicating that something has gone wrong—total DTMF packets removed from RTP streams that have dropped. The suggested action is to monitor the counters and if they are increasing or are associated with another failure, then call TAC.
IOSd MPF Stub Call statistics
Number of currently in-use Calls	Number of calls currently in use.
High-water number of in-use Calls	The maximum number of calls that have ever been in use.
Maximum number of in-use Calls supported	This will only be filled in once the Call IS database moves to initialized state.
SBC Media Forwarder Statistics Summary information
Total packets received	Total packets received by the DBE forwarding process.
Total packets forwarded	Total packets forwarded by the DBE forwarding process.
Total packets dropped	Total packets dropped by the DBE forwarding process for any reason.
Total packets punted	Total packets punted to the IP stack by the DBE forwarding process.
Incoming packets diverted to SBC subsystem	Number of incoming packets diverted to the Media Gateway Manager (MGM).
Outgoing packets inserted by SBC subsystem	Number of outgoing packets inserted by MGM.
Detailed breakdown of statistics
Dropped packets
IP TTL expired	Number of packets rejected by DBE forwarding process and dropped because the IP time to live (TTL) has expired.
No associated flow	Number of packets rejected by DBE forwarding process and dropped because they do not correspond to a matching media flow.
Wrong source for flow	Number of packets rejected by DBE forwarding process and dropped because the source IP address and source port do not match the expected source address and source port for the flow.
Ingress flow receive disabled	Number of packets rejected by DBE forwarding process and dropped because receiving packets from the remote endpoint is disabled.
Egress flow send disabled	Number of packets rejected by DBE forwarding process and dropped because sending packets to the remote endpoint is disabled.
Not conforming to flowspec	Number of packets rejected by DBE forwarding process and dropped because they do not conform according to flowspec traffic policing for the flow. A flowspec is the traffic parameters of a stream of IP packets between two applications in IPv6 or IPv4.
Badly formed RTP	Number of packets rejected by DBE forwarding process and dropped due to Real Time Protocol (RTP) errors.
Badly formed RTCP	Number of packets rejected by DBE forwarding process and dropped due to Real Time Control Protocol (RTCP) errors.
Excessive RTCP packet rate	Number of RTCP packets rejected by DBE forwarding process and dropped because too many RTCP packets were sent on a given flow; policer indicated violated the flow specifier. The DBE forwarding process allows two RTCP packets per second for each flow.
Borrowed for outgoing DTMF	Number of packets rejected by DBE forwarding process and dropped because they were borrowed from their own flow in order to allow an outgoing packet to be inserted into a flow.
Unknown destination address	Number of packets rejected by DBE forwarding process and dropped because the destination address is unknown.
Misdirected	Number of packets that was dropped due to having an address that would have caused the packets to be punted.
Feature disabled	Number of packets that was received while SBC was in the process of being deactivated. Depending on the volume of traffic, this number will remain small. This counter only increments during the deactivation process. Once the feature (SBC) is fully deactivated (with the no activate command), this counter will no longer increment.
Reprocess limit exceeded	Error condition counter. Counts errors when an SBC packet is re-processed too many times because the destination address was changed to be a local address on the DBE. After the destination address is translated and forwarded, the packet ends up in the SBC path again. This counter does not typically increase.
Punted packets
H.248 control packets	Not implemented in command output.
Packets containing options	Number of packets rejected by DBE forwarding process and punted because the IP header contains IP options.
Fragmented packets	Number of packets rejected by DBE forwarding process and punted to the IP stack because the IP datagram is fragmented.
Unexpected IP protocol	Number of packets rejected by DBE forwarding process and punted because they are neither UDP nor TCP, or they are TCP but they are not destined for a signaling pinhole.
Packets from invalid port range	Number of packets rejected by DBE forwarding process and punted because the destination UDP port is outside the VoIP UDP port range.
Punted packets dropped through rate limiting	Number of packets not punted to the IP stack and dropped due to rate limiting.
Packets colored with configured DSCP	Number of packets colored with configured marker DSCP value by Two-Rate-Three-Color Marker feature.
Diverted DTMF packets dropped
Excessive DTMF packet rate	Number of incoming packets diverted to MGM but dropped due to rate limiting. These packets are included in the divert count and drop count.
Bad UDP checksum	The UDP checksum was incorrect in the DTMF packet. The packet is dropped.
Diverted packet queue full	Not implemented in command output.
Other	Not implemented in command output.
Inserted packets dropped
Flow inactive or disabled	Number of outgoing packets inserted by MGM but dropped because the request is invalid. These packets are included in the insert count and drop count.
No outgoing packet buffer available	Number of outgoing packets inserted by MGM but dropped because no packet buffers are available. These packets are included in the insert count and drop count.
Outgoing Queue full	Number of outgoing packets inserted by MGM but dropped because the outgoing packet queue is full. These packets are included in the insert count and drop count.
Other	Number of outgoing packets inserted by MGM but dropped for other reasons. These packets are included in the insert count and drop count.
Generated event information
Number of media UP events	Number of media UP events generated.
Number of media DOWN events	Number of media DOWN events generated.
Number of unexpected source events	Number of unexpected source address events generated.
Platform specific statistics
Packets learn source address	For flows that have source address latching configured, a count of the number of packets that are latched.
Packets Learn source address timed out	If a flow has be programmed to relatch the source address and a new source address was not received in the specified timeframe, then this counts the timeout.
Packets conformed	Count of the number of packets that the policer indicated conformed to the flow specifier.
Packets violated	Count of the number of packets that the policer indicated violated the flow specifier.
Packets exceed	Count of the number of packets that the policer indicated exceeded the flow specifier
Packets RTCP receive	Count of the number of RTCP packets received.

Related Commands

Command	Description
show sbc dbe addresses	Displays the H.248 control addresses and media addresses configured on DBEs.
show sbc dbe controllers	Displays the media gateway controllers and the controller address configured on each DBE.
show sbc dbe media-flow-stats	Displays the statistics about one or more media flows collected on the DBE.
show sbc dbe media-stats	Displays general DBE statistics. These statistics do not include data from active calls.
show sbc dbe signaling-flow-stats	Displays the statistics about one or more signaling flows collected on the DBE.

show sbc dbe h248-profile

To list the information on the specified H.248 profile, including transport, H.248 form, and active packages, use the show sbc dbe h248-profile command in the Privileged EXEC mode.

show sbc sbc-name dbe h248-profile

Syntax Description

sbc-name

Defines the name of the service.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows the defaults and configured options for the H.248 profile:

Router# show sbc mysbc dbe h248-profile

Transport UDP IAH

H.248 Version 3

Packages:

Generic(g)

Base Root(root): Max Terminations per context 10

Network(l)

DiffServ(ds)

Gate Management(gm)

Traffic Management(tman)

IP NAPT(ipnapt)

Segment(seg): Max PDU Size 4096 bytes

Related Commands

Command	Description
h248-profile	Configures the vDBE H.248 profile name to interoperate with the MGC.
h248-profile-version	Configures the vDBE H.248 profile version to interoperate with the MGC. This command is used after you have defined the name of the profile using the h248-profile command.

show sbc dbe media-flow-stats

To list the media flow statistics collected on the data border element (DBE), use the show sbc dbe media-flow-stats command in user EXEC or privileged EXEC mode.

show sbc {sbc-name} dbe media-flow-stats [{summary | detail}] [vrf vrf-name] [ {ipv4 A.B.C.D | ipv6 ipv6-address} [port port-number]] [context {id}| termination {termination substring}]]

Syntax Description

sbc-name	Name of the session border controller (SBC) service.
summary	(Optional) Displays a summary of the media flow statistics, including pinhole flows, for the DBE.
detail	(Optional) Displays detailed media statistics, including pinhole flows, for the DBE.
vrf vrf-name	(Optional) Displays only media flows to or from the specified VPN routing and forwarding instance (VRF).
ipv4 A.B.C.D	(Optional) Displays only media flows to or from the specified IPv4 media IP address.
ipv6 ipv6-address	(Optional) Displays only media flows to or from the specified IPv6 media IP address.
port port-number	(Optional) Displays only media flows to or from the specified port number.
context	(Optional) Shows summary or detailed display of all pinhole flows within the context ID.
id	(Optional) Specifies the context ID number.
termination	(Optional) Shows summary or detailed display of pinhole flows. that match the termination substring.
termination substring	(Optional) Specifies the termination substring number.

Command Default

No default behavior or values

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.1	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Cisco IOS XE Release 2.2	The context and termination keywords were added. New fields (Max Burst size, Delay variation tolerance, SDP string, Graceful deactivation, DiffServ Code Point, Media Loss Event, and NAT Latch Event) were added to the ouput display.
Cisco IOS XE Release 2.4	This command is supported for the unified model.

Usage Guidelines

Not all endpoints report RTP Control Protocol (RTCP) endpoint statistics. In addition, not all endpoints that report RTCP statistics report all the fields shown.

When the "Media Flowing" field is reported as Yes, it either means that media has been observed flowing on the call within the media timeout period, or the call has failed over within the last media timeout period and the SBC has not yet had a chance to observe whether media is flowing or not.

Examples

The following example displays signaling and media flow pairs and additional fields added in Cisco IOS XE Release 2.2:

Router# show sbc global dbe media-flow-stats

SBC Service "global"

  Media Flow:

    Context ID:          6

    Stream ID:           2

    State of Media Flow: Allocated

    Call Established Time: 16:54:29 UTC Feb 20 2008

    Flow Priority:       Unspecified

    Side A:

      Name                        mycompany/voice/gn/0/1/0/1/ac/3

      Reserved Bandwidth:         12600 (bytes/second)

      Status                      OutofService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.2.1

      Local Port:                 10002

      Remote Address:             10.10.127.22

      Remote Port:                17384

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      RTCP Packets Sent:          Not known

      RTCP Packets Received:      Not known

      RTCP Packets Lost:          Not known

      DTMF Interworking:          No

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Billing ID:                 000000000000000000000000000000000000000000000000

      Media directions allowed:   inactive

      Max Burst size:             3250 (bytes)         <===== additional fields for side A

      Delay variation tolerance:  0 (ms)

      SDP string:                 m=audio $ RTP/AVP 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No                     

Side B:

      Name                        mycompany/voice/gn/0/2/0/1/bb/4

      Reserved Bandwidth:         12600 (bytes/second)

      Status                      OutofService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.2.1

      Local Port:                 10004

      Remote Address:             200.0.0.1

      Remote Port:                19384

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      RTCP Packets Sent:          Not known

      RTCP Packets Received:      Not known

      RTCP Packets Lost:          Not known

      DTMF Interworking:          No

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Billing ID:                 000000000000000000000000000000000000000000000000

      Media directions allowed:   inactive

      Max Burst size:             3250 (bytes)         <===== additional fields for Side B

      Delay variation tolerance:  0 (ms)

      SDP string:                 m=audio $ RTP/AVP 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No

The following example shows detailed statistics from an IPv4 media flow collected on the DBE:

Router# show sbc mySbc dbe media-flow-stats detail

SBC Service "mySbc"

  Media Flow:

    Context ID:          1

    Stream ID:           2

    State of Media Flow: Active

    Call Established Time: 23:50:20 UTC Jun 21 2007

    Flow Priority:       Routine

    Side A:

      Name                        abc/voice/gn/0/1/0/1/ac/3

      Reserved Bandwidth:         12 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.255.113

      Local Port:                 20000

      Remote Address:             100.50.255.110

      Remote Port:                20000

      Remote Source Address Mask: 100.50.255.0/24

      Packets Received:           2272

      Packets Sent:               1784

      Packets Discarded:          0

      Data Received:              266 (bytes)

      Data Sent:                  209 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      RTCP Packets Sent:	 Not known

      RTCP Packets Received:	 Not known

      RTCP Packets Lost:	 Not known

      DTMF Interworking:          No

      Media Flowing:              Yes

      Unexpected SrcAddr Packets: No

      Billing ID:                 000000000000000000000000000000000000000000000000

      Media directions allowed:  sendrecv

      Max Burst size:             3250 (bytes)         <===== additional fields for side A

      Delay variation tolerance:  0 (ms)

      SDP string:                 m=audio $ RTP/AVP 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No                     

    Side B:

      Name                        abc/voice/gn/0/1/0/1/bb/4

      Reserved Bandwidth:         23 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.255.113

      Local Port:                 20002

      Remote Address:             200.50.255.110

      Remote Port:                30000

      Packets Received:           2249

      Packets Sent:               2272

      Packets Discarded:          465

      Data Received:              263 (bytes)

      Data Sent:                  266 (bytes)

      Data Discarded:             54 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      RTCP Packets Sent:	 Not known

      RTCP Packets Received:	 Not known

      RTCP Packets Lost:	 Not known

      DTMF Interworking:          No

      Media Flowing:              Yes

      Unexpected SrcAddr Packets: No

      Billing ID:                 000000000000000000000000000000000000000000000000

      Media directions allowed:  sendrecv

      Max Burst size:             3250 (bytes)         <===== additional fields for side B

      Delay variation tolerance:  0 (ms)

      SDP string:                 m=audio $ RTP/AVP 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No                     

The following example shows detailed statistics from an IPv6 media flow collected on the DBE:

Router# show sbc mySbc dbe media-flow-stats detail

SBC Service "mySbc"

  Media Flow:

    Context ID:          13

    Stream ID:           2

    State of Media Flow: Allocated

    Call Established Time: 23:51:29 UTC Jun 21 2007

    Flow Priority:       Routine

    Side A:

      Name                        abc/voice/gn/0/1/0/1/ac/1

      Reserved Bandwidth:         23 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:           3333:1111:1111:2222:3333:4444:5555:7777

      Local Port:                 30000

      Remote Address:          2222:1111:1111:2222:3333:4444:5555:7777

      Remote Port:                20000

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      RTCP Packets Sent:	 Not known

      RTCP Packets Received:	 Not known

      RTCP Packets Lost:	 Not known

      DTMF Interworking:          No

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Billing ID:                 000000000000000000000000000000000000000000000000

      Media directions allowed:  sendrecv

      Max Burst size:             3250 (bytes)         <===== additional fields for side A

      Delay variation tolerance:  0 (ms)

      SDP string:                 m=audio $ RTP/AVP 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No                     

    Side B:

      Name                        abc/voice/gn/0/1/0/1/bb/2

      Reserved Bandwidth:         12 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:           2222:1111:1111:2222:3333:4444:5555:7777

      Local Port:                 20000

      Remote Address:          3333:1111:1111:2222:3333:4444:5555:7777

      Remote Port:                30000

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      RTCP Packets Sent:	 Not known

      RTCP Packets Received:	 Not known

      RTCP Packets Lost:	 Not known

      DTMF Interworking:          No

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Billing ID:                 000000000000000000000000000000000000000000000000

      Media directions allowed:  sendrecv

      Max Burst size:             3250 (bytes)         <===== additional fields for side B

      Delay variation tolerance:  0 (ms)

      SDP string:                 m=audio $ RTP/AVP 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No                     

The following example shows summary statistics collected for media flows on the DBE:

Router# show sbc mySbc dbe media-flow-stats summary

SBC Service "mySbc"

    Context ID 1                Stream ID 2

    Side A:             Name abc/voice6/gn/0/1/0/1/ac/3    Media Flowing:  No

      Local Address/Port:  3:100:1:1:1:1:1:1/30000

      Remote Address/Port: 2:100:1:1:1:1:1:1/20000

      Status:              In Service

    Side B:             Name abc/voice6/gn/0/1/0/1/bb/4    Media Flowing:  No

      Local Address/Port:  2:100:1:1:1:1:1:1/20000

      Remote Address/Port: 3:100:1:1:1:1:1:1/30000

      Status:              In Service

    Context ID 2                Stream ID 2

    Side A:             Name abc/voice4/gn/0/1/0/1/ac/7    Media Flowing:  No

      Local Address/Port:  202.100.1.3/20002

      Remote Address/Port: Not known

      Status:              In Service

    Side B:             Name abc/voice4/gn/0/1/0/1/bb/8    Media Flowing:  No

      Local Address/Port:  202.100.1.3/20000

      Remote Address/Port: 200.100.1.1/30000

      Status:              In Service

The following command lists the statistics for media flows collected on the DBE associated with a VRF vpn1:

Router# show sbc dmsbc-node9 dbe media-flow-sta vrf vpn1 ipv4 88.88.110.100 port 20000

SBC Service ''dmsbc-node9'' 

Media Flow: 

State of Media Flow: Active 

Call Age: 3850390 ms 

Call Priority: Routine 

Reserved Bandwidth: 10 (kilobytes/second) 

No media timeout remaining: 2741 

Class of service: Any 

Side A: 

VRF Name: vpn1 

Local Address: 88.88.110.100 

Local Port: 20000 

Remote Address: 200.200.200.172 

Remote Port: 17488 

RTP Packets Received: 140134 

RTP Packets Sent: 140131 

RTP Packets Discarded: 0

The following command lists the statistics about one or more media flows collected on the DBE for a port with an IPv4 address associated with a specific VRF instance:

Router# show sbc j dbe media-flow-stats detail vrf vpn1 ipv4 10.127.3.1 port 16526

SBC Service "j"

  Media Flow:

    State of Media Flow: Active

    Call Priority:       Routine

    ContextID:           12

    StreamID:            49153

    Reserved Bandwidth:  10500 (bytes/second)

    No media timeout remaining: 30

    Class of service:    Voice

    Side A:

      VRF Name:                   vpn1

      Local Address:              88.102.9.100

      Local Port:                 16384

      Remote Address:             10.127.3.1

      Remote Port:                16526

      RTP Packets Received:       2119

      RTP Packets Sent:           2096

      RTP Packets Discarded:      0

      RTP Data Received:          423800 (bytes)

      RTP Data Sent:              419200 (bytes)

      RTP Data Discarded:         0 (bytes)

      End Point Packets Sent:     Not known

      End Point Packets Received: Not known

      End Point Packets Lost:     Not known

      DTMF Interworking:          No

      Media Flowing:              Yes

      Affected by Routing Error:  No

      Unexpected SrcAddr Packets: No

      Billing ID:                 0x47B507DF2020202020202030302B3030303030300000

0018

      Media directions allowed:  sendrecv

    Side B:

      VRF Name:                   vpn2

      Local Address:              88.102.10.100

      Local Port:                 16384

      Remote Address:             10.127.4.1

      Remote Port:                19566

      RTP Packets Received:       2096

      RTP Packets Sent:           2119

      RTP Packets Discarded:      0

      RTP Data Received:          419200 (bytes)

      RTP Data Sent:              423800 (bytes)

      RTP Data Discarded:         0 (bytes)

      End Point Packets Sent:     Not known

      End Point Packets Received: Not known

      End Point Packets Lost:     Not known

      DTMF Interworking:          No

      Media Flowing:              Yes

      Affected by Routing Error:  No

      Unexpected SrcAddr Packets: No

      Billing ID:                 0x47B507DF2020202020202030302B3030303030300000

0017

      Media directions allowed:  sendrecv

Table 5 show sbc dbe media-flow-stats Field Descriptions 

Field	Description
Context ID	The context ID to which the flow is associated.
Stream ID	Stream ID.
State of Media Flow	Flow (or Termination) state (Active, Allocated, or Unknown). Active—The DBE has programmed the flow pair and media has started flowing in at least one direction. Allocated—The DBE has programmed the flow pair, but no media has started to flow. Unknown—The DBE has not yet been given enough information by the controller to be able to program the flow pair.
Call Established Time	Call established time in the format 23:51:29 UTC Jun 21 2007.
Flow Priority	Priority of the call (Routine or Urgent).
Side A	Information for the initiating side of the call.
Side B	Information for the terminating side of the call.
Name	Name of the flow.
Reserved Bandwidth	Bandwidth reserved for the call in bytes per second. (This value maps to the tman/sdr value.)
Status	Status is InService or OutofService. InService—Flow on this side is in service. OutofService—No media is forwarded.
VRF Name	Either the VRF name, or "Global" when there is no VRF.
VLAN Tags (Priorities)	VLAN tags and Ethernet priorities information.
Local Address	Local address on the DBE on which packets are received for this side of the call.
Local Port	Local port on the DBE on which packets are received for this side of the call.
Remote Address	Address of the remote endpoint from which packets are expected to be sent for this side of the call.
Remote Port	Port on the remote endpoint from which packets are expected to be sent for this side of the call.
Remote Source Address Mask	If specified, all packets matching the Remote Source Address Mask are classified as belonging to this flow rather than just those matching the full remote and port. (This value maps to the gm/sam value.)
Packets Received	Number of packets received from the remote endpoint.
Packets Sent	Number of packets forwarded to the remote endpoint.
Packets Discarded	Number of packets dropped (due to bandwidth policing, for example).
Data Received	Number of bytes of data received from the remote endpoint.
Data Sent	Number of bytes of data forwarded to the remote endpoint.
Data Discarded	Number of bytes of data dropped (due to bandwidth policing, for example). (This value maps to the gm/sam value.)
GM Discarded Packets	This counter is always set to zero because it is not currently implemented. It will be the number of data packets received from the remote endpoint that have been discarded locally because of source address/port filtering.
Time To Recovery	The tsc/ttr value from Termination State Control (TSC) package, in milliseconds.
RTCP Packets Sent	If there are RTCP packets flowing in the call, the number of RTP packets (within the most recently received RTCP) that the endpoint reports as being sent.
RTCP Packets Received	If there are RTCP packets flowing in the call, the number of RTP packets (within the most recently received RTCP) that the endpoint reports as being received.
RTCP Packets Lost	If there are RTCP packets flowing in the call, the number of RTP packets (within the most recently received RTCP) that the endpoint reports as being lost.
DTMF Interworking	Indicates whether DTMF interworking is in operation for the flow.
Media Flowing	Indicates whether packets are flowing from the endpoint.
Unexpected SrcAddr Packets	If unexpected-source-alerting is switched on with the unexpected-source-alerting command, this counter records the number of alerts generated for the flow when media packets for a call are received from an unexpected source address and port. An unexpected source event happens when a packet is received, matched to a flow (but not by a full 5-tuple comparison), and found to have come from the wrong remote address.
Billing ID	Signaling border element (SBE) billing ID for this side of the call.
Media directions allowed	Allowed directions of media flow for this side of the call (inactive, sendonly, recvonly, or sendrecv).
Max Burst size	The maximum burst size (tman/mbs) associated with the Tman package.
Delay variation tolerance	The delay variation tolerance (tman/dvt) associated with the Tman package. Defines the delay variation tolerance for the stream in tenths of microseconds when enforcing the PDR value in the first leaky bucket.
SDP string	The SDP string is that present on the H.248 ADD request to provision the call.
Graceful deactivation	Description to be added.
DiffServ Code Point	The Diffserv Code point is the (DSCP value) provided on the H.248 request to mark the media packets. This reflects the ds/dscp parameters.
Media Loss Event	Media Loss Event is "Yes" if the flow has the nt/qualert subscription.
NAT Latch Event	The NAT Latch Event is "Yes" if the flow has adr/rsac subscribed.

Related Commands

Command	Description
show sbc dbe flow-stats	Lists all flow statistics, both signaling and media flows, collected on the data border element (DBE).
show sbc dbe addresses	Displays the H.248 control addresses and media addresses configured on DBEs.
show sbc dbe controllers	Displays the media gateway controllers and the controller address configured on each DBE.
show sbc dbe forwarder-stats	Displays the global list of statistics for the DBE forwarding process.
show sbc dbe media-stats	Displays general DBE statistics. These statistics do not include data from active calls.
show sbc dbe signaling-flow-stats	Displays the statistics about one or more signaling flows collected on the DBE.
unexpected-source-alerting	Enables the generation of alerts when media packets for a call are received from an unexpected source address and port.

show sbc dbe media-stats

To list general data border element (DBE) statistics, use the show sbc dbe media- stats command in user EXEC or privileged EXEC mode.

show sbc {sbc-name} dbe media-stats

Syntax Description

sbc-name

Name of the session border controller (SBC) service.

Command Default

No default behavior or values

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.1	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Cisco IOS XE Release 2.4	This command is supported in the unified model.

Usage Guidelines

The show sbc dbe media- stats statistics do not include data from active calls. The global counters keep track of packets received and sent on calls that have already ended.

The Active Flows statistic counts the number of flows for which media has been observed within the media-timeout period, or where the call has failed over within the last media-timeout period and the SBC has not yet had a chance to observe whether media is flowing or not.

The Unclassified Pkts statistic includes all packets received on the VLAN interface that are not matched to a valid media flow. This includes media packets not matched to a flow, signaling packets, and any other traffic.

Examples

The following example shows general DBE statistics on a DBE that is on an SBC called "mySbc." These DBE statistics do not include data from active calls.

Router# show sbc mySbc dbe media-stats

SBC Service "mySbc"

  Max Term per Context   = 68

  Available Bandwidth    = Unlimited

  Available Flows        = 9998

  Available Packet Rate  = 999800 (packets/second)

  Active Media Flows     = 0

  Peak Media Flows       = 0

  Total Media Flows      = 1

  Active Signaling Flows = 0

  Peak Signaling Flows   = 0

  Total Signaling Flows  = 1

  SBC Packets Received   = 0

  SBC Octets Received    = 0

  SBC Packets Sent       = 0

  SBC Octets Sent        = 0

  SBC Packets Discarded  = 0

  SBC Octets Discarded   = 0

  No Media Count         = 0

Table 6 show sbc dbe media-stats Field Descriptions 

Field	Description
Max Term per Context	Maximum number of terminations per context.
Available Bandwidth	Total amount of bandwidth available for new calls.
Available Flows	Total amount of flows available for new calls.
Available Packet Rate	Amount of media packets per second available to new calls.
Active Media Flows	Current number of active calls.
Peak Media Flows	Maximum number of concurrent calls recorded.
Total Media Flows	Total number of calls set up on the DBE since the statistics were last cleared.
Active Signaling Flows	Current number of flows that are actively forwarding signaling traffic.
Peak Signaling Flows	Peak number of active signaling flows since the statistics were last reset.
Total Signaling Flows	Accumulated total number of signaling flows. This count contains both active signaling flows and signaling flows that were allocated but never connected.
SBC Packets Received	Total number of SBC packets received by the DBE for completed calls.
SBC Octets Received	Number of octets of SBC data received by the DBE for completed calls.
SBC Packets Sent	Total number of SBC packets sent by the DBE for completed calls.
SBC Octets Sent	Number of octets of SBC data sent by the DBE for completed calls.
SBC Packets Discarded	Number of SBC packets discarded on completed calls.
SBC Octets Discarded	Number of SBC octets discarded on completed calls.
No Media Count	Number of calls that have been dropped because there was no media flowing on the call.

Related Commands

Command	Description
show sbc dbe addresses	Displays the H.248 control addresses and media addresses configured on DBEs.
show sbc dbe controllers	Displays the media gateway controllers and the controller address configured on each DBE.
show sbc dbe forwarder-stats	Displays the global list of statistics for the DBE forwarding process.
show sbc dbe media-flow-stats	Displays the statistics about one or more media flows collected on the DBE.
show sbc dbe signaling-flow-stats	Displays the statistics about one or more signaling flows collected on the DBE.
unexpected-source-alerting	Enables the generation of alerts when media packets for a call are received from an unexpected source address and port.

show sbc dbe signaling-flow-stats

To list the signaling flow statistics collected on the data border element (DBE), use the show sbc dbe signaling-flow-stats command in user EXEC or privileged EXEC mode.

show sbc {sbc-name} dbe signaling-flow-stats [{summary | detail} [vrf vrf-name] [{ipv4 A.B.C.D | ipv6 ipv6-address} [port port-number]] [context {id}| termination {termination substring}]]

Syntax Description

sbc-name	Name of the session border controller (SBC) service.
summary	(Optional) Displays a summary of the signaling flow statistics, including pinhole flows, for the DBE.
detail	(Optional) Displays detailed signaling flow statistics, including pinhole flows, for the DBE.
vrf vrf-name	(Optional) Displays only signaling flows to or from the specified VPN routing and forwarding instance (VRF).
ipv4 A.B.C.D	(Optional) Displays only signaling flows to or from the specified IPv4 media IP address.
ipv6 ipv6-address	(Optional) Displays only signaling flows to or from the specified IPv6 media IP address.
port port-number	(Optional) Displays only signaling flows to or from the specified port number.
context	(Optional) Shows summary or detailed display of all pinhole flows within the context ID.
id	(Optional) Specifies the context ID number.
termination	(Optional) Shows summary or detailed display of pinhole flows. that match the termination substring.
termination substring	(Optional) Specifies the termination substring number.

Command Default

No default behavior or values

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.1	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Cisco IOS XE Release 2.2	The context and termination keywords were added. New fields (Max Burst size, Delay variation tolerance, SDP string, Graceful deactivation, DiffServ Code Point, Media Loss Event, and NAT Latch Event) were added to the ouput display.
Cisco IOS XE Release 2.4	This command is supported in the unified model.

Usage Guidelines

When the "Media Flowing" field is reported as Yes, it either means that media has been observed flowing on the call within the media timeout period, or the call has failed over within the last media timeout period and the SBC has not yet had a chance to observe whether media is flowing or not.

Examples

The following example displays signaling and media flow pairs and additional fields added in Cisco IOS XE Release 2.2:

Router# show sbc global dbe signaling-flow-stats

SBC Service "global"

  Media Flow:

    Context ID:          6

    Stream ID:           1

    State of Signaling Flow: Allocated

    Call Established Time: 16:53:58 UTC Feb 20 2008

    Flow Priority:       Unspecified

    Side A:

      Name                        mycompany/sip4/gn/0/1/0/1/ac/1

      Reserved Bandwidth:         0 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.2.1

      Local Port:                 10000

      Remote Address:             3.0.0.3

      Remote Port:                5000

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Max Burst size:             0 (bytes)            <===== additional fields for Side A

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No 

    Side B:

      Name                        mycompany/sip4/gn/0/1/0/1/bb/2

      Reserved Bandwidth:         0 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.2.1

      Local Port:                 10001

      Remote Address:             3.0.0.3

      Remote Port:                5000

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Max Burst size:             0 (bytes)            <===== additional fields for side B

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        B8

      Media Loss Event:           No

      NAT Latch Event:            No

The following example displays detailed statistics from an IPv4 signaling flow collected on the DBE:

Router# show sbc mySbc dbe signaling-flow-stats detail

SBC Service "mySbc"

  Media Flow:

    Context ID:          2

    Stream ID:           1

    State of Signaling Flow: Active

    Call Established Time: 12:55:11 UTC Aug 11 2007

    Flow Priority:       Routine

    Side A:

      Name                        abc/sip/gn/0/1/0/1/ac/1

      Reserved Bandwidth:         43 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.255.110

      Local Port:                 5000

      Remote Address:             100.50.255.110

      Remote Port:                5000

      Remote Source Address Mask: 100.50.255.0/24

      Packets Received:           1344

      Packets Sent:               0

      Packets Discarded:          444

      Data Received:              885 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             292 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      Media Flowing:              Yes

      Unexpected SrcAddr Packets: No

      Max Burst size:             0 (bytes)            <===== additional fields for Side A

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        0

      Media Loss Event:           No

      NAT Latch Event:            No 

    Side B:

      Name                        abc/sip/gn/0/1/0/1/bb/2

      Reserved Bandwidth:         0 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:              202.50.255.110

      Local Port:                 5001

      Remote Address:             200.50.255.110

      Remote Port:                10000

      Packets Received:           1335

      Packets Sent:               900

      Packets Discarded:          1335

      Data Received:              880 (bytes)

      Data Sent:                  593 (bytes)

      Data Discarded:             880 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Max Burst size:             0 (bytes)            <===== additional fields for side B

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        B8

      Media Loss Event:           No

      NAT Latch Event:            No

The following example displays detailed statistics from an IPv6 signaling flow collected on the DBE:

Router# show sbc global dbe signaling-flow-stats detail

SBC Service "global"

  Media Flow:

    Context ID:          2

    Stream ID:           1

    State of Signaling Flow: Allocated

    Call Established Time: 12:55:11 UTC Aug 11 2007

    Flow Priority:       Routine

    Side A:

      Name                        abc/sip/gn/0/1/0/1/ac/1

      Reserved Bandwidth:         23 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address:           1111:2222:3333:4444:5555:6666:7777:3331

      Local Port:                 5000

      Remote Address:             Not known

      Remote Port:                Not known

      Remote Source Address Mask: 2222:1111:1111:2222:3333:4444:5555:7777/48

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       Not known

      Time To Recovery:           Not known

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Max Burst size:             0 (bytes)            <===== additional fields for side A

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        B8

      Media Loss Event:           No

      NAT Latch Event:            No

    Side B:

      Name                        abc/sip/gn/0/1/0/1/bb/2

      Reserved Bandwidth:         0 (bytes/second)

      Status                      InService

      VRF Name:                   Global

      VLAN Tags(Priorities):      0(0), 0(0)

      Local Address Mask:  2222:1111:1111:2222:3333:4444:5555:7777/48

      Local Port:                 0

      Remote Address:          3333:1111:1111:2222:3333:4444:5555:7777

      Remote Port:                10000

      Packets Received:           0

      Packets Sent:               0

      Packets Discarded:          0

      Data Received:              0 (bytes)

      Data Sent:                  0 (bytes)

      Data Discarded:             0 (bytes)

      GM Discarded Packets:       0

      Time To Recovery:           Not known

      Media Flowing:              No

      Unexpected SrcAddr Packets: No

      Max Burst size:             0 (bytes)            <===== additional fields for side B

      Delay variation tolerance:  0 (microseconds)

      SDP string:                 m=application $ udp 0

      Graceful deactivation:      No

      DiffServ Code Point:        B8

      Media Loss Event:           No

      NAT Latch Event:            No

The following example shows summary statistics collected for signaling flows on the DBE:

Router# show sbc mySbc dbe signaling-flow-stats summary

SBC Service "mySbc"

    Context ID 1                Stream ID 1

    Side A:             Name abc/sip6/gn/0/1/0/1/ac/1    Media Flowing:  Yes

      Local Address/Port:  1:100:1:1:1:1:1:1/5060

      Remote Address/Port: 2:100:1:1:1:1:1:1/5000

      Status:              In Service

    Side B:             Name abc/sip6/gn/0/1/0/1/bb/2    Media Flowing:  Yes

      Local Address/Port:  2:100:1:1:1:1:1:1/5000

      Remote Address/Port: 3:100:1:1:1:1:1:1/5060

      Status:              In Service

    Context ID 2                Stream ID 1

    Side A:             Name abc/sip4/gn/0/1/0/1/ac/5    Media Flowing:  Yes

      Local Address/Port:  202.100.1.1/5000

      Remote Address/Port: 100.100.1.1/5000

      Status:              In Service

    Side B:             Name abcsip4/gn/0/1/0/1/bb/6    Media Flowing:  Yes

      Local Address/Port:  202.100.1.1/5001

      Remote Address/Port: 200.100.1.1/5000

      Status:              In Service

Table 7 show sbc dbe signaling-flow-stats Field Descriptions 

Field	Description
Context ID	Context ID to which the flow is associated.
Stream ID	Stream ID.
State of Signaling Flow	Flow state (Active, Allocated, or Unknown). •Active—DBE has programmed the flow pair and the media has started flowing in at least one direction. •Allocated—DBE has programmed the flow pair, but no media has started to flow. •Unknown—DBE has not yet been given enough information by the controller to be able to program the flow pair.
Call Established Time	Call established time in the format 23:51:29 UTC Jun 21 2007.
Flow Priority	Priority of the call (Routine or Urgent).
Side A	Information for the initiating side of the call
Side B	Information for the terminating side of the call
Name	Name of the flow.
Reserved Bandwidth	Bandwidth reserved for the call in bytes per second.
Status	Status is InService or OutofService. InService—Flow on this side is in service. OutofService—No media is forwarded.
VRF Name	Either the VRF name, or "Global" when there is no VRF.
VLAN Tags (Priorities)	VLAN tags and Ethernet priority information.
Local Address	Local address on the DBE on which packets are received for this side of the call.
Local Port	Local port on the DBE on which packets are received for this side of the call.
Remote Address	Address of the remote endpoint from which packets are expected to be sent for this side of the call.
Remote Port	Port on the remote endpoint from which packets are expected to be sent for this side of the call.
Remote Source Address Mask	If specified, all packets matching the Remote Source Address Mask are classified as belonging to this flow rather than just those matching the full remote and port.
Packets Received	Number of packets received from the remote endpoint.
Packets Sent	Number of packets forwarded to the remote endpoint.
Packets Discarded	Number of packets dropped (due to bandwidth policing, for example).
Data Received	Number of bytes of data received from the remote endpoint.
Data Sent	Number of bytes of data forwarded to the remote endpoint.
Data Discarded	Number of bytes of data dropped (due to bandwidth policing, for example).
GM Discarded Packets	This counter is always set to zero because it is not currently implemented. It will be the number of data packets received from the remote end point and discarded locally because of source address/port filtering.
Time To Recovery	The tsc/ttr value from Termination State Control (TSC) package, in milliseconds.
Media Flowing	Indicates whether packets are flowing from the endpoint.
Unexpected SrcAddr Packets	If unexpected-source-alerting is switched on with the unexpected-source-alerting command, this counter records the number of alerts generated for the flow when media packets for a call are received from an unexpected source address and port. An unexpected source event happens when a packet is received, matched to a flow (but not by a full 5-tuple comparison), and found to have come from the wrong remote address.
Max Burst size	The maximum burst size (tman/mbs) associated with the Tman package.
Delay variation tolerance	The delay variation tolerance (tman/dvt) associated with the Tman package. Defines the delay variation tolerance for the stream in tenths of microseconds when enforcing the PDR value in the first leaky bucket.
SDP string	The SDP string is that present on the H.248 ADD request to provision the call.
Graceful deactivation	Description to be added.
DiffServ Code Point	The Diffserv Code point is the (DSCP value) provided on the H.248 request to mark the media packets. This reflects the ds/dscp parameters.
Media Loss Event	Media Loss Event is "Yes" if the flow has the nt/qualert subscription.
NAT Latch Event	The NAT Latch Event is "Yes" if the flow has adr/rsac subscribed.

Related Commands

Command	Description
show sbc dbe flow-stats	Lists all flow statistics, both signaling and media flows, collected on the data border element (DBE).
show sbc dbe addresses	Displays the H.248 control addresses and media addresses configured on DBEs.
show sbc dbe controllers	Displays the media gateway controllers and the controller address configured on each DBE.
show sbc dbe forwarder-stats	Displays the global list of statistics for the DBE forwarding process.
show sbc dbe media-stats	Displays general DBE statistics. These statistics do not include data from active calls.
show sbc dbe media-flow-stats	Displays the statistics about one or more media flows collected on the DBE.
unexpected-source-alerting	Enables the generation of alerts when media packets for a call are received from an unexpected source address and port.

show sbc rsrcmon

To show congestion states and statistics during switchover, use the show sbc rsrcmon command in the Privileged EXEC mode.

show sbc sbc-name rsrcmon

Syntax Description

sbc-name

Specifies the name of the SBC service.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows the addresses that are configured on mySBC:

Router# show sbc test rsrcmon

  Resource Monitoring                        :  Enabled

  Congestion Status                          :  Normal

    CPU Congestion Status                    :  Normal

    Mem Congestion Status                    :  Normal

    Calls Rejected Due to Congestion         :  0 

    CPU Congestion Count                     :  0

    Mem Congestion Count                     :  0

  CPU Congestion Threshold                   :  91 %

  CPU Congestion Clear Threshold             :  80 %

  Top Procs Frequency                        :  200 ms

  CPU Probe Duration during Congestion       :  1000 ms

  CPU Probe Duration during Normal Operation :  3000 ms

  Avg CPU Utilization in last  500 msec      :   0%(cpu0)  7%(cpu1)

                              1500 msec      :   0%(cpu0) 10%(cpu1)

  SBC Memory Allocation Limit                :    No Limit

      Current Allocation                     :    78466149 bytes

      Peak Allocation                        :    78466149 bytes

      Allocation Failure Count               :           0 

      Buffer Pool Usage                      :       67413 bytes

      CB Pool Usage                          :    37464456 bytes

      Free Memory SBC Holding                :    40934280 bytes

      Memory Usage Ceiling                   :   180000000 bytes

      Last Monitored Usage                   :  37533189 bytes (20 %)

Here is info on malloc:

Total memory for dynamic memory allocation (arena) --    440040 bytes

Number of ordinary blk not in use (ordblks) ---------         4

Number of small blk not in use (smblks) -------------         0

Number of blks allocated w/ mmap (hblks) ------------       300

Sum of memory allocated with mmap (hblkhd) ----------  78798848 bytes

Space in small blks in use (usmblks) ----------------         0 bytes

Space in free small blks (fsmblks) ------------------         0 bytes

Space in ordinary blocks in use (uordblks) ----------    434736 bytes

Space in free ordinary blocks  (fordblks) -----------      5304 bytes

keepcost --------------------------------------------      5168

Here is OS memory info

Total   =  844869632 bytes

Used    =  470876160 bytes (321875968 bytes after minus buffers/cached)

Free    =  373993472 bytes (522993664 bytes after adding buffers/cached)

Shared  =          0 bytes

Buffers =    1130496 bytes

Cached  =  147869696 bytes

show sbc sbe aaa

To list the AAA status and configuration on each SBE, use the show sbc sbe aaa command in the Privileged EXEC mode.

show sbc sbc-name sbe aaa

Syntax Description

sbc-name

Specifies the name of the SBC service.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows the addresses that are configured on mySBC:

Router# show sbc sbe aaa

SBC Service "mySbc"

  AAA control address: 10.1.0.1

  Accounting server: 10.2.0.1

  Authentication server: 172.19.5.1

  Authentication server: 172.19.5.2

show sbc sbe addresses

To list the addresses configured on SBEs, use the show sbc sbe addresses command in the Privileged EXEC mode.

show sbc sbc-name sbe addresses

Syntax Description

sbc-name

Specifies the name of the SBC service.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows the addresses that are configured on mySBC:

Router# show sbc mySBC sbe addresses

SBC Service "mySbc"

  Control Addresses

    AAA control address:	            10.1.0.1

    H.248 control address:	            10.1.0.1

  Signaling Addresses

    H.323 adjacency h323ToIsp42:     10.1.0.2:1720, VRF vpn3

    SIP adjacency SipToIsp42:        10.1.0.2:5060, VRF vpn3

show sbc sbe adjacencies

To list the adjacencies configured on signaling border elements (SBEs), use the show sbc sbe adjacencies command in Privileged EXEC mode.

show sbc sbc-name sbe adjacencies {adjacency-name} [detail]

Syntax Description

sbc-name	Specifies the name of the SBC service.
adjacency-name	Specifies the name of the SIP adjacency.
detail	Displays all the detailed field output for the specified SIP adjacency.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Cisco IOS XE Release 2.4.1	The command output was modified to show whether the adjacency is configured to support SIP method statistics.
Cisco IOS XE Release 2.5	The command output was modified to show: IP realm information, contact username information, IP-FQDN translation parameters, and 100rel interworking parameters.

Usage Guidelines

The statistics-setting command must be configured on an adjacency before using the show sbc sbe sip-method-stats command to display SIP method statistics. You can use the show sbc sbe adjacencies command to verify that the statistics-setting command is configured on an adjacency.

Examples

For Cisco IOS XE Release 2.5 and later, the show sbc sbe adjacencies detail command lists the adjacencies information, including the IP realm information, configured on an SBE:

Router# show sbc global sbe adjacencies Cisco-gw detail

SBC Service "global"

Adjacency Cisco-gw (SIP)

Status: Detached

Signaling address: 111.45.103.119:default

Signaling-peer: :5060 (Default)

Force next hop: No

Account:

Group: None

In header profile: Default

Out header profile: Default

In method profile: Default

Out method profile: Default

In body profile: None

Out body profile: None

In UA option prof: Default

Out UA option prof: Default

In proxy opt prof: Default

Out proxy opt prof: Default

Priority set name: None

Local-id: None

Rewrite REGISTER: Off

Target address: None

NAT Status: Auto Detect

Reg-min-expiry: 3000 seconds

Fast-register: Enabled

Fast-register-int: 30 seconds

Register aggregate: Disabled

Registration Required: Disabled

Register Out Interval: 0 seconds

Parse username params: Disabled

Supported timer insert:Disabled

Suppress Expires: Disabled

p-asserted-id header-value: not defined

p-assert-id assert: Disabled

Authenticated mode: None

Authenticated realm: None

Auth. nonce life time: 300 seconds

IMS visited NetID: None

Inherit profile: Default

Force next hop: No

Home network Id: None

UnEncrypt key data: None

SIPI passthrough: No

Passthrough headers:

Media passthrough: No

Client authentication: No

Incoming 100rel strip: No

Incoming 100rel supp: No

Out 100rel supp add: No

Out 100rel req add: No

Parse TGID parms: No

IP-FQDN inbound:

IP-FQDN outbound:

FQDN-IP inbound:

FQDN-IP outbound:

Outbound Flood Rate: None

Hunting Triggers: Global Triggers

Add transport=tls param: Disabled

Redirect mode: Pass-through

Security: Untrusted-Unencrypted

Ping: Disabled

Ping Interval: 32 seconds

Ping Life Time: 32 seconds

Ping Peer Fail Count: 3

Ping Trap sending: Enabled

Ping Peer Status: Not Tested

Rewrite Request-uri: Disabled

Registration Monitor: Disabled

DTMF SIP NOTIFY Relay: Enabled

DTMF SIP NOTIFY Interval: 2000

DTMF SIP default duration: 200

DTMF Preferred Method: SIP NOTIFY

Realm : cisco.com

Statistics setting: Disabled

For Cisco IOS XE Release 2.5 and later, the show sbc sbe adjacencies detail command shows the Register contact username information.

Router# show sbc test sbe adjacencies SIPP1Reg detail

SBC Service "test"

  Adjacency SIPP1Reg (SIP)

    Status:                Attached

    Signaling address:     10.10.100.140:default

    Signaling-peer:        10.10.100.12:7068

    Force next hop:        No

    Account:               

    Group:                 SIPP1Reg

    ..

    Rewrite REGISTER:      Off

    Register contact username: Rewrite

    Target address:        10.10.100.12:7069

    NAT Status:            Auto Detect

    Reg-min-expiry:        3000 seconds

    Fast-register:         Enabled

    Fast-register-int:     30 seconds

    Register aggregate:    Disabled

    Registration Required: Disabled

    Register Out Interval: 0 seconds

    ..

The following example shows the adjacencies that are configured on SBEs:

Router# show sbc mysbc sbe adjacencies

SBC Service ''mysbc'' 

Name Type State Description 

--------------------------------------------- 

h323-7206-CG H.323 Attached 

h323-ixvoice H.323 Attached 

sip-60 SIP Attached 

7600-phone1 SIP Attached 

7600-phone2 SIP Attached 

sip-ixvoice SIP Attached 

sip-7206-CG- SIP Attached

The following example shows detailed information for the sippb adjacency. The statistics setting (shown at the very bottom of the example) is set to Detail. This means that the statistics-setting command was configured to allow the adjacency to support detailed SIP method statistics, including SIP response codes and SIP request names. Use the show sbc sbe sip-method-stats command to display SIP method statistics.

Router# show sbc test sbe adjacencies sippb detail

SBC Service "test"

  Adjacency sippb (SIP)

    Status:                Attached

    Signaling address:     99.99.103.150:5082

    Signaling-peer:        100.100.1.64:5082

    Force next hop:        No

    Account:               sipp-b

    Group:                 None

    In header profile:     Default

    Out header profile:    Default

    In method profile:     Default

    Out method profile:    Default

    In UA option prof:     Default

    Out UA option prof:    Default

    In proxy opt prof:     Default

    Out proxy opt prof:    Default

    Priority set name:     None

    Local-id:              None

    Rewrite REGISTER:      Off

    Target address:        100.100.1.64:5084

    NAT Status:            Auto Detect

    Reg-min-expiry:        3000 seconds

    Fast-register:         Enabled

    Fast-register-int:     30 seconds

    Register aggregate:    Disabled

    Register Out Interval: 86400 seconds

    Authenticated mode:    None

    Authenticated realm:   None

    Auth. nonce life time: 300 seconds

    IMS visited NetID:     None

    Inherit profile:       Default

    Force next hop:        No

    Home network Id:       None

    UnEncrypt key data:    None

    SIPI passthrough:     No

    Rewrite from domain:   Yes

    Rewrite to header:     Yes

    Media passthrough:     No

    Client authentication: No

    Hunting Triggers:      Global Triggers

    Redirect mode:         Pass-through

    Security:              Untrusted-Unencrypted

    Signaling Peer Status: Not Tested

    Rewrite Request-uri:   Disabled

    Registration Monitor:  Disabled

    DTMF SIP NOTIFY Relay:     Enabled

    DTMF SIP NOTIFY Interval:  2000

    DTMF SIP default duration: 200

    DTMF Preferred Method:  SIP NOTIFY

    Statistics setting:     Detail

The following example shows detailed output for adjacency SoftSwitch where SoftSwitch Shielding is enabled. The "Register Out Timer:" field shows the time interval in seconds when the SBC forwards the next REGISTER messages to the softswitch.

Router# show sbc mySbc sbe adjacencies SoftSwitch detail

SBC Service "mySbc"

  Adjacency SoftSwitch (SIP)

    Status:                Attached

    Signaling address:     100.100.100.100:5060, VRF Admin

    Signaling-peer:        10.10.51.10:5060

    Force next hop:        No

    Account:               

    Group:                 None

    In header profile:     Default

    Out header profile:    Default

    In method profile:     Default

    Out method profile:    Default

    In UA option prof:     Default

    Out UA option prof:    Default

    In proxy opt prof:     Default

    Out proxy opt prof:    Default

    Priority set name:     None

    Local-id:              None

    Rewrite REGISTER:      Off

    Target address:        None

    Register Out Timer:    36000 seconds

    Register Aggregate:    Disabled

    NAT Status:            Auto Detect

    Reg-min-expiry:        30 seconds

    Fast-register:         Enabled

    Fast-register-int:     30 seconds

    Authenticated mode:    None

    Authenticated realm:   None

    Auth. nonce life time: 300 seconds

    IMS visited NetID:     None

    Inherit profile:       Default

    Force next hop:        No

    Home network Id:       None

    UnEncrypt key data:    None

    SIPI passthrough:      No

    Rewrite from domain:   Yes

    Rewrite to header:     Yes

    Media passthrough:     No

    Preferred transport:   UDP

    Hunting Triggers:      Global Triggers

    Redirect mode:         Pass-through

    Security:              Untrusted

    Outbound-flood-rate:   None

    Ping-enabled:          No

    Signaling Peer Status: Not Tested

The following example displays detailed output for adjacency Cary-IP-PBX, including the "Register Aggregate:" field that shows Aggregate Registration is "Enabled."

Router# show sbc mySbc sbe adjacencies Cary-IP-PBX detail

SBC Service "mySBC"

  Adjacency Cary-IP-PBX (SIP)

    Status:                Attached

    Signaling address:     100.100.100.100:5060, VRF Admin

    Signaling-peer:        10.10.51.10:5060

    Force next hop:        No

    Account:               

    Group:                 None

    In header profile:     Default

    Out header profile:    Default

    In method profile:     Default

    Out method profile:    Default

    In UA option prof:     Default

    Out UA option prof:    Default

    In proxy opt prof:     Default

    Out proxy opt prof:    Default

    Priority set name:     None

    Local-id:              None

    Rewrite REGISTER:      Off

    Target address:        None

    Register Out Timer:    1800 seconds

    Register Aggregate:    Enabled

    NAT Status:            Auto Detect

    Reg-min-expiry:        30 seconds

    Fast-register:         Enabled

    Fast-register-int:     30 seconds

    Authenticated mode:    None

    Authenticated realm:   None

    Auth. nonce life time: 300 seconds

    IMS visited NetID:     None

    Inherit profile:       Default

    Force next hop:        No

    Home network Id:       None

    UnEncrypt key data:    None

    SIPI passthrough:      No

    Rewrite from domain:   Yes

    Rewrite to header:     Yes

    Media passthrough:     No

    Preferred transport:   UDP

    Hunting Triggers:      Global Triggers

    Redirect mode:         Pass-through

    Security:              Untrusted

    Outbound-flood-rate:   None

    Ping-enabled:          No

    Signaling Peer Status: Not Tested

    Rewrite Request-uri:   Enabled

    Registration Monitor:  Disabled

The following example displays detailed output for adjacency Cary-IP-PBX, including the "Registration Monitor:" field that shows Registration Monitoring is "Enabled:"

Router# show sbc mySBC sbe adjacencies Cary-IP-PBX detail

SBC Service "mySbc"

  Adjacency Cary-IP-PBX (SIP)

    Status:                Attached

    Signaling address:     100.100.100.100:5060, VRF Admin

    Signaling-peer:        10.10.51.10:5060

    Force next hop:        No

    Account:               

    Group:                 None

    In header profile:     Default

    Out header profile:    Default

    In method profile:     Default

    Out method profile:    Default

    In UA option prof:     Default

    Out UA option prof:    Default

    In proxy opt prof:     Default

    Out proxy opt prof:    Default

    Priority set name:     None

    Local-id:              None

    Rewrite REGISTER:      Off

    Target address:        None

    Register Out Timer:    1800 seconds

    Register Aggregate:    Enabled

    NAT Status:            Auto Detect

    Reg-min-expiry:        30 seconds

    Fast-register:         Enabled

    Fast-register-int:     30 seconds

    Authenticated mode:    None

    Authenticated realm:   None

    Auth. nonce life time: 300 seconds

    IMS visited NetID:     None

    Inherit profile:       Default

    Force next hop:        No

    Home network Id:       None

    UnEncrypt key data:    None

    SIPI passthrough:      No

    Rewrite from domain:   Yes

    Rewrite to header:     Yes

    Media passthrough:     No

    Preferred transport:   UDP

    Hunting Triggers:      Global Triggers

    Redirect mode:         Pass-through

    Security:              Untrusted

    Outbound-flood-rate:   None

    Ping-enabled:          No

    Signaling Peer Status: Not Tested

    Rewrite Request-uri:   Disabled

    Registration Monitor:  Enabled

Related Commands

Command	Description
show sbc sbe sip-method-stats	Displays summary or detailed statistics for a SIP method.
statistics-setting	Configures an adjacency to support SIP method statistics.

show sbc sbe adjacencies authentication-realms

To display authentication realm on the specified adjacency, use the show sbc sbe adjacencies authentication-realms command in Privileged EXEC mode.

show sbc sbc-name sbe adjacencies adjacency-name authentication-realms

Syntax Description

sbc-name	Specifies the name of the SBC service.
adjacency-name	The name of the SIP adjacency whose details are to be displayed.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to display all currently configured authentication-realms for all SIP adjacencies:

Router# show sbc mysbc sbe adjacencies sipAdjacency authentication-realms 

Configured authentication realms 

-------------------------------- 

Domain Username Password 

abcdef.com abc abc

show sbc sbe all-authentication-realms

To display all currently configured authentication-realms for all SIP adjacencies, use the show sbc sbe all-authentication-realms command in Privileged EXEC mode.

show sbc sbe all-authentication-realms

Syntax Description

.This command has no arguments or keywords

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to display all currently configured authentication realms for all SIP adjacencies:

Router# show sbc mySbc sbe all-authentication-realms

Configured authentication realms

--------------------------------

Adjacency: SipToIsp42

Domain Username Password 

Example.com usersbc passwordsbc 

show sbc sbe billing remote

To display the remote billing configuration. use the show sbc sbe billing remote command in Privileged EXEC mode.

show sbc sbe billing remote

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to display the remote billing configuration:

Router# show sbc mySbc sbe billing remote

Remote Billing

  Local IP address:            10.21.20.1

show sbc sbe blacklist configured-limits

To list the explicitly configured limits, showing only the sources configured, use the show sbc sbe blacklist configured-limits command in Privileged EXEC mode.

Values not explicitly configured and, therefore, inherited from other defaults, are bracketed.

show sbc sbc-name sbe blacklist configured-limits

Syntax Description

sbc-name

Specifies the name of the SBC.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following command lists the limits that you explicitly configured, showing only the sources. Non-explicitly configured values appear in brackets:

Router(config-sbc-sbe)# show sbc mySbc sbe blacklist configured-limits

SBC Service mySbc SBE dynamic blacklist configured limits

Default for all addresses

=========================

Reason          Trigger          Trigger      Blacklisting

                   Size           Period            Period

------          -------          -------      ------------

Authentication       20            1 sec            1 hour

Bad address          20            1 sec            1 hour

Routing              20            1 sec            1 hour

Registration          5           30 sec          10 hours

Policy               20            1 sec             1 day

Corrupt              20           100 ms            1 hour

Spam                  2           10 secs            1 mins    

Default for addresses on vpn3

=============================

Reason          Trigger          Trigger      Blacklisting

                   Size           Period            Period

------          -------          -------      ------------

Authentication       20            1 sec             1 day

Bad address          20            1 sec             1 day

Routing              20            1 sec             1 day

Registration          5           30 sec             1 day

Policy               20            1 sec             1 day

Corrupt              50           100 ms          12 hours

Spam                  2           10 secs            1 mins    

112.234.23.2

============

Reason          Trigger          Trigger      Blacklisting

                   Size           Period            Period

------          -------          -------      ------------

Authentication     2000          (1 sec)          (1 hour)

Bad address        2000          (1 sec)          (1 hour)

Routing            2000          (1 sec)          (1 hour)

Registration        500         (30 sec)        (10 hours)

Policy             2000          (1 sec)           (1 day)

Corrupt            2000         (100 ms)          (1 hour)

Spam                  2          10 secs            1 mins    

vpn3 172.19.12.12

=================

Reason          Trigger          Trigger      Blacklisting

                   Size           Period            Period

------          -------          -------      ------------

Authentication     (20)          (1 sec)          (1 hour)

Bad address        (20)          (1 sec)          (1 hour)

Routing            (20)          (1 sec)          (1 hour)

Registration        (5)         (30 sec)        (10 hours)

Policy             (20)          (1 sec)           (1 day)

Corrupt              40            10 ms          (1 hour)

Spam                  2          10 secs            1 mins    

Default for ports of vpn3 172.19.12.12

======================================

Reason          Trigger          Trigger      Blacklisting

                   Size           Period            Period

------          -------          -------      ------------

Authentication       20            1 sec            1 hour

Bad address          20            1 sec            1 hour

Routing              20            1 sec            1 hour

Registration          5           30 sec          10 hours

Policy               20            1 sec             1 day

Corrupt              20           100 ms            1 hour

Spam                  2           10 secs            1 mins    

Related Commands

Command	Description
reason	Enters a submode for configuring a limit to a specific event type on the source (in other words, a port, IP address, VPN, global address space).
trigger-size	Defines the number of the specified events from the specified source that are allowed before the blacklisting is triggered, and blocks all packets from the source.
trigger-period	Defines the period over which events are considered. For details, see the description of the trigger-size command.
timeout	Defines the length of time that packets from the source are blocked, should the limit be exceeded.
show sbc sbe blacklist	Lists the limits in force for a particular source (whether they are from defaults or explicitly configured) in a form in which they can be entered into the CLI. Also listed are any defaults for a smaller scope configured at this address.
show sbc sbe blacklist current-blacklisting	Lists the limits causing sources to be blacklisted.

show sbc sbe blacklist critical

To show all critical blacklists, use the show sbc sbe blacklist critical command in Privileged EXEC mode.

show sbc sbc-name sbe blacklist critical [ WORD | configured-limits | current-blacklisting | ipv4 {A.B.C.D}]

Syntax Description

sbc-name	Specifies the name of the SBC.
WORD	Specifies the VPN ID for which you want to display critical blacklisting information.
configured-limits	Shows all configured blacklisting limits for critical blacklists.
current-blacklisting	Shows the currently blacklisted addresses for critical blacklists.
ipv4 {A.B.C.D}	Shows configured critical blacklisting for a single IPv4 address.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4.2	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Usage Guidelines

Examples

The following example shows the currently blacklisted addresses for critical blacklists:

Router# show sbc test sbe blacklist critical current-blacklisting 

SBC Service "test" SBE dynamic blacklist current members

VRF: 600

=========

Source Source Blacklist Time

Address Port Reason Remaining

--------------------------------------------------------------

10.0.120.12 All Corruption 585 secs 

The following example shows critical blacklist information for VPN ID 600 for a specific IPv4 address:

Router# show sbc test sbe blacklist critical 600 ipv4 10.0.120.12

SBC Service "test"

600 10.0.120.12

=================

Reason Trigger Trigger Blacklisting

Size Period Period

--------------------------------------------------------------

Authentication (4) (100 ms) (10 mins) 

Bad-Address (4) (100 ms) (10 mins) 

Routing (4) (100 ms) (10 mins) 

Registration (4) (100 ms) (10 mins) 

Policy (4) (100 ms) (10 mins) 

Corruption 2 1 secs (10 mins) 

Spam 2 1 secs (10 mins) 

Default for all ports of 600 10.0.120.12

==========================================

Reason Trigger Trigger Blacklisting

Size Period Period

--------------------------------------------------------------

Authentication (4) (100 ms) (10 mins) 

Bad-Address (4) (100 ms) (10 mins) 

Routing (4) (100 ms) (10 mins) 

Registration (4) (100 ms) (10 mins) 

Policy (4) (100 ms) (10 mins) 

Corruption (4) (100 ms) (10 mins) 

Spam (30) (100 ms) (10 mins) 

Related Commands

Command	Description
reason	Enters a submode for configuring a limit to a specific event type on the source (in other words, a port, IP address, VPN, global address space).
trigger-size	Defines the number of the specified events from the specified source that are allowed before the blacklisting is triggered, and blocks all packets from the source.
trigger-period	Defines the period over which events are considered. For details, see the description of the trigger-size command.
timeout	Defines the length of time that packets from the source are blocked, should the limit be exceeded.
show sbc sbe blacklist configured-limits	Lists the explicitly configured limits, showing only the sources configured. Any values not explicitly defined for each source are in brackets.
show sbc sbe blacklist current-blacklisting	Lists the limits causing sources to be blacklisted.

show sbc sbe blacklist current-blacklisting

To list the limit causing sources to be blacklisted, use the show sbc sbe blacklist current-blacklisting command in the Privileged EXEC mode.

show sbc sbc-name sbe blacklist current-blacklisting

Syntax Description

sbc-name

Defines the name of the service.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows the current blacklisting information for the SBC:

Router# show sbc mySbc sbe blacklist current-blacklisting

SBC Service mySbc SBE dynamic blacklist current members

Global addresses

================

Source           Source   Blacklist       Time

Address          Port     Reason          Remaining

-------          ------   ---------       ---------

125.125.111.123  All      Authentication  15 mins

125.125.111.253  UDP 85   Registration    10 secs

144.12.12.4      TCP 80   Corruption      Never ends

192.169.0.9      All      Spam            49 secs 

VRF: vpn3

=========

Source           Source   Blacklist       Time

Address          Port     Reason          Remaining

-------          ------   ---------       ---------

132.15.1.2       TCP 285  Registration    112 secs

172.23.22.2      All      Policy          10 hours

192.169.0.9      All      Spam            49 secs 

Related Commands

Command	Description
reason	Enters a submode for configuring a limit to a specific event type on the source (in other words, a port, IP address, VPN, global address space).
trigger-size	Defines the number of the specified events from the specified source that are allowed before the blacklisting is triggered, and blocks all packets from the source.
trigger-period	Defines the period over which events are considered. For details, see the description of the trigger-size command.
timeout	Defines the length of time that packets from the source are blocked, should the limit be exceeded.
show sbc sbe blacklist	Lists the limits in force for a particular source (whether they are from defaults or explicitly configured) in a form in which they can be entered into the CLI. Also listed are any defaults for a smaller scope configured at this address.
show sbc sbe blacklist configured-limits	Lists the explicitly configured limits, showing only the sources configured. Any values not explicitly defined for each source are in brackets.

show sbc sbe blacklist ipv4

To list the limits in force for a particular source, whether from defaults or explicitly configured, in a form in which they can be entered into the CLI, use the show sbc sbe blacklist ipv4 command in Privileged EXEC mode.

show sbc sbc-name sbe blacklist [source] ipv4 IP address

Syntax Description

sbc-name	Specifies the name of the SBC.
source	Specifies the source for which you want to display blacklisting information. This source is one of the following values: •VPN ID (Only VPN ID is permitted in the present implementation.)
IP address	Specifies the IPv4 address.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Usage Guidelines

Also listed are any defaults for a smaller scope configured at this address.

Values not explicitly configured and, therefore, inherited from other defaults, are bracketed.

Examples

The following example shows how to list blacklisting information for a specific VPN with a valid IPv4 address:

Router# show sbc mySbc sbe blacklist vpn3 ipv4 172.19.12.12

SBC Service mySbc SBE dynamic blacklist vpn3 172.19.12.12

vpn3 172.19.12.12

=================

Reason          Trigger          Trigger      Blacklisting

                   Size           Period            Period

------          -------          -------      ------------

Authentication     (20)            10 ms          (1 hour)

Bad address        (20)            10 ms          (1 hour)

Routing            (20)            10 ms          (1 hour)

Registration        (5)           100 ms        (10 hours)

Policy             (20)            10 ms           (1 day)

Corrupt              40            10 ms          (1 hour)

Spam                  2            10 secs         1 mins    

Default for ports of vpn3 172.19.12.12

======================================

Reason          Trigger          Trigger      Blacklisting

                   Size           Period            Period

------          -------          -------      ------------

Authentication       20            1 sec            1 hour

Bad address          20            1 sec            1 hour

Routing              20            1 sec            1 hour

Registration          5           30 sec          10 hours

Policy               20            1 sec             1 day

Corrupt              20           100 ms            1 hour

Spam                  2           10 secs           1 mins    

Related Commands

Command	Description
reason	Enters a submode for configuring a limit to a specific event type on the source (in other words, a port, IP address, VPN, global address space).
trigger-size	Defines the number of the specified events from the specified source that are allowed before the blacklisting is triggered, and blocks all packets from the source.
trigger-period	Defines the period over which events are considered. For details, see the description of the trigger-size command.
timeout	Defines the length of time that packets from the source are blocked, should the limit be exceeded.
show sbc sbe blacklist configured-limits	Lists the explicitly configured limits, showing only the sources configured. Any values not explicitly defined for each source are in brackets.
show sbc sbe blacklist current-blacklisting	Lists the limits causing sources to be blacklisted.

show sbc sbe cac-policy-set

To list detailed information for a given entry in a CAC policy table, use the show sbc sbe cac-policy-set command in Privileged EXEC mode.

show sbc name sbe cac-policy-set [ id [table name [entry id ]] | active [table name [entry id ]] ] [detail]

Syntax Description

name	Specifies the name of the Session Border Controller (SBC) service.
id	CAC policy set ID, the numeric identifier of the CAC policy set to which the table belongs. Valid range is 1 through 2147483647
table name	table specifies the table in the CAC policy set. name specifies name of the table.
entry id	entry specifies the numeric identifier of the CAC entry that you want to display. Displays output in detail format. id is the CAC entry ID.
active	Shows the active CAC policy sets.
detail	Shows the detail information for CAC policy sets.

Command Default

Displaying brief output format is the default.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
Cisco IOS XE Release 2.5	Callee Bandwidth-Field and Caller Bandwidth-Field field were added to output.

Usage Guidelines

There are two output formats: brief (default) and detail. The brief version displays important high-level information for each entry on a single line. The detail version displays policy-set, table, and entry values in detail.

This command allows filters for the policy-set id, the active policy-set, the table name, and the entry id. The default is to display all policy-sets, tables, and entries.

If the entry option is specified, the information is displayed in a detail format.

Examples

The following example displays output in detail format for CAC policy set 1, table 1, and entry 1, including the Callee Bandwidth-Field and Caller Bandwidth-Field fields introduced in Cisco IOS XE Release 2.5:

Router# show sbc SBC1 sbe cac-policy-set 1 table 1 entry 1

SBC Service "SBC1"

CAC Policy Set 1         

  Active policy set: No

  Description: This is a description for cac-policy-set 1

  Averaging period: 60 sec

  First CAC table: 1                             

  First CAC scope: call

  Table name: 1

    Description: 

    Table type: policy-set                      Total call failures: 0

    Entry 1      

    CAC scope: call

    Action: CAC complete                    Number of calls rejected: 0

    Max calls per scope:    Unlimited       Max call rate per scope: Unlimited 

    Max in-call rate:       Unlimited       Max out-call rate:       Unlimited 

    Max reg. per scope:     Unlimited       Max reg. rate per scope: Unlimited 

    Max channels per scope: Unlimited       Max updates per scope:   1         

    Early media:            Allowed         Early media direction:   Both      

    Early media timeout:    None            Transcoder per scope:    Allowed

    Callee Bandwidth-Field: TIAS-to-AS      Caller Bandwidth-Field:  AS-to-TIAS

    Media bypass:                    Allowed   

    Media flag:                      Not Set                     

    Renegotiate Strategy:            Delta            

    Max bandwidth per scope:         Unlimited           

    SRTP Transport:                  Trusted-Only (by default)

    Caller hold setting:             Standard        

    Callee hold setting:             Standard        

    Caller privacy setting:          Never hide           

    Callee privacy setting:          Never hide           

    Caller voice QoS profile:        Default                       

    Caller video QoS profile:        Default                       

    Caller sig QoS profile:          Default                       

    Callee voice QoS profile:        Default                       

    Callee video QoS profile:        Default                       

    Callee sig QoS profile:          Default                       

    Restrict codecs to list:         Default                       

    Restrict caller codecs to list:  Default                       

    Restrict callee codecs to list:  Default                       

    Caller inbound SDP policy:       None

    Caller outbound SDP policy:      None

    Callee inbound SDP policy:       None

    Callee outbound SDP policy:      None

The following example displays in brief format information for active CAC policy set 6:

Router# show sbc SBC1 sbe cac-policy-set active

SBC Service "SBC1"

CAC Policy Set 6         

  Active policy set: Yes

  First CAC table: white-list1                   

  First CAC scope: category

  Table name: white-list1

    Table type: limit category                  Total call failures: 0

    Entry   Match value                         Action                  Failures

    -----   -----------                         ------                  --------

    2       non-emergency                       white-list2                    0

  Table name: white-list2

    Table type: policy-set                      Total call failures: 0

    Entry   Scope                               Action                  Failures

    -----   -----                               ------                  --------

    1       call                                Complete                       0

The following example displays detailed output for active CAC policy set 6:

Router# show sbc SBC1 sbe cac-policy-set active detail

SBC Service "SBC1"

CAC Policy Set 6         

  Active policy set: Yes

  Description: 

  Averaging period: 60 sec

  First CAC table: white-list1                   

  First CAC scope: category

  Table name: white-list1

    Description: 

    Table type: limit category                  Total call failures: 0

    Entry 2      

    Match value: non-emergency

    Action: white-list2                     Number of calls rejected: 0

    Max calls per scope:    10000           Max call rate per scope: 1800      

    Max in-call rate:       Unlimited       Max out-call rate:       Unlimited 

    Max reg. per scope:     Unlimited       Max reg. rate per scope: Unlimited 

    Max channels per scope: Unlimited       Max updates per scope:   Unlimited 

    Early media:            Allowed         Early media direction:   Both      

    Early media timeout:    None            Transcoder per scope:    Allowed

    Media bypass:                    Allowed   

    Media flag:                      Not Set                     

    Renegotiate Strategy:            Delta            

    Max bandwidth per scope:         96000               

    SRTP Transport:                  Trusted-Only (by default)

    Caller hold setting:             Standard        

    Callee hold setting:             Standard        

    Caller privacy setting:          Never hide           

    Callee privacy setting:          Never hide           

    Caller voice QoS profile:        Default                       

    Caller video QoS profile:        Default                       

    Caller sig QoS profile:          Default                       

    Callee voice QoS profile:        Default                       

    Callee video QoS profile:        Default                       

    Callee sig QoS profile:          Default                       

    Restrict codecs to list:         Default                       

    Restrict caller codecs to list:  Default                       

    Restrict callee codecs to list:  Default                       

    Caller inbound SDP policy:       None

    Caller outbound SDP policy:      None

    Callee inbound SDP policy:       None

    Callee outbound SDP policy:      None

  Table name: white-list2

    Description: 

    Table type: policy-set                      Total call failures: 0

    Entry 1      

    CAC scope: call

    Action: CAC complete                    Number of calls rejected: 0

    Max calls per scope:    Unlimited       Max call rate per scope: Unlimited 

    Max in-call rate:       Unlimited       Max out-call rate:       Unlimited 

    Max reg. per scope:     Unlimited       Max reg. rate per scope: Unlimited 

    Max channels per scope: Unlimited       Max updates per scope:   Unlimited 

    Early media:            Allowed         Early media direction:   Both      

    Early media timeout:    None            Transcoder per scope:    Allowed    

    Media bypass:                    Allowed   

    Media flag:                      Not Set                     

    Renegotiate Strategy:            Delta            

    Max bandwidth per scope:         Unlimited           

    SRTP Transport:                  Trusted-Only (by default)

    Caller hold setting:             Standard        

    Callee hold setting:             Standard        

    Caller privacy setting:          Never hide           

    Callee privacy setting:          Never hide           

    Caller voice QoS profile:        Default                       

    Caller video QoS profile:        Default                       

    Caller sig QoS profile:          Default                       

    Callee voice QoS profile:        Default                       

    Callee video QoS profile:        Default                       

    Callee sig QoS profile:          Default                       

    Restrict codecs to list:         mycodecs1                     

    Restrict caller codecs to list:  Default                       

    Restrict callee codecs to list:  Default                       

    Caller inbound SDP policy:       None

    Caller outbound SDP policy:      None

    Callee inbound SDP policy:       None

    Callee outbound SDP policy:      None

Related Commands

Command	Description
show sbc sbe call-policy-set table entry	Displays a summary of the entries associated with the given routing table.

show sbc sbe call branches

To show all the branches on the specified call on SBEs, use the show sbc sbe call branches command in Privileged EXEC mode.

show sbc sbe call call-num branches

Syntax Description

call-num

Specifies the call to display information about.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to display the branches associated with call 2:

Router# show sbc mySbc sbe call 2 branches

SBC Service "mySbc"

Call: 2   

State: active

Type: video

Branch Calling Number Called Number Billing ID

1      102 789 767    -             DAB3C4D153624C7124E1234

2      -              05 659 896  

show sbc sbe call-policy-set

To show the properties associated with a given routing policy set or policy table, use the show sbc sbe call-policy-set command in Privileged EXEC mode.

show sbc sbc-name sbe call-policy-set id table name entry entry-id

Syntax Description

id	Specifies the numeric identifier of the routing policy set or table.
table name	Specifies the name of the table.
entry entry-id	Specifies the numeric identifier of the entry that you want to display.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to display a summary of the entries associated with the given table:

Router# show sbc test sbe call-policy-set 1 table rtgTable entry 1

SBC Service ''test'' 

Policy set 1 table rtgTable entry 1 

Routing table entry 

Match adjacency tekOrig 

Action Routing complete 

Dest Adjacency tekTerm 

Failures 0

Related Commands

Command	Description
debug sbc ips	Configures descriptive text for the CAC-policy-set.
rtg-dst-address-table	Configures the name of the first policy table to process when performing the number analysis stage of policy.
first-number-analysis-table	Configures the name of the first policy table to process when performing the routing stage of policy for subscriber-registration events.

show sbc sbe call-policy-set tables

To list a summary of the call policy tables associated with the given policy set, use the show sbc sbe call-policy-set tables command in Privileged EXEC mode.

show sbc sbc-name sbe call-policy-set policy-set tables

Syntax Description

sbc name	This is the name of the SBC service.
policy-set	The numeric identifier of the call policy set whose tables are to be displayed.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to display a summary of the routing policy tables associated with the given policy set:

Router# show sbc a sbe call-policy-set 2 tables

SBC Service "a"

Policy set 2 tables

Table name    Match type    Description     Total Failures

----------------------------------------------------------

start-table   rtg-src-adj                   0 (0 *)

na-table      na-dst-num                    0 (0 *)

* Numbers in brackets refer to a call being rejected by a

routing or number analysis table because there were no

matching entries in the table.  This is also included in

the total figure. 

show sbc sbe call-policy-sets

To list all of the routing policy sets on the SBE, use the show sbc sbe call-policy-sets command in Privileged EXEC mode.

show sbc sbc-name sbe call-policy-sets

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to list the routing policy sets on the SBE with a configuration that has one call-policy-set:

Router# show sbc test sbe call-policy-sets

SBC Service ''test'' 

Policy Set Description 

--------------------------------------------------------- 

1 

Active policy set = 1 

The following example shows how to list all of the routing policy sets on the SBE with multiple call-policy-sets with descriptions:

Router# show sbc a sbe call-policy-sets

SBC Service "a"

Policy Set     Description

---------------------------------------------------------

1           Call policy set for navtel

2           Call policy set for number analysis

3           Call policy set for h323

Active policy set = 1

Router# 

show sbc sbe call-policy-set table entries

To display a summary of the entries associated with a given table, use the show sbc sbe call-policy-set table entries command in Privileged EXEC mode.

show sbc sbc-name sbe call-policy-set id table name entries

Syntax Description

id	Specifies the numeric identifier of the routing policy set to which the table belongs.
sbc name	This is the name of the SBC service.
name	Specifies the table whose entries are to be displayed.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to display a summary of the entries associated with the given table:

Router# show sbc a sbe call-policy-set 1 table start-table entries

SBC Service ''a'' 

Policy set 1 table start-table entries 

Table class Entry Match Value 

-------------------------------------- 

Routing entry 1 navtel2 

Routing entry 2 navtel1 

Router#

show sbc sbe call-policy-set table entry

To display detailed information for a given entry in a CAC policy table, use the show sbc sbe call-policy-set table entry command in Privileged EXEC mode.

show sbc sbc-name sbe call-policy-set id table name entry

Syntax Description

id	Specifies the numeric identifier of the routing policy set to which the table belongs.
name	Specifies the table whose entries are to be displayed.
sbc name	This is the name of the SBC service.
entry	Specifies the entry index of the table.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to display a summary of the entries associated with the given table:

Router# show sbc mySbc sbe call-policy-set 1 table rtgTable entry 1 

SBC Service ''mySbc'' 

Policy set 1 table rtgTable entry 1 

Routing table entry 

Match adjacency sipOrig 

Action Routing complete 

Dest Adjacency h323Term 

Failures 0

show sbc sbe call-rate-stats

To list all of the current rate of attempted call setups per second over a short period of time (default to 3 seconds,. use the show sbc sbe call-rate-stats command in Privileged EXEC mode.

show sbc sbc-name sbe call-rate-stats

Syntax Description

sbc name

This is the name of the SBC service.

Defaults

Default value is 3 seconds.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to list all of the current rate of attempted call setups per second:

Router# show sbc sbc-1 sbe call-rate-stats

Calls Per Second:

-----------------

Current CPS  10

Maximum CPS  80

Minimum CPS  1

Average CPS 0 

show sbc sbe calls

To list all the calls on the SBEs, use the show sbc sbe calls command in Privileged EXEC mode.

show sbc sbc-name sbe calls

Syntax Description

sbc name

This is the name of the SBC service.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to list the complete call statistics for the current hour:

Router# show sbc a sbe calls

SBC Service ''a'' 

Call State Type Src Adjacency Dest Adjacency 

----------------------------------------------------------------------------- 

393 Activating Audio navtel1 navtel2 

394 Activating Audio navtel1 navtel2 

Router#

show sbc sbe call-stats

To list the statistics for all the calls on the specified SBE, use the show sbc sbe call-stats command in Privileged EXEC mode.

show sbc sbc-name sbe call-stats period

Syntax Description

sbc name

This is the name of the SBC service.

period

Specifies the interval when the statistics display. The possible values are: •current5mins—shows the statistics of the current 5 minute interval. •previous5mins—shows the statistics of the previous 5 minute interval. •current15mins—shows the statistics for the current 5 minute interval and the previous two 5 minute intervals combined. •previous15mins—shows the statistics for the previous 5 minute interval and the previous two 5 minute intervals combined. •currenthour—shows the statistics of the current 5 minute interval and the previous eleven 5 minute intervals combined. •previoushour—shows the statistics of the previous 5 minute interval and the previous eleven 5 minute intervals combined. •currentday—shows the statistics of the current 5 minute interval and the previous two hundred eighty-seven 5 minute intervals combined. •previousday—shows the statistics of the previous 5 minute interval and the previous two hundred eighty-seven 5 minute intervals combined. See Usage Guidelines for more details on how the system accumulates the intervals.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers, and failure statistics were added to the output.

Usage Guidelines

Readings are taken at 5-minute intervals past the hour (that is, 05, 10, 15, and so on). The system keeps buckets that accumulate counts over 5 minutes each. Each bucket is started at 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55 minutes past the hour according to the system clock. The show sbc sbe call-stats command then combines a number of those buckets and displays the sum of those buckets.

For example, if the time is now 12:34, currenthour will apply to the statistics collected since 11:35 and current15mins will apply to statistics collected since 12:20. In this example, previoushour would be 10:35-11:35 and previous15mins would be 12:05-12:20.

Examples

The following example shows how to list the complete call statistics for the current day:

Router# show sbc global sbe call-stats currentday

SBC Service ''global'' 

Active calls:                             0

Activating calls =                        0

Deactivating calls =                      0

Total call attempts =                     8

Failed call attempts =                    8

Successful call attempts =                0

Call routing failed =                     8

Call resources failed =                   0

Call media failed =                       0

Call signaling failed =                   0

Active call failures =                    0

Congestion failures =                     0

Policy control failures:

Total call setup failures =              8

Total call update failures =             0

Call setup failed due to NA =             0

Call setup failed due to rtg =            8

Call setup failed due to CAC =            0

CAC fails due to num call lim =           0

CAC fails due to call rate lim =          0

CAC fails due to num media channels lim = 0 

CAC fails due to num media updates lim =  0

CAC fails due to bandwidth lim =          0

CAC fails due to in-call rate lim =       0

CAC fails due to out-call rate lim =      0

Table 8 show sbc sbe call-stats Field Descriptions 

Field	Description
Active calls	If the period being queried is "current5mins," this is the number of calls currently active at the instant that the query is issued. Otherwise, this is the average number of calls that has been active for the entire period. A call must have been active for at least half of the period in order to count as having been active on average for the entire period. Therefore, this statistic is effectively a count of the number of calls that have been active for half the period or more.
Activating calls	If the period being queried is "current5mins," this is the number of calls currently activating at the instant that the query is issued. Otherwise, this is the average number of calls that have been activating for the entire period. A call must have been activating for at least half of the period in order to count as having been activating on average for the entire period. Therefore this statistic is effectively a count of the number of calls that have been activating for half the period or more.
Deactivating calls	If the period being queried is "current5mins," this is the number of calls that are undergoing deactivation at the instant that the query is issued. Otherwise, this is the average number of calls that have been deactivating for the entire period. A call must have been deactivating for at least half of the period in order to count as having been deactivating on average for the entire period. Therefore this statistic is effectively a count of the number of calls that have been deactivating for half the period or more.
Total call attempts	Call establishment attempts made. A call attempt may have failed in a later summary period. This counter may include failed calls which are not included in the failed call attempt count.
Failed call attempts	Call establishment attempts failed. A failed call attempt may result from a call which was started during a previous summary period. This counter may include call attempts which are not included in the total call attempt count.
Successful call attempts	Total call attempts minus Failed call attempts.
Call routing failed	Call establishment attempts failed due to a routing failure.
Call resources failed	Call establishment attempts failed due to a resource failure.
Call media failed	Call establishment attempts failed due to a media failure.
Call signaling failed	Call establishment attempts failed due to a signaling failure.
Active call failures	Calls failed from an active state. This count includes all deactivation causes other than normal release.
Congestion failures	Call establishment attempts failed due to system congestion.
Total call setup failures	Total number of call setup failures due to Number Analysis, Routing, and CAC Policies.
Total call update failures	Total number of call update failures due to CAC Policies.
Call setup failed due to NA	Total number of call setup failures due to Number Analysis policies.
Call setup failed due to rtg	Total number of call setup failures due to routing policies.
Call setup failed due to CAC	Total number of call setup failures due to CAC policies.
CAC fails due to num call lim	Total number of call setup failures due to CAC call limits.
CAC fails due to call rate lim	Total number of call setup failures due to CAC call rate limits.
CAC fails due to num media channels lim	Total number of call setup failures due to CAC number of media channels limits.
CAC fails due to num media updates lim	Total number of call setup failures due to CAC number of media updates limits.
CAC fails due to bandwidth lim	Total number of call setup failures due to CAC Bandwidth Limits.
CAC fails due to in-call rate lim	Total number of failures due to the CAC limit on the rate of in-call messages.
CAC fails due to out-call rate lim	Total number of failures due to the CAC limit on the rate of out-of-call requests.

Related Commands

Command	Description
show sbc sbe call-rate-stats	Lists all the calls on the SBEs.

show sbc sbe codec-list

To show information about the codec lists that are configured on the SBE, use the show sbc sbe codec-list command in Privileged EXEC mode.

show sbc sbc-name sbe codec-list list-name

Syntax Description

sbc name	This is the name of the SBC service.
list-name	Specifies the name of the codec list.

Command Default

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to display information about the codec list named my_codecs.

Router# show sbc mySbc sbe codec-list my_codecs

SBC Service "mySbc"

Codec list "my_codecs" (Legitimate codecs)

  Codec Name                Min Packetization Period

  ==========                ========================

  PCMU                      20ms

  G729                      10ms

Related Commands

show sbc sbe gates

To list the gates created on the SBE, use the show sbc sbe gates command in Privileged EXEC mode.

show sbc sbc-name sbe gates

Syntax Description

sbc name

This is the name of the SBC service.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to list the gates created on the SBE:

Router# show sbc a sbe gates

SBC Service ''a'' 

Billing correlator A: 0x4803FFFFFF8EFFFFFFD12020202020202030000000000000000000 

000544 

Billing correlator B: 0x4803FFFFFF8EFFFFFFD12020202020202030000000000000000000 

000543 

Media Gateway is collocated 

Number of flow pairs = 1 

Router# 

show sbc sbe h323 timers

To display a list of H.323 timer configuration, use the show sbc sbe h323 command in Privileged EXEC mode.

show sbc sbc-name sbe h323 timers

Syntax Description

sbc name

This is the name of the SBC service.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how the show sbc sbe h323 timers command is used to display a list of H.323 timer configuration:

Router# show sbc test sbe h323 timers

SBC Service ''test'' 

H.323 Timers 

Global scope 

adjacency retry timeout 30000 

h225 timeout setup 4000 

h225 timeout proceeding 10000 

h225 timeout establishment 180000 

ras rrq ttl 60 

ras rrq keepalive 45000 

ras retry count (arq) 2 

ras timeout (arq) 5000 

ras retry count (brq) 2 

ras timeout (brq) 3000 

ras retry count (drq) 2 

ras timeout (drq) 3000 

ras retry count (grq) 2 

ras timeout (grq) 5000 

ras retry count (rrq) 2 

ras timeout (rrq) 3000 

ras retry count (urq) 1 

ras timeout (urq) 3000 

Adjacency tekOrig 

H225 Timeout Setup 4000 

H225 Timeout Proceeding 10000 

H225 Timeout Establishment 180000 

RAS RRQ TTL 60 

RAS RRQ Keepalive 45000 

RAS Retry Count (arq) 2 

RAS Timeout (arq) 5000 

RAS Retry Count (brq) 2 

RAS Timeout (brq) 3000 

RAS Retry Count (drq) 2 

RAS Timeout (drq) 3000 

RAS Retry Count (grq) 2 

RAS Timeout (grq) 5000 

RAS Retry Count (rrq) 2 

RAS Timeout (rrq) 3000 

RAS Retry Count (urq) 1 

RAS Timeout (urq) 3000 

show sbc sbe hold-media-timeout

To show the configured duration of the media timeout timer for on-hold calls, use the show sbc sbe hold-media-timeout command in Privileged EXEC mode.

show sbc sbc-name sbe hold-media-timeout

Syntax Description

sbc-name

Specifies the SBC service.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows sample data for the media timeout timer for on-hold calls:

Router# show sbc mysbc sbe hold-media-timeout

SBC Service "mysbc"

SBE On-hold media timeout duration is: 10 seconds

Router# 

show sbc sbe hunting-trigger

To show the H.323 or SIP hunting triggers at the global level, use the show sbc sbe hunting-trigger command in Privileged EXEC mode.

show sbc sbc-name sbe {h323 | sip} hunting-trigger

Syntax Description

sbc-name	Specifies the SBC service.
h323	Specifies H.323 hunting-trigger.
sip	Specifies SIP hunting-trigger.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows sample data for the media timeout timer for on-hold calls:

Router# show sbc uut105-1 sbe h323 hunting-trigger 

H.323 Hunting Triggers 

---------------------- 

noBandwidth 

unreachableDestination 

destinationrejection 

noPermission 

badFormatAddress 

securityDenied 

Related Commands

Command	Description
hunting-trigger	Configures failure return codes to trigger hunting.

show sbc sbe media-gateway-associations

To list all the media gateways associated with this SBE and statistics associated with the media gateway, use the show sbc sbe media-gateway-associations command in Privileged EXEC mode.

show sbc sbc-name sbe media-gateway-associations

Syntax Description

sbc-name

Specifies the SBC service.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to list all the media gateways associated with this SBE and statistics associated with the media gateway:

Router# show sbc test sbe media-gateway-associations 

SBC Service ''test'' 

Media gateway 200.200.207.101:2944 

Gateway Protocol = megaco 

Transport Protocol = UDP 

Local Address = 88.104.1.3:2944 

Sent Received Failed Retried 

Requests 3687 1 0 0 

Replies 1 3686 - 0 

show sbc sbe media-gateways

To list the gateway configuration and attachment status on SBE, use the show sbc sbe media-gateways command in Privileged EXEC mode.

show sbc sbc-name sbe media-gateways

Syntax Description

sbc-name

Specifies the SBC service.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows how to list the gateway configuration and attachment status on SBEs:

Router# show sbc mySbc sbe media-gateways

SBC Service "mySbc"

  Configured Gateway 10.0.0.1 

  Configured Gateway 100.1.0.1

  Configured Gateway 172.3.4.9

show sbc sbe mib

To show all or a specific Session Border Controller (SBC) MIB, use the show sbc sbe mib command in Privileged EXEC mode.

show sbc sbc-name sbc sbe mib [ all | bcacalenttable | bcacalassntable | bcacallstntable | bmenttable | bmgatetable | bmsdpattribtable | bmsdpmatchtabletable | bmsdppolicytable | cacconfigsettable | cacentitytable | cacpolicyentries | cacpolicytabletable |csbcqosprofiletable | h323enttable | icccainstancetable | iccpolcystatstable | rpsrtgactiontable | rpsrtgtabletable | rpsvalidationentrytable | rpsvalidationtabletable | sipchenttable | siptmenttable | sudblocalidtable | sudbsubscribertable | vpssauthrealmtable | vpssheaderfilterelementtable | vpssheaderfilterprofiletable | vpssinstancetable | vpssmethodfilterelementtable | vpssmethodfilterprofiletable | vpssoptionfilterelementtable | vpssoptionfilterprofiletable | vpssparamactionset | vpssparameteraction | vpssprioritytable ]

Syntax Description

sbc-name

Specifies the SBC service.

Defaults

No default behavior or values

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.4	This command was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.

Examples

The following example shows the output of the show sbc sbe mib all command:

Router# show sbc test sbe mib all 

bcaCalAssnTable.

---------------------------------------------

---------------------------------------------

No Entry found.

bcaCalEntTable.

---------------------------------------------

---------------------------------------------

bcaCalEntTableApplIndex = 1

bcaCalEntTableRowStatus = 1

bcaCalEntTableAdminStatus = 1

bcaCalEntTableOperStatus = 1

bcaCalEntTablesocketIndex = 1

bcaCalEntTableSocketJoinStatus = 4

bcaCalEntTableNMRIndex = 1

bcaCalEntTableNMRJoinStatus = 4

bcaCalEntTableMGFailureTimerDuration = 4

bcaCalEntTableRequestTimeoutInterval = 10000

bcaCalEntTableAllowedMG = All