1. The B2BUA sets the transport protocol of the m= line to the transport protocol of the selected egress profile.
2. If the value of listen-port of the selected egress profile is not zero, the B2BUA sets the port of the m= line to the value of listen-port. If the value of listen-port is zero, the port in the m= line is chosen from a steering port of the egress realm.
3. The B2BUA adds an a=setup attribute to the SDP. The value of this attribute is determined by the value of the preferred-setup-role ACLI command. For example, if the value of preferred-setup-role is passive (the default value) the B2BUA adds the attribute a=setup:passive.
4. The B2BUA performs NAT on the MSRP Universal Resource Identifier (URI) in the a=path attribute.

   The B2BUA does not include an a=fingerprint in the offer SDP if the selected egress profile has TCP/TLS/MSRP transport protocol. However, if the egress profile specifies both TCP/MSRP and TCP/TLS/MSRP the B2BUA selects the TCP/TLS/MSRP transport protocol, resulting in an egress offer containing an m= line with TCP/TLS/MSRP transport protocol. The B2BUA offers only a single media line, TCP/MSRP or TCP/TLS/MSRP. The B2BUA does not perform recursion (that is, first initiation attempt with TCP/TLS/MSRP and re-attempt with TCP/MSRP if first attempt is rejected).

In compliance with RFC4145 and RFC6135, the SBC can act as offerer or answerer when using SDP to negotiate MSRP sessions. As answerer, the SBC receives MSRP signaling from a UA that wants to start an MSRP session. As offerer, it acts as an MSRP B2BUA and starts an MSRP session. Within a connection-oriented media architecture, SDP negotiates these roles from the a=setup parameter, which determines which end station is responsible for initiating the session as active, and which is passive.

As an MSRP session offerer, a user agent client can follow RFC 4145 and include an a=setup attribute in a MSRP media line, or it may follow the default connection direction specified in RFC 4975, which specifies that the endpoint that sent the original offer is responsible for connecting to its remote peer. The B2BUA, in contrast, always includes an a=setup attribute in its SDP offer. You can configure this setup value on the SBC by configuring the preferred-setup-role parameter within the tcp-media-profile, profile-list element. Parameter values include:

• active—The SBC explicitly requests the active role.
• passive—The SBC sends actpass to the UA as its setup role. This allows the SBC to be either active or passive, depending on the response from the UA. If the UA responds requesting active, the SBC takes the passive role, and vice-versa. This actpass value ensures that the SBC can either:
  • Initiate an outgoing connection to a remote UA
  • Accept an incoming connection from a remote UA

  The absence or value of the “a=setup” attribute in the answer SDP received from the remote UA determines the actual role performed by the SBC, as specified by RFC 4145.

  • When the SBC receives “a=setup:active”, it performs the passive role, listening on the advertised port.
  • When the SBC receives “a=setup:passive”, it performs the active role.
  • When the SBC receives an offer SDP with the attribute a=setup:actpass attribute, it sets the a=setup attribute of its SDP answer to the value set in the preferred-setup-role parameter.
  • When the SBC receives an answer SDP that does not include an a=setup attribute, it assumes that the user agent server does not support connection negotiation per RFC 4145, takes the active role as specified in RFC 4975, and makes the outgoing connection.

The default and recommended preferred-setup-role configuration is passive, which allows the remote UA to choose its role.

Whether taking the active or passive role on the caller side (ingress), the SBC initiates an outgoing connection towards the callee (egress) on-demand and its MSRP requests to the callee. Again, the SBC as B2BUA sends its SDP offer with the setup line using its configured value.

Key behavior also includes:

• When active, the SBC refers to the applicable tcp-media-profile, profile-list to see if you have configured the listen-port. If you have configured a listen-port, the SBC listens for traffic on that port. By default, the listen-port is set to 0, which causes the SBC to listen using a port it allocates from the steering-pool of the applicable realm.
• When it is the answerer, the SBC is forced into a specific role and does not always use the configured preferred-setup-role value. The SBC uses the actpass value to negotiate in scenarios where:
  • The remote UA is negotiating the connection using the passive value or,
  • When the remote UA is using passive improperly during the negotiation, which is prohibited by RFC 6135.
