SCM Changes in Release 14.0

This chapter identifies features and functionality added to, modified for, or deprecated from 14.0 SCM software releases.

Topics covered in this chapter are:

IMPORTANT:

Enhancements to Diameter, GTPP, and RADIUS in release 14.0 are located in the Accounting Management Changes chapter.

Enhancements to SNMP MIB in release 14.0 are located in the SNMP MIB Changes chapter.

Enhancements to Web Element Manager (WEM) in release 14.0 are located in the Web Element Manager Changes chapter.

SCM Feature Changes as of September 28, 2012

This section provides information on SCM feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the Session Control Manager Administration Guide for this release.

New SCM Features

This section identifies new SCM features available in release 14.0.

S-CSCF Will Forward the Contact and Accept Contact Headers in OPTIONS and 200 OK OPTIONS Response

As per RFC 3841, Accept-Contact header can only come in request. Custom change allows Accept-Contact header in response.

SUBSCRIBE Method Should Forward to the AS by iFC

Changes made in S-CSCF to retain the incoming contact in B2BUA mode.

Support for NPDB Using TCP-Proxy

Each session manager running on different PSCs were establishing their own NPDB connections. This put strain on the NPDB server with too many connection requests from the same client. To reduce the overhead at peer and to hide the internal details of system, new proclet called “cscfcpmgr” (cscf connection proxy manager) has been added.

VoLTE Registration Subscription Report

Added CSCF handling of Unsupported-VoLTE AVP in SAA from HSS.

Modified SCM Features

This section identifies SCM features modified in release 14.0.

AoR Registration Behavior Change

Multiple AoR registering with the same Contact is restricted.

Previous Behavior: If another AoR tried to register with the Contact used by an already registered AoR, registration was successful; however, it had a few other issues.

New Behavior: If another AoR tries to register with the Contact used by an already registered AoR, P-CSCF will reject the registration.

Call Waiting Behavior Change

Customer requirement to enable/disable policy authorization for calls with inactive media. The media will be considered inactive when all m lines in SDP are in inactive state.

This behavior can be enabled or disabled using the new authorization inactive-media CLI command in CSCF PCRF-Policy-Control Configuration Mode.

Previous Behavior: AAR is sent for all types of media, whether it is active or inactive. And for call waiting indication from AS, AF-Application ID was sent with the default value (300) in AAR.

New Behavior: Administrator can provision whether to send AAR for inactive media or not. For call waiting indication from AS, AF-Application id is sent with the value of 316 in AAR.

CDF Interworking Behavior Change

Added “User-Agent” header value into the criteria for selecting CDF. The CSCF Diameter Selection Configuration Mode is enhanced to accept User-Agent header value in the form of a regular expression.

Previous Behavior: The CSCF chose default AAA Group for accounting when CDF selection was disabled.

The CDF selection for unregistered subscribers was performed using criteria from INVITE message.

New Behavior: The CSCF now chooses HSS-provided CDF addresses when CDF selection is disabled.

The CDF selection for unregistered subscribers will not be performed. The CSCF chooses HSS-provided CDF addresses.

CDF Selection Behavior Change

CDF selection enhanced based on type of VoIP call.

VT Call: Existing CDF selection behavior should apply for VT call only.
  • For a call containing VT tag in Accept-Contact, CDF from the AAA group selected during registration should be used.
  • For unregistered subscribers, the existing behavior applies.
  • If no AAA Group was selected during registration, then the existing behavior applies.
Non-VT Call: VT tag is not present or Accept-Contact is not present.
  • CDF given in default AAA Group should be used.
  • This applies for unregistered subscribers also.

Added a CLI command to enable the custom cdf-selection solution under CSCF Service Configuration Mode.

Previous Behavior: Prefix-based CDF selection logic is applied for all calls.

New Behavior: When custom cdf-selection CLI command is enabled, prefix-based CDF selection logic is applied for VT calls only. For non-VT calls, CDF in default AAA Group is used.When custom cdf-selection is disabled, prefix-based CDF selection logic is applied for all calls.

Contact Header Behavior Change

S-CSCF needs to forward Contact header without modification for RCS.

Previous Behavior: S-CSCF changed the contact to its IP address and port when acting in B2BUA mode.

New Behavior: S-CSCF will not modify the contact header while acting in B2BUA mode. It will retain the incoming UE’s contact and add record-route header for the indialog requests that come to the S-CSCF.

Customer-chat Behavior Change

Customer-chat in Accept-Contact should be considered the same as IM.

Previous Behavior: lgt-chat and IM were two different feature tags and displayed as two different feature tags in show CLI.

Example: 

[local]asr5000# show
subscribers cscf-only full
AoR: user1@192.168.91.150:5060
callid: 00004e21
  Contact:
  <sip:user1@192.168.90.151:5074>;expires=1989;description=“IM”;lgt-chat;user=phone
  Custom Features: IM
CHAT

In this example, both feature tags were displayed in show CLI.

New Behavior: lgt-chat is now treated as IM and displayed as IM in show CLI.

lgt-chat is now treated as IM and displayed as IM in show CLI.

Example: 

CAE Server Address:
AoR: user1@192.168.91.150:5060
callid: 00004e23
  Contact:
  <sip:user1@192.168.90.151:5074>;expires=1992;description=“MSG,AT”;lgt-chat;user=phone
  Custom Features: AT
MSG IM

In this example, lgt-chat is displayed as IM in show CLI.

Custom Header Added to INV Toward MGCF

A custom header is added by S-CSCF in the INVITE message when forwarding it to MGCF.

Forking Behavior Change

Added forking support for non-invite requests.

Previous Behavior: Forking was not supported for non-invite requests.

New Behavior: Forking is supported for the following methods:
  • MESSAGE
  • PUBLISH
  • OPTIONS

From/PAI Header Behavior Change

From/PAI Header Display Name parameter size should be 128 bytes. The display name was being truncated to 32 characters because of the limitation in stacksize of UMM structure for a From/PAI header.

Previous Behavior: If a From/PAI header display name is greater than 32 characters, then CSCF truncated the display name to 32 characters and forwarded the message.

New Behavior: CSCF will now support a From/PAI header with a display name of any length. CSCF will forward the display name in From/PAI header as it is without truncation.

iFC Behavior Change

Change in CSCF behavior after iFCs are deleted.

Previous Behavior: In the earlier releases, when operator deleted the IFC-IDs in the CLI, we were not deleting SIFC-IDs in the sessmgr if they were referenced by any subscriber. This behavior was leading to inconsistencies when updating/modifying iFCs through CLI.

New Behavior: Now, if the conditions or groups are removed in the shared iFC, the changes will be affected for the new call or Re-Registrations immediately. The system does not keep the AS information if configuration is removed both for Registration and INVITE cases.

Delete SIFC-IDs is taken into effect immediately and any new session/re-registration should not refer to the deleted IFCs anymore. In addition, registration/re-registration can restore the iFCs for the subscriber through HSS.

MGCF Interworking Behavior Change

MGCF interworking should do route look up based on LIA Server Name.

Previous Behavior: S-CSCF was forwarding the INVITE message based on server-name AVP received in LIA without doing route look up based on server-name AVP.

New Behavior: Now, S-CSCF does route look up based on server name. If route look up fails, then it forwards directly based on server name address.

The following route entries from the CSCF Routes Configuration Mode are used for route look up:
  • route nexthop-address ip_address
  • route peer-servers server_name
  • route peer-servers-group group_name
  • route route-list group_name

Monitor Protocol Behavior Change

Added monitor protocol support for NPDB feature.

Previous Behavior: Absence of monitor protocol support for NPDB.

New Behavior: NPDB option has been added to the list of global protocols supported by monitor protocol CLI command. Upon selection of this option, monitor protocol output for NPDB messages can be viewed at various verbosity levels.

MSRP Setup Behavior Change

Previous Behavior: When user is behind NAT, MSRP setup attribute can be active or actpass.

New Behavior: When user is behind NAT, MSRP setup attribute must be active.

If the user behind nat sends the session description (SDP) with MSRP setup attribute other than active, then:

  1. If it is request, it will be rejected with 500 server internal error.
  2. If it is response, then call will be continued and when ACK is received, the terminating P-CSCF will send BYE to both sides.

Multiple Registration Behavior Change

Need to use PRID/PUID/DeviceType/PANI for the multi-bind.

Added IMS support for UE to perform Multiple Registration from same device but from different access types. Access Type is obtained from the PANI header of the SIP REGISTER message.The new multi bind private ID formats are:

  • accesstype:devicetype:privateID when all parameters are present
  • accesstype::privateID when accesstype is present and devicetype is not present
  • :devicetype:privateID when accesstype is not present and devicetype is present
  • privateID when both accesstype and devicetype are not present
  • accesstype = ASCII (enum value of UMM_TYPE_PAccessNetworkType) when valid
  • accesstype = accesstype text from PANI when accesstype is UMM_ACCESSTYPE_OTHER.