• Sending “a=setup:actpass” value in an offer from the SBC is also compliant if the remote UA does not support the COMEDIA mechanism described in RFC 4145, and is, therefore, always a passive endpoint. If the remote UA sends back an answer with SDP that indicates the role it is going to take, the SBC takes the other role.
• When configured to propose actpass, via the passive setting, it is possible that SBC could end up performing the active role on both the ingress and egress sides of the session. In this case, there may not be any MSRP request received from the UA on one side of the SBC to trigger the outgoing connection on the other side. It is, therefore, mandatory for the SBC to establish a connection right after successful negotiation of offer/answer exchange and send an empty MSRP request on the established connection. This behavior is in compliance with RFC 4145.
• The SBC initiates the egress outbound TCP connection right after it receives the answer SDP from the ingress remote UA. The TCP initiation processing from the data path happens when the host sends a MSRP session provision message to the data path after receiving the answer SDP. From the call flow perspective, this outbound TCP initiation by the SBC can happen before it sends any SIP ACK message.

When the SBC takes the active role, it can initiate an MSRP TCP/TLS outbound connection towards the remote MSRP UA immediately after it receives the answer SDP. But the remote UA may not be ready to accept the MSRP connection request on its advertised IP/port right away. Per RFC 3264, a SIP UA should listen on its advertised IP and port immediately to receive connections, but there are end stations that do not comply with this. To alleviate the risk of failed sessions, you can configure the conn-setup-delay-timer parameter under the msrp-config within the media-manager element to wait the configured number of milleseconds before initiating the outbound connection.

When setting up sessions with UAs that are not compliant in this respect, the TCP connection attempt from the SBC can fail. This can happen if the SBC receives the TCP-RST from the remote UA for the SYN it sent, and the stops attempting the connection. This presents the risk of experiencing SIP session and MSRP connection termination, for example, when the flow guard timer expires. A remote UA cannot send any MSRP (instant) message towards the other participant through the SBC until the SBC successfully establishes the connection.

You can avoid this issue and provide flexibility for non-standard UAs by configuring the conn-setup-delay-timer parameter. This setting delays the initiation of the outbound TCP connection towards the remote UA until the SBC takes the active role. The default is 0 and the range is from 0 to 1500 milleseconds.

Configure this value if you have UA’s that do not listen on advertised ports within this window to ensure the SBC:

• Delays TCP initiation.
• Buffers any data received on the other call leg, waiting for the connection to be established.
• Sends this data after the timer expires.

The MSRP B2BUA supports sharing of a single TCP connection by multiple MSRP sessions. In such a topology, each TCP connection maintains a list active MSRP sessions.

With regard to the above figure, the upper Oracle Communications Session Border Controller’s TCP connection between Endpoint 1 and the MSRS B2BUA is shared by 2 MSRP sessions. At bottom, each MSRP session uses a separate TCP connection. When the B2BUA assumes the active role, it always initiate a separate connection to the MSRP endpoint peers, endpoints 2 and 3 as shown above.

When the list of active MSRP sessions for a shared TCP connection becomes empty as a result of SIP session terminations or disconnections of peer TCP connections, B2BUA disconnects the shared TCP connection. If the shared connection is disconnected by the peer, the B2BUA disconnects all the separate TCP connections it initiated for the MSRP sessions that use the shared connection.

When the B2BUA is in passive mode, it listens for incoming connection from the active party, monitoring the port specified by the listen-port ACLI command.

When the B2BUA is in active mode, it makes the connection to the passive party, selecting a port allocated from the steering-pool of the applicable realm.

The Oracle Communications Session Border Controller (SBC) requires the Connection Establishment for Media Anchoring (CEMA) extension (RFC6714) and the session-id matching mechanism to allow the SBC to exchange Message Session Relay Protocol (MSRP) messages through middleboxes that do not act as MSRP Back to Back User Agents (B2BUA). When such a middlebox passes the MSRP messages through without updating the SDP a=path attribute, the SBC cannot establish a TCP connection through the middlebox. The CEMA mechanism makes the connection possible. In a scenario where the middlebox does update the SDP a=path attribute, the MSRP messages will not pass validation and will be dropped. The Session-id matching mechanism prevents that situation. The SBC supports this functionality only on Virtual Machines.

With the CEMA extension enabled, the SBC detects the presence of a middlebox that anchors the media and does not update the SDP a=path attribute by comparing the SDP c and m lines to the SDP a=path attribute. When the CEMA-enabled SBC plays the active role in establishing the TCP connection it establishes the connection to the endpoint identified by the c and m lines instead of the a=path.

Figure 22-2 Signaling Flow with a Middlebox and CEMA Enabled

Figure 22-3 MSRP Flow with a Middlebox and CEMA Enabled

To-path Authority Validation

The presence of middleboxes that anchor the media and update the SDP a=path attribute to match the updated SDP c and m lines cannot be detected in the signaling plane. An MSRP B2BUA that is not enabled for CEMA correctly sets up TCP connections to the middlebox because the SDP a=path attribute points to the middlebox. Because the middleboxes do not accordingly update the MSRP message To-Path headers, MSRP messages passing through such a middlebox cannot validate because the authority part of the To-Path header does not match the authority part of the SDP a=path attribute. In such scenarios the validation of the MSRP URI is based only on the session-id part of the MSRP URI, the MSRP scheme, and transport (Session-Id matching).

To solve the problem, the tcp-media-profile configuration object includes the msrp-sessmatch attribute that controls whether or not the URI comparison of the To-Path header in the MSRP messages received from the respective realm includes the authority part.

• Disabled (default)-The MSRP URI comparison between the SDP a=path attribute and the To-Path header in the MSRP messages received from a realm includes the MSRP URI scheme, authority IP address, port number, session-id, and transport. If the comparison is unsuccessful and the sender requires a report, the SBC returns an MSRP 481 error response to the sender.
• Enabled-The MSRP URI comparison between the SDP a=path attribute and the To-Path header in the MSRP messages received from a realm includes only the MSRP URI scheme, session-id, and transport. If the comparison is unsuccessful and the sender requires a response, the SBC sends an MSRP 481 error response to the sender. If you enable msrp-sessmatch, you must disable msrp-cema-support.

Figure 22-4 Signaling Flow with Session Matching Enabled

Figure 22-5 MSRP Flow with Session Matching Enabled

You can configure the Oracle Communications Session Border Controller (SBC) to use an allowlist to filter media types and sub-types that you want the system to allow. During SIP signaling, the SBC removes media types not listed on the allowlist from the SDP offer. The SBC also rejects Message Session Relay Protocol (MSRP) SEND requests that announce media types in the MSRP content-type header other than those negotiated during the SDP offer-answer exchange. The SBC supports this functionality only on Virtual Machines.

Use the msrp-types-allowlist parameter in the tcp-media-profile configuration to set a list of media types and sub-types that you want the system to accept in MSRP messages. Each entry represents one media type and sub-type. When the parameter contains a valid value, the system checks that incoming MSRP SEND requests contain only the media types specified in the SDP a=accept-types attribute. Leave the msrp-types-allowlist parameter empty to tell the system not to perform any media types filtering. Use the asterisk character (*) to allow all MSRP media types. Valid values: empty | MsrpMediaTypeList | *. Default: empty.

The SBC does not provide filtering for the attributes that may accompany a media type, for example, the attribute 'charset' in,text/html;charset=ISO-8859-1. When an SDP offer contains a media type on the allowlist that includes attributes, the SBC does not touch the attributes.

To set a limit on the Message Session Relay Protocol (MSRP) size of the message that the Oracle Communications Session Border Controller (SBC) can receive from a given realm, the tcp-media-profile configuration includes the msrp-message-size, msrp-message-size-file, and msrp-message-size-enforce options. The SBC supports this functionality only on Virtual Machines.

The msrp-message-size-enforce parameter, when enabled, performs byte counting on the MSRP messages to enforce compliance with the negotiated maximum MSRP message size. The negotiated maximum MSRP message size is the minimum between the SDP a=max-size attribute value (if one is provided by the B2BUA) and the configured value for msrp-message-size or msrp-message-size-file. If the SBC detects that the actual size of the MSRP chunk does not match the negotiated maximum size, it immediately stops forwarding the chunk. When the MSRP session is a file transfer, the SIP session terminates by sending a BYE on both the originating and the terminating legs.