Previous Behavior: The binding of “contact” was based on the combination of the device type and the Private user ID. The same user could register with different devices and the registrations resulted in separate bindings. When a user performed multiple registrations from the same device but from different access types, the latest registration replaced the “contact” binding of the previous registration. Only one binding of “contact” was maintained for this user.

New Behavior: The binding of the contact is based on the combination of Access type, device type and Private user ID. Now, the same user can register with not only different devices, but also with same device provided that the access type is different. These registrations result in separate “contact” bindings.

Multiple Binding Behavior Change

Previous Behavior:
  1. SAR is sent for all deregistrations.
  2. Two Bindings were created at CSCF for two contacts using same Private ID and Device Type, but different access types --3gpp2_1x_hrpd or 3gpp_e_utran_fdd.
New Behavior:
  1. When Multiple Registration Feature and custom volte CLI command are enabled, deregistration SAR is sent only for the last contact bound to that Private ID. Deregistration SAR is not sent if the corresponding Private ID has other contact bindings.
  2. Single Binding is created at CSCF when two contacts register using same Private ID and Device Type, but different access types--3gpp2_1x_hrpd or 3gpp_e_utran_fdd. The contact information from the latest registration is stored in CSCF.

NPDB RN Length Change Behavior Change

Previous Behavior: If the RN length was <=5, then RN was copied and the remaining characters up to 6th element were replaced with “f”. (Example: If the RN was 1234, then the “1234ff” was copied to the recipient code.)

If the RN length was >5, then the first 5 digits were copied to the Recipient Code and the 6th character was replaced with “f”. (Example: If the RN wa 70123400000 then, the “70123f” was copied to the recipient code.)

The default value of recipient code was “ffffff”.

New Behavior: The Recipient code which is extracted from the routing number in NPDB response should contain 7 characters (including f).

If the RN starts with “0”, then the 6 digits after “0” will be copied to the Recipient Code (Example: If the RN is 01021320000, then the “102132f” is copied to the recipient code.)

If the RN does not start with “0” then the first 6 digits are copied to the Recipient Code (Example: If the RN is 70123400000, then “701234f” is copied to the recipient code.). The 7th character is replaced with “f”.

If the RN length is <=6 and the RN does not start with “0”, then the RN is copied and the remaining characters up to the 7th element will be replaced with “f”. (Example: If the RN is 12345, then the “12345ff” is copied to the recipient code.)

If the RN length is <=6 and RN starts with “0”, then the RN is copied discarding zero and the remaining characters up to the 7th element will be replaced with “f”. (Example: If the RN is 01234, then the “1234fff” is copied to the recipient code.)

The default behavior is if the routing number sent by NPDB server is not valid, then the default recipient code “fffffff” will be filled.

NPDB Support Added for UNKNOWN Messages

NPDB interworking was only supported for INVITE; another method was needed.

NPDB interworking support added for UNKNOWN messages.

Number of Prefix Entries Increased

Increased the number of prefix entries of PCRF from 128 to 256.

Parameter Token Value Behavior Change

As specification allows adding integrity-protected parameter as quoted string as well as token, P-CSCF was adding the integrity-protected parameter as quoted string. Per customer requirement, quotes should not be added for this parameter.P-CSCF will not add quotes for this parameter when custom volte CLI command is enabled. Format changed for integrity-protected parameter value inserted during registration by P-CSCF in authorization header.

Previous Behavior: When P-CSCF inserted integrity-protected parameter in authorization header during registration, it used to include value with quotes.

Example: integrity-protected=“yes”

New Behavior: P-CSCF will include integrity-protected parameter value without quotes when custom volte CLI command is enabled.

PCRF Selection Behavior Change

For Rx policy sessions, P-CSCF is required to select PCRF server based on IMSI prefix.

Previous Behavior: The following commands are available in the CSCF Proxy-CSCF Configuration Mode for the existing PCRF selection feature. This selection is limited to configuring primary and secondary peers only.

diameter policy-control
origin endpoint endpoint_name

diameter policy-control
peer-select peer peer_name [ peer-realm realm_name ]  [ secondary-peer peer_name [ sec-peer-realm realm_name ] ] 

no
diameter policy-control { origin endpoint | peer-select }

When primary/secondary PCRF peers are configured, the P-CSCF used these for Rx Interface.

When primary/secondary PCRF peers were not configured, P-CSCF did a round robin among peers in the diameter endpoint associated with P-CSCF service.