1. From superuser mode, use the following command sequence to access 
msrp-config configuration mode. While in msrp-config mode, you configure global MSRP behavior.

   ORACLE# configure terminal
   ORACLE(configure)# media-manager
   ORACLE(media-manager)# msrp-config
   ORACLE(msrp-config)# ?
   state                     state
   uri-translation           perform translation of MSRP URI
   session-inactivity-timer  timer value (seconds) for session inactivity
 monitoring period
   conn-setup-delay-timer    timer value (seconds) to wait for UA to enter session negotiation
   msrp-kpi                  To enable MSRP kpi statistics
   double-port-allocation    To allocate 2 ports for MSRP calls
   select                    select msrp config to edit
   no                        delete msrp config
   show                      show msrp config
   done                      write msrp config information
   exit                      return to previous menu
   ORACLE(msrp-config)#

2. Use the state parameter to enable MSRP operations.

   Retain the default value, enabled, to enable MSRP operations.

   If necessary, you can use disabled to temporarily suspend all MSRP operations.

   ORACLE(msrp-config)# state enabled
   ORACLE(msrp-config)#

3. Use the uri-translation parameter to enable or disable NAT of URIs found in the From-Path and To-Path headers of MSRP requests and responses, and in a=path attributes found in SDP offers.

   NAT is enabled by default.

   Retain the default value (enabled) to enable NAT; use disabled to disable NAT.

   ORACLE(msrp-config)# uri-translation enabled
   ORACLE(msrp-config)#

4. Use the session-inactivity-timer parameter in connection with the 
msrp-delayed-bye-timer parameter to implement the delayed transmission of SIP BYE requests, thus establishing a configurable transition interval allowing for the completion of active MSRP sessions.

   The session-inactivity-timer parameter specifies the maximum inactivity interval (defined as the absence of transmitted data) tolerated before the MSRP connection is terminated.

   Retain the default value (5), or specify another inactivity interval within the range 5 to 10 seconds.

   ORACLE(msrp-config)# session-inactivity-timer 7
   ORACLE(msrp-config)#

5. Use the conn-setup-delay-timer parameter to specify the maximum time before the system sets up a session with the UA even though it has not received any input or response from that UA.

   Retain the default value (0), or specify another inactivity interval within the range 0 to 1500 seconds.

   ORACLE(msrp-config)# conn-setup-delay-timer 7
   ORACLE(msrp-config)#

6. Use the msrp-kpi parameter to enable MSRP KPI statistics.

   Retain the default value, disabled, for standard MSRP statistics.

   If necessary, you can use enabled to enable MSRP KPI statistics.

   ORACLE(msrp-config)# double-port-allocation enabled
   ORACLE(msrp-config)#

7. Use the double-port-allocation parameter to allow the system to assign two steering-pool ports for MSRP sessions.

   Retain the default value, disabled, for normal steering pool port assignment.

   If necessary, you can use enabled to allow the system to assign two steering-pool ports for MSRP sessions.

   ORACLE(msrp-config)# double-port-allocation enabled
   ORACLE(msrp-config)#

8. Use done, exit, and verify-config to complete MSRP global configuration.
9. If you wish to implement the delayed transmission of SIP BYE requests, use the following command sequence to access sip-config configuration model

   ORACLE# configure terminal
   ORACLE(configure)# session-router
   ORACLE(session-router)# sip-config
   ORACLE(sip-config)#

10. Use the msrp-delayed-bye-timer parameter to enable the delayed transmission of SIP BYE requests, thus establishing a configurable transition interval allowing for the completion of active MSRP sessions.

    The msrp-delayed-bye-timer parameter specifies the maximum delay period allowed before transmitting the delayed BYE request.

    Retain the default value (15), or specify another delay period within the range 1 to 60 seconds.

    Delayed transmission of BYE requests is enabled by default. Use the special value of 0 to disable delay, and transmit BYE requests immediately upon receipt.

    ORACLE(sip-config)# msrp-delayed-bye-timer 20
    ORACLE(sip-config)#

The tcp-media-profile defines Message Session Relay Protocol (MSRP) operations within a realm. You specify settings that are common to every tcp media profile, as well as optional settings that you use to customize a particular tcp media profile.

1. Access the tcp-media-profile configuration element.

   ORACLE# configure terminal
   ORACLE(configure)# media-manager
   ORACLE(session-router)# tcp-media-profile
   ORACLE(tcp-media-profile)# 

2. Use the name parameter to provide a unique identifier for this TCP Media Profile instance.

   ORACLE(tcp-media-profile)# name tlsMSRP
   ORACLE(tcp-media-profile)#