New Behavior: New CLI associates the P-CSCF service with a “diameter host-select-template”. The host-select-template has a table of prefix and PCRF peers. When “diameter policy-control host-select-template” is configured, PCRF server is selected using a lookup based on subscriber IMSI prefix from this table. 

diameter policy-control
host-select-template name template_name

no
diameter policy-control host-select-template

When this new keyword is not configured or there is no matching entry for the given subscriber number, existing behavior will apply as follows:

  • The P-CSCF uses the peers configured as primary/secondary peers from diameter policy-control peer-select CLI.When diameter policy-control host-select-template is not configured, or, When there is no matching entry for the given subscriber number in the host-select-template table.
  • The P-CSCF selects one of the peer entries (round-robin method) in the Diameter endpoint associated with the P-CSCF service:When both host-select-template and primary/secondary peers are not configured, or, When there is no matching entry for the given subscriber number in the host-select-template table and primary/secondary peers are not configured.

Rx Behavior Change

Change in AVP value and number in AAR request over Rx interface.

Previous Behavior: In AAR request, Subscription-ID AVP carries UE contact.

New Behavior: In AAR request, Subscription-ID AVP carries UE's IMS public user identity and IMS private user Identity.

S-CSCF Cx Communication Behavior Change

S-CSCF Cx communication is being enhanced.

Previous Behavior:
  1. If the S-CSCF receives user data greater than 24k, then it accepted the register and no further Cx interaction took place.
  2. If S-CSCF receives no user data, register was rejected with a 403 and no further Cx interaction took place.
New Behavior:
  1. If the S-CSCF receives user data greater than 24k, then the S-CSCF rejects the register with a 481 temporarily available, initiates an SAR with server assignment type as DEREGISTRATION_TOO_MUCH_DATA, and removes any earlier registration of the corresponding user.
  2. If the S-CSCF receives dubious user data (empty or unparseable), then the S-CSCF rejects the registration with 403, initiates an SAR with server assignment type as ADMIN_DEREG, and removes any earlier registration of the corresponding user.

S-CSCF Expects the TLDN from HSS in the Form of Hex String.

As per the requirement, the TLDN string obtained from the HSS should be in the form of a Hexadecimal string.

Previous Behavior: The TLDN string obtained from the HSS was assumed to be the actual TLDN number.

New Behavior: The TLDN string obtained from the HSS is assumed to be the hexadecimal equivalent of the TLDN.

Server Header Behavior Change

CLI added to handle the server header, including forwarding, modifying, adding, or suppressing.

Previous Behavior: When response from AS was received, “Starent” added to server header.

New Behavior: The handling of server header can be configured by new server-header command in CSCF Service Configuration Mode.

ServerName + TLDN Routing Behavior Change

CSCF routing functionality has been enhanced do route lookup based on server name and TLDN when both are received in LIA.

Previous Behavior: S-CSCF was doing TLDN-based routing, even through it receives server name in LIA. If there was no matching criteria for TLDN, then request was routed based on request URI. Basically, S-CSCF was ignoring server name if TLDN received in LIA.

New Behavior: Now, S-CSCF first looks at matching criteria for both server name and TLDN; if it does not find both, then it looks for any matching criteria for server name or TLDN. Finally, if there is no matching criteria for server name or TLDN, then it forwards to server name address.

Smart Edu Service Support

Added code to support subscriber-capability smart-edu.

Subscriber Info Behavior Change

P-CSCF will remove the old contact for a Public+Private user ID pair upon receiving a new contact in 200 OK for register.

Previous Behavior: P-CSCF was not removing the old binding and it relies on subscription package (notify from S-CSCF) to delete it.

New Behavior: P-CSCF removes the old contact for a Public+Private user ID pair upon receiving a new contact in 200 OK for register. Enabling subscription package for custom-reg-binding is not mandatory.

Support for AF-App-ids Over Rx for Different Feature Tags

Added different values for AF-APP-ids (over Rx) for different feature tags.

Trust-domain Entities Behavior Change

50 trust-domain entities are not enough. SCT is now used for configuration instead of array of char buffers.

Previous Behavior: A maximum of 50 entries could be configured for trusted-domain-entity in a service. The last entry was overwritten if more than 50 entries were configured and no error was displayed.

New Behavior: A maximum of 256 entries can now be configured. An error will be displayed if there is an attempt to configure more than 256.

Delete one entry and configure if the maximum entries are already configured.

Video - Audio Call Conversion Behavior Change

Previous Behavior: Rx: AAR: While removing media streams from a session, Flow-Description AVP added “any” for the port field when it was unavailable.

New Behavior: Rx: AAR: While removing media streams from a session, Flow-Description AVP adds “0” for the port field when it is unavailable.

The value of the port field is modified only for the case where media streams are being removed; other scenarios are not impacted.

SCM Configuration Management Changes as of September 28, 2012

This section provides information on SCM configuration command changes in release 14.0.

IMPORTANT:

For more information regarding commands in this section, refer to the Command Line Interface Reference for this release.

New SCM Configuration Commands

This section identifies new SCM commands available in release 14.0.

authorization inactive-media

Enables policy authorization for calls with inactive media.

CSCF PCRF-Policy-Control Configuration Mode 

[ default | no ] authorization
inactive-media

custom cdf-selection

Enables using the CDF selected during registration for “VT” calls. For other calls, the CDF in default AAA-Group is used. Default is disabled.

When disabled, the CDF selected during registration shall be used for all calls.

CSCF Service Configuration Mode 

no custom cdf-selection

server-header

This command determines the handling of the Server header. This is applicable for B2BUA mode only; Proxy mode will forward the message as it is.

CSCF Service Configuration Mode 

server-header { name header_name | pass-through }

[ default | no ] server-header

Modified SCM Configuration Commands

This section identifies SCM commands modified in release 14.0.

aaa-group

Configures diameter selection entries.

Filters can now be based on the following new subscriber capability types:

  • lte-voip
  • lte-vt
  • smart-edu

CSCF Diameter Selection Configuration Mode 

aaa-group name { [ preference value ] criteria { aor aor_prefix | subscriber-capability capability_type | subscriber-ip-type { v4 | v6 } } +

no aaa-group name preference value

access-type

Access type 3gpp2-cdma-cs option has been added to the list of access types.

CSCF Service Configuration Mode 

access-type { type } access-profile { default | name access_profile_name } | ue-ip-address-range
name ue_ip_name  { address ip_address_mask | range start_ip_address
end_ip_address }

no access-type { type } [ access-profile | ue-ip-address-range
 [ name ue_ip_name ] ]

cscf peer-servers-group

Creates a peer servers group and enters the Peer Servers Group Configuration Mode.

The following new types of peer servers group are now supported:

  • bgcf
  • ecscf
  • ibcf
  • icscf
  • mgcf
  • mrfc
  • other
  • pcscf
  • scscf

Context Configuration Mode 

cscf peer-servers-group group_name  type { bgcf | ecscf | ibcf | icscf | mgcf | mrfc | other | pcscf | scscf | sip-as } [ -noconfirm ]

no cscf peer-servers-group group_name

custom response

Configures reject with specific response code for UE capability failure or UE status.

The following new UE capability failure types are now supported:

  • lte-voip
  • lte-vt
  • smart-edu

CSCF Service Configuration Mode 

custom response { ue-capability-failure capability_type | ue-status status } reject response-code response_code

no custom response { ue-capability-failure capability_type | ue-status status }

deny

Configures the system to deny subscriber sessions based on criteria matching the received packet.

Sessions can now be filtered based on the following new subscriber capability types:

  • lte-voip
  • lte-vt
  • smart-edu

CSCF ACL Configuration Mode 

[ no ] deny
subscriber-capability smart-edu

diameter

This command associates the P-CSCF service with a “diameter host-select-template”. The host-select-template has a table of prefix and PCRF peers. When configured, PCRF server is selected using a lookup based on subscriber IMSI prefix from this table.

CSCF Proxy-CSCF Configuration Mode 

diameter policy-control
host-select-template name template_name

no
diameter policy-control host-select-template

host-select row-precedence

This command configures individual rows of peer servers within the Diameter host table.

In StarOS release 14.0 and later, precedence may be an integer from 1 through 256 for SCM.

Diameter Host Select Configuration Mode 

host-select row-precedence precedence table { 1 | 2 | prefix-table { 1 | 2 } } host host_name [ realm realm_id ] [ secondary
host host_name realm realm_id ] ] [-noconfirm] 

host-select row-precedence precedence table prefix-table { 1 | 2 } msisdn-prefix-from msisdn_prefix_from msisdn-prefix-to msisdn_prefix_to host host_name [ realm realm_id ] [ secondary
host host_name realm realm_id ] [-noconfirm]

no host-select row-precedence precedence table { 1 | 2 | prefix-table { 1 | 2 } } [-noconfirm]

permit

Configures the system to permit subscriber sessions based on criteria matching the received packet.