3. Use the media-type parameter in conjunction with the transport-protocol parameter to identify the media-types and transport protocols (found in the SDP media description, m=, field as described in RFC 4566, SDP: Session Description Protocol) subject to this TCP Media Profile.

   media-type identifies the media subject to this TCP Media Profile. Retain the default value, message, for MSRP operations.

   transport-protocol identifies the transport layer protocols subject to this TCP Media Profile. Use either TCP/MSRP to specify unsecured TCP traffic or TCP/TLS/MSRP to specify secured, encrypted TLS traffic.

   ORACLE(tcp-media-profile)# profile-list
   ORACLE(profile-entry)#media-type message
   ORACLE(profile-entry)#media-type

   ORACLE(profile-entry)# transport-protocol TCP/TLS/MSRP
   ORACLE(profile-entry)#

4. When the transport-protocol is TCP/TLS/MSRP, use the tls-profile parameter to identify the TLS profile that specifies the cryptographic resources available to support TLS operations.

   This parameter can be safely ignored if transport-protocol is TCP/MSRP.

   ORACLE(profile-entry)# transport-protocol tcp/msrp
   ORACLE(profile-entry)#

5. When the transport-protocol is TCP/TLS/MSRP, use the require-fingerprint parameter to enable or disable endpoint authentication using the certificate fingerprint methodology defined in RFC 4572, Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP).

   By default, mutual authentication is disabled.

   This parameter can be safely ignored if transport-protocol is TCP/MSRP.

   ORACLE(profile-entry)# require-fingerprint enabled
   ORACLE(profile-entry)#

6. Use the listen-port parameter to identify the TCP port monitored by the B2BUA for incoming MSRP connections. The 0 default value indicates that the B2BUA will choose the listening port from the steering pool of the realm (which the tcp-media-profile belongs to). Valid values: 0-65535. Default: 0.

   ORACLE(profile-entry)# listen-port 43000
   ORACLE(profile-entry)#

7. Use the preferred-setup-role parameter to specify the value the B2BUA uses for the a=setup attribute when negotiating the setup up role, regardless of the role (offerer or answerer) assumed by the B2BUA in the SDP offer- answer exchange.

   ORACLE(profile-entry)# preferred-setup-role passive
   ORACLE(profile-entry)#

   The value of preferred-setup-role is used for the value of the a=setup attribute when the SBC makes an offer SDP and when the SBC replies to an offer SDP that has a=setup:actpass. It is not used when the SBC is forced into a role by the offerer, that is, if the offerer sends a=setup:active, the SBC must answer with a=setup:passive (and vice versa). Valid values: passive | active. Default: passive.

   • Passive—Recommended. Indicates that the B2BUA accepts an incoming connection. Indicates that the system can either initiate an outgoing connection to a remote UA or accept an incoming connection from a remote UA. The role performed by the system, however, is ultimately determined by the value of the “a=setup” attribute in the answer SDP received from the remote UA.
   • Active—Indicates that the B2BUA creates an outgoing connection.
8. Use the msrp-cema-support parameter to specify whether or not the SBC negotiates support for the CEMA extension (RFC6714) for TCP or TLS connections to and from the realm associated with the current TCP media profile. Enable the CEMA extension to enable the SBC to exchange MSRP traffic through middleboxes that anchor the media, but do not touch the SDP a:path attribute. Valid values: enabled | disabled. Default: disabled.

   ORACLE(profile-entry)# msrp-cema-support enabled
   ORACLE(profile-entry)#

9. Use the msrp-sessmatch parameter to specify whether or not the SBC validates the MSRP To-Path header based only on the session-id field and MSRP transport type of the MSRP URI (and not also on the IP address and port number in the authority part of the MSRP URI). Sessmatch enables the SBC to exchange MSRP traffic through Middleboxes that anchor the media and also adjust the SDP a=path attribute. Valid values: enabled | disabled. Default: disabled.

   ORACLE(profile-entry)# msrp-sessmatch enabled
   ORACLE(profile-entry)#

10. Use the msrp-message-size-enforce parameter to specify one element in an allowlist of allowed MSRP media types. Media types not included on the allowlist will be removed from the SDP a=accept-types attribute of the SDP offers. A "*" indicates that all MSRP media types are allowed. When left empty, it indicates that no media types filtering is performed. Valid value: MsrpMediaTypeList.

    ORACLE(profile-entry)# msrp-message-size-enforce enabled
    ORACLE(profile-entry)#

11. Use the msrp-message-size parameter to specify the maximum size (in bytes) that MSRP is allowed to negotiate for the messages. It represents the maximum limit for the SDP a=max-size attribute, for the "size" token of the SDP a=file-selector attribute and MSRP Byte-range header. A value of 0 indicates that no maximum limit is enforced. Valid values: 0-4,000. Default: 0.

    ORACLE(profile-entry)# msrp-message-size 2000
    ORACLE(profile-entry)#

12. Use the msrp-message-size-file parameter to specify whether MSRP messages exceeding the negotiated size are rejected, respectively whether MRSP file transfers will be aborted when the negotiated size is exceeded. A value of 0 indicates that no maximum limit is enforced. Valid values: 0-4G. Default: 0.

    ORACLE(profile-entry)# msrp-message-size-file 4
    ORACLE(profile-entry)#

13. Use the msrp-types-allowlist parameter to specify a list of registered MSRP media types (RFC4975) supported for the ingress realm.

    ORACLE(profile-entry)# msrp-types-allowlist <listname>
    ORACLE(profile-entry)#

14. Use done, exit, and verify-config to complete tcp-media-profile configuration.

1. From superuser mode, use the following command sequence to access 
realm-config configuration mode. While in realm-config mode, you assign a 
tcp-media-profile to a realm.

   ORACLE# configure terminal
   ORACLE(configure)# media-manager
   ORACLE(media-manager)# realm-config
   ORACLE(realm-config)#

2. Use the select command to identify the target realm.
3. Use the tcp-media-profile parameter to assign a specific, named 
tcp-media-profile to the target realm.

   ORACLE(realm-config)# tcp-media-profile tlsMutualAuth
   ORACLE(realm-config)#

4. Use done, exit, and verify-config to complete tcp-media-profile assignment.

1. Access the tls-profile configuration element.

   ORACLE# configure terminal
   ORACLE(configure)# security
   ORACLE(security)# tls-profile
   ORACLE(tls-profile)# 

2. Use the name parameter to provide a unique identifier for this TLS Profile instance.

   ORACLE(tls-profile)# name tlsMutualAuth
   ORACLE(tls-profile)#

3. If the require-fingerprint attribute of the tcp-media-profile is set to enabled, use the mutual-authenticate parameter to enable mutual authentication.

   ORACLE(tls-profile)# mutual-authenticate enabled
   ORACLE(tls-profile)#

4. Retain default values for other parameters.
5. Type done to save your configuration.
6. Repeat Steps 1 through 5 to configure additional tls-profiles as required.

When you want to see MSRP flow, cumulative, and state counts statistics for the Oracle Communications Session Border Controller (SBC), use the show mbcd statistics, show msrp statistics, and show mbcd msrp commands.

The show mbcd statistics command displays MSRP flow counts for the current statistics window. For example:

ORACLE# show mbcd statistics
16:38:49-145
MBCD Status                -- Period -- -------- Lifetime --------
                 Active    High   Total      Total  PerMax    High
Client Sessions       1       1       0          1       1       1
...
Flow-MSRP             2       2       0          2       2       2
...
Flow Rate = 0.0
Load Rate = 0.0
ORACLE#

The show msrp statistics command can display the cumulative count for dozens of statistics. The system always displays the default set of statistics, even when the value is zero, plus any other statistics that do have a value. For example:

ORACLE# show msrp statistics
                       FD Table Size: 0
               Session-ID Table Size: 0
               Total Active Sessions: 0
             Maximum Active Sessions: 0
          Total Established Sessions: 0
          Total Provisioned Sessions: 0
             Total Finished Sessions: 0
          Total Accepted Connections: 0
         Total Connected Connections: 0
          Total Released Connections: 0
             Total Requests Received: 0
                 Total Requests Sent: 0
            Total Responses Received: 0
                Total Responses Sent: 0
            Total Global Buffer Data: 0
          Total MSRP Nat Flows Added: 0
        Total MSRP Nat Flows Deleted: 0
          Total Active CEMA Sessions: 0
Total Established Sessmatch Sessions: 0
Total Provisioned Sessmatch Sessions: 0
     Total Active Sessmatch Sessions: 0

The show mbcd msrp command displays MSRP session state counts. For example:

ORACLE# show mbcd msrp
14:35:15-194
MSRP Statistics                          ---- Lifetime ----
                                  Recent      Total  PerMax
Provision Sessions Unreleased          0          0       0
Listening Sessions Unreleased          0          0       0
Established Sessions Unreleased        0          0       0
Closed Sessions Unreleased             0          0       0
Finished Sessions Unreleased           0          0       0
PPM Messages Received                  0          0       0
PPM Messages Processed                 0          0       0
PPM Messages Sent                      0          0       0
PPM Messages Send Fail                 0          0       0

MSRP Flow States                        -- Period -- -------- Lifetime --------
                              Active    High   Total      Total  PerMax    High
MSRP-FlowListen                    0       0       0          0       0       0
MSRP-FlowProvision                 0       0       0          0       0       0
MSRP-FlowProvisioned               0       0       0          0       0       0
MSRP-FlowEstablished               0       0       0          0       0       0
MSRP-FlowShared                    0       0       0          0       0       0
MSRP-FlowClose                     0       0       0          0       0       0
MSRP-FlowFinished                  0       0       0          0       0       0
MSRP-FlowReleased                  0       0       0          0       0       0
MSRP-FlowWaitDrop                  0       0       0          0       0       0

You can configure the system to extend the show mbcd msrp output. After configuration, the system provides additional arguments. The additional arguments provide a broad set of system-wide or realm-based statistics, and include SEND and REPORT statistics. See "Extended MSRP Statistics" in the ACLI Configuration Guide and "MSRP Protocol Performance" in the Maintenance and Troubleshooting Guide for more information, including configuration.

You can configure the Oracle Communications Session Border Controller (SBC) to display additional protocol statistics on MSRP methods using SNMP and CLI.

The SBC displays MSRP traffic statistics on a per-window, periodic basis (100 seconds) and on a lifetime basis. The SBC correlates statistics using MSRP method type, including SEND and REPORT, and on a per-realm and system-wide basis. You can display the statistics using the ALCI by specifying method and basis. You can also collect the statistics using SNMP walks. Use the reset all and reset mbcd commands to reset MSRP KPI statistics.

The SBC supports Extended MSRP statistics on the following physical platforms, only:

• Acme Packet 4600
• Acme Packet 4900
• Acme Packet 6100
• Acme Packet 6300
• Acme Packet 6350
• Acme Packet 6400

The SBC uses SIP and SDP to signal MSRP media traffic. MSRP traffic includes:

• MSRP SEND requests, which present the following methods:
  • CHAT
  • IS-TYPING
  • RECEIPT
• REPORT traffic, which indicates delivery success and failure
• Transaction response status traffic, which indicates success and failure in response to a request

You can use extended MSRP statistics to segregate MSRP method traffic, track cause values and byte counts on a receive and transmit basis. This allows you to analyze sessions within the context of specific transaction types, across relays, and across MSRP chunks.

The MSRP complexities that extended KPIs can help you analyze include:

• The session-oriented nature of MSRP requires the use of Message-ID and byte ranges, if present, to correlate traffic.
• Cause codes can change over the course of a session, based on circumstances across the relay path or the endpoints.
• SEND requests deliver a complete message or a chunk, which is a portion of a complete message, which can be supported by monitoring byte ranges to correlate components of associated requests.
• REPORT requests report on the status of a previously sent message, or a range of bytes inside a message.

You enable extended MSRP statistics by enabling the msrp-kpi parameter in msrp-config.

ORACLE(msrp-config)# msrp-kpi
<enabled/disabled> To enable the MSRP KPI statistics
Default: disabled

When you enable these extended statistics, the SBC provides additional MSRP statistics commands.

show mbcd msrp
show mbcd msrp realm <identifier>
show mbcd msrp SEND
show mbcd msrp REPORT
show mbcd msrp REPORT failure
show mbcd msrp SEND responses
show mbcd msrp realm <identifier> SEND
show mbcd msrp realm <identifier> REPORT
show mbcd msrp realm <identifier> REPORT failure
show mbcd msrp realm <identifier> SEND responses

See the MSRP Protocol Performance section in the Oracle® Communications Session Border Controller Maintenance and Troubleshooting Guide for detail on these commands.

See the Oracle® Communications Session Border Controller MIB Guide for detail on these tables.