Sessions can now be filtered based on the following new subscriber capability types:

  • lte-voip
  • lte-vt
  • smart-edu

CSCF ACL Configuration Mode 

[ no ] permit
subscriber-capability smart-edu

redirect

Configures the system to redirect subscriber sessions based on criteria matching the received packet.

Sessions can now be filtered based on the following new subscriber capability types:

  • lte-voip
  • lte-vt
  • smart-edu

CSCF ACL Configuration Mode 

[ no ] redirect
subscriber-capability smart-edu

route

Configure the routing parameters for the context.

Sessions can now be filtered based on the following new subscriber capability types:

  • lte-voip
  • lte-vt
  • smart-edu

In addition, access type 3gpp2-cdma-cs option has been added to the list of access type filter criteria.

CSCF Routes Configuration Mode 

route { domain name | local { icscf | pcscf | scscf } | nexthop-address address | peer-servers server_name | peer-servers-group group_name | route-list group_name | vpn name } [ [ mod-req-uri ] base-criteria criteria [ filter-criteria1 criteria ] [ filter-criteria2 criteria ] ] [ log ]

no route { domain name | local { icscf | pcscf | scscf } | nexthop-address address | peer-servers server_name | peer-servers-group group_name | route-list group_name | vpn name } base-criteria criteria [ filter-criteria1 criteria ]  [ filter-criteria2 criteria ]

server-name

Enables/disables filling the server name AVP in MAR and SAR for Cx interface, and the From header in third party register request, with configured server name. In addition, it can be used by other CSCF service to fill From header while performing peer server monitoring using OPTIONS request.

CSCF Service Configuration Mode

(previously CSCF Serving-CSCF Configuration Mode) 

server-name server_name

no server-name

Deprecated SCM Configuration Commands

This section identifies deprecated SCM commands that are no longer supported in release 14.0.

None for this release.

SCM Performance Management Changes as of September 28, 2012

This section provides information on SCM performance management changes in release 14.0.

IMPORTANT:

For more information regarding bulk statistics in this section, refer to the Statistics and Counters Reference for this release.

For more information regarding commands in this section, refer to the Command Line Interface Reference for this release.

New SCM Bulk Statistics

This section identifies new SCM bulk statistics available in release 14.0.

None for this release.

Modified SCM Bulk Statistics

This section identifies SCM bulk statistics modified in release 14.0.

None for this release.

Deprecated SCM Bulk Statistics

This section identifies deprecated SCM bulk statistics that are no longer supported in release 14.0.

None for this release.

New SCM Performance Commands

This section identifies new SCM performance commands available in release 14.0.

show cscf peer-servers-group

Displays the status of peer-servers-lists inside peer-servers groups.

Exec Mode 

show cscf peer-servers-group { all | full | name group_name [ servers-list-name list_name ] } [ | { grep grep_options | more } ]

Modified SCM Performance Commands

This section identifies SCM performance commands modified in release 14.0.

monitor protocol

Enters the system‘s protocol monitoring utility.

Exec Mode

Added monitor protocol support for NPDB feature:
  • 91 - NPDB(IMS) (Admin only)

show cscf service

The new npdb keyword displays NPDB message statistics for a CSCF service.

Exec Mode 

show cscf service statistics
name service_name npdb [ all | instance id ] [ | { grep grep_options | more } ]
The following fields have been added to the output of this command:
  • CSCF NPDB Statistics
  • Summary/Instance-ID:
  • Total TCP Connections Attempted TCP Connections Successful TCP Connections Failed TCP Connections Closed NPDB Connections Attempted NPDB Connections Successful NPDB Connections Failed NPDB Transactions Active BIND Messages Sent BIND Retry Messages Sent BIND_ACK Messages Received PING_PONG Messages Sent PING_PONG Retry Messages Sent PING_PONG_ACK Messages Received QUERY Messages Sent QUERY Retry Messages Sent QUERY_ACK Messages Received REL_REQ Messages Sent REL_RES Messages Received ERRREP Messages Sent ERRREP_ACK Messages Received ERRREP Messages Received ERRREP_ACK Messages Sent

show subscribers cscf-only full all

Displays information for subscribers accessing the specified CSCF service.

Exec Mode

The following field has been added to the output of this command:
  • Unsupported VoLTE

Deprecated SCM Performance Commands

This section identifies deprecated SCM performance commands that are no longer supported in release 14.0.

None for this release.

SCM Security Management Changes as of September 28, 2012

This section provides information on SCM security management changes in release 14.0.

None for this release.