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:
-
SCM Feature Changes
as of May 31, 2013
-
SCM Command Changes
as of May 31, 2013
-
SCM Performance Indicator
Changes as of May 31, 2013
-
SCM Feature Changes
as of February 20, 2013
-
SCM Configuration Management
Changes as of February 20, 2013
-
SCM Performance Management
Changes as of February 20, 2013
-
SCM Security Management
Changes as of February 20, 2013
-
SCM Feature Changes
as of January 31, 2013
-
SCM Configuration Management
Changes as of January 31, 2013
-
SCM Performance Management
Changes as of January 31, 2013
-
SCM Security Management
Changes as of January 31, 2013
-
SCM Feature Changes as
of September 28, 2012
-
SCM Configuration Management
Changes as of September 28, 2012
-
SCM Performance Management
Changes as of September 28, 2012
-
SCM Security Management
Changes as of September 28, 2012
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 May 31, 2013
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.
ATCF/ATGW
Support
IMPORTANT:
This feature has been implemented as lab
quality.
Complete ATCF/ATGW
functionality supported at lab quality. This feature was first in Build
14.0.47681.
ATCF (Access Transfer
Control Function)/ATGW (Access Transfer Gateway) shall
provide proxy role and UA role, as per TS 24.237.
All associated CLI
commands and performance statistics are also now supported at lab quality.
CLI Support for
ATCF Mgmt URI from ATCF
IMPORTANT:
This feature has been implemented as lab
quality.
CLI command mgmt-uri in CSCF ATCF/ATGW Configuration
Mode now supported at lab quality. This feature was first introduced
in Build 14.0.47681.
CLI Support to display
Equipment-id Information
This CLI will now provide
an option to display the equipment-id present in the E-CSCF service
during EATF calls.
CLI command show cscf service has
been modified in Exec
Mode to support this enhancement.
EATF Support
EATF (Emergency Call
Access Transfer) functionality supported at deploy quality. This feature
was first introduced at lab quality in Build 14.0.47681.
All associated CLI
commands and performance statistics are also now supported at deploy quality.
Support for ATCF/ATGW
with P-GW Collapsed on ASR 5000
IMPORTANT:
This feature has been implemented as lab
quality.
This feature has been
implemented at lab quality. This feature was first introduced in
Build 14.0.47681.
Support for ATCF/ATGW
(v6-v4 Interworking) with P-GW Collapsed on ASR 5000
IMPORTANT:
This feature has been implemented as lab
quality.
This feature has been
implemented at lab quality. This feature was first introduced in
Build 14.0.47681.
Support for v6-v4
Interworking for ATCF/ATGW
IMPORTANT:
This feature has been implemented as lab
quality.
Support for v6-v4 interworking
in ATCF/ATGW implemented at lab quality. This feature was
first introduced in Build 14.0.47681.
Modified SCM Features
This section
identifies SCM features modified in release 14.0.
AAR to Redirected
PCRF has Wrong Dest Realm and Host
AAR to redirected PCRF
now has the correct destination host and realm values
Alarm generated
when NPDB Connection is down
Added support to generate
SNMP alerts when NPDB connection goes down and comes up.
Previous Behavior:
There was no alarm generated when the connection went down.
New Behavior: A
new alarm is generated to indicate a NPDB connection has gone down.
This alarm will be cleared when the connection is up again.
There are two types
of NPDB configuration:
- Without using connection
proxy
- With connection proxy
(used by a specific customer)
When connection proxy
is used, there can be one connection proxy manager for the entire chassis
or a configuration can be made so each card runs on its own connection
proxy manager.
Connection proxy manager
is responsible for creating NPDB connections to the NPDB server.
Currently, there can be two NPDB servers configured (one primary
and one secondary) in NPDB client configuration.
Added two SNMP traps.
They are NPDBConnectionUp and NPDBConnectionDown.
NPDBConnectionDown
is generated when a NPDB connection goes down (regardless of whether
the server is primary or secondary). NPDBConnectionUp is generated
when connection to NPDB server is successful again.
Connection Proxy establishes
a connection with the NPDB server based on the NPDB client configuration
parameters. When the NPDB connection is successful (connection moved
to CSCFCPS_NPDB_STATE_NPDB_CONNECTED),
then NPDBConnectionUp alarm is generated.
When NPDB server does
not respond to the QUERY, then PINGPONG requests even after retries
is configured. If the NPDB server resets/closes the socket
connection, then the NPDBConnectionDown SNMP alert message is sent.
This is cleared by subsequent successful connection (NPDBConnectionUp).
This feature has been
implemented.
A-BG License on
CLIs
Previous Behavior:
By default, the A-BG CLIs were enabled.
New Behavior: A-BG
CLIs will be enabled only if the A-BG license is supported in cfg
file.
Contact your Cisco
account representative for information on how to obtain a license.
ASR of Signaling
Bearer received in P-CSCF
Previous Behavior:
When PCRF sends ASR for signaling bearer, De-register was not sent
from P-CSCF to S-CSCF.
New Behavior: When
PCRF sends ASR for signaling bearer, De-register is sent from P-CSCF
to S-CSCF.
CLI command signalling-bearer-loss added
in CSCF Policy Rules
Configuration Mode to support this enhancement.
Calling Party Information
Priority
For a specific customer,
there was a possibility that P-Asserted-Id may be replaced by AS for
some service purposes. To avoid this replaced P-Asserted-Id from
being used in AAR or ACR, the P-Served-User must be used for calling
party information.
The priority for calling
party information is:
- P-Served-User
- P-Asserted-Id
- From
Previous Behavior:
Calling party information was obtained from “P-Asserted-Id”,
if present; otherwise it was obtained from “From” header
of the INVITE request.
New Behavior: For
ACR and AAR, calling party information is obtained from “P-Served-User” whenever
present and when sesscase is orig. When not present, it is obtained from “P-Asserted-Id”;
otherwise, it is obtained from “From” header.
Called-Party-Address will never be updated with “P-Served-User”.
IMPORTANT:
This behavior is only
applicable when the custom
volte CLI command is enabled.
Changes to E-CSCF
Call Routing and Failover
Customer requirements
changed regarding E-CSCF call routing and failover design.
Previous Behavior:
No standardization on R-URI, To, From, PAI headers.
No secondary MGCF address
used to route the emergency calls from PSAP Database.
New Behavior: Standardization
on R-URI, To, From, PAI headers.
Secondary MGCF address
used to route the emergency calls from PSAP Database.
E-CSCF shall respond
to SIP Option from P-CSCF
Previous Behavior:
E-CSCF rejected OPTIONS message with 405 Method Not Allowed message.
New Behavior: E-CSCF
now responds to OPTIONS message with 200OK instead of 405 to avoid
long timeout.
Error Reason Header
Enhancement
Previous Behavior:
No Reason header was sent.
New Behavior: For
any error response sent from sessmgr or cscfmgr, SIP reason header
is added per customer requirement.
CLI command custom reason-header-cause-code added
in CSCF Service Configuration
Mode to support this enhancement.
Lawful Intercept
(LI): Messages Not Captured During an Emergency When User is Unregistered
Previous Behavior:
All Emergency calls are not tapped.
New Behavior: All
emergency call messages are tapped.
For additional information
and documentation on the Lawful Intercept feature, contact your Cisco
account representative.
Lawful Intercept
(LI) supported for ATCF/ATGW Function
IMPORTANT:
This feature has been implemented as lab
quality.
Previous Behavior:
No messages were tapped, even if Lawful Intercept enabled, for user
involved in access transfer.
New Behavior: Messages
will be tapped towards SCC-AS.
For additional information
and documentation on the Lawful Intercept feature, contact your Cisco
account representative.
Lawful Intercept
(LI) support for A-BG (v6-v4) with v6 Subscriber
IMPORTANT:
This feature has been implemented as lab
quality.
Previous Behavior:
IPv4 Lawful Intercept content delivery only.
New Behavior: Support
for IPv6 Lawful Intercept content delivery is added.
For additional information
and documentation on the Lawful Intercept feature, contact your Cisco
account representative.
Prefix Based MGCF
Selection
Added a feature to
do route processing, based on ServerName and Legacy-Routing-Info AVP
in LIA.
A specific customer
is deploying the MGCF to the each MSC. Therefore, MSC ID (PCSSN) will
be used for the MGCF selection. In this scenario, when LIA includes
the MGCF server name, then it will also include a new AVP, Legacy-Routing-Info,
for the MGCF selection.
If MGCF server-name
is present in LIA along with Legacy-Routing-Info AVP, then the current
routing logic needed to be enhanced to do a route lookup based on
the server-name and the legacy-routing-info.
Previous Behavior:
- Legacy-Routing-Info
AVP, if present in LIA, was ignored.
- When both TLDN and
Legacy-Routing-Info AVP were present, then the message was processed
based on the TLDN AVP value.
New Behavior:
- When Legacy-Routing-Info
AVP is present, the value of this AVP will be used along with ServerName
to do route lookup.
- When both TLDN and
Legacy-Routing-Info AVP are present, then the value of TLDN AVP will
be ignored.
Prefix Based Term
S-CSCF Routing When the HSS Interworking Failed
There was a customer
request to add special routing logic to handle failure during HSS interaction
for LIR-LIA.
New CLI command routes
the register messages based on the route table if LIR-LIA fails during
HSS interaction.
Previous Behavior:
LIR-LIA was always done for a call regardless of the of subscriber
capability.
New Behavior: When
lir-failure route-list is configured/enabled, in the case
of LIR failure, route the message based on the route table. Also,
while doing a lookup of this route table, destination user from
req-uri will be placed in source-aor criteria field. The message
is routed to the first matching entry in the route-list table.
When lir-failure route-list
is not configured (disabled), then it is handled the same as the previous
behavior.
CLI command lir-failure added
in CSCF Serving-CSCF
Configuration Mode to support this enhancement.
SAA 5001 Should
Trigger 404 SIP Response
When the response code
was set to 404 USER NOT KNOWN for SAA 5001, SAA processing was overwritten
by 500 Server Internal Error at S-CSCF.
Added functionality
to use the response code set while processing SAA 5001 at S-CSCF,
if present.
Previous Behavior:
500 Server Internal Error was triggered on SAA 5001 on disabling
authentication. The response code 404 User Not Found set while processing
SAA 5001 and was not considered at S-CSCF. This response code was
set to 500 Internal Server Error later at S-CSCF.
New Behavior: For
SAA 5001, 404 User Not Found will be triggered on disabling authentication.
The response code 404 User Not Found set while processing SAA 5001 will
be used at S-CSCF.
Session Recovery
Supported for ATCF/ATGW
IMPORTANT:
This
feature has been implemented as lab quality.
Previous Behavior: Redundancy
was not working for ATCF/ATGW.
New Behavior: Redundancy
is now working for ATCF/ATGW.
Support for Bandwidth
Configuration per Media Type
Previous Behavior:
Configuration of uplink and downlink bandwidth peak values was common
for all media types.
New Behavior: Configuration
of bandwidth uplink and downlink peak value per media type (audio,
video, and other) now available.
CLI command qos bandwidth has
been modified in CSCF
Policy Rules Configuration Mode to support this enhancement.
SCM Command Changes
as of May 31, 2013
This section
provides information on SCM 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 Commands
This section
identifies new SCM commands available in release 14.0.
lir-failure
This command allows
you to define routes towards the target server for LIR failure case.
configure
context context_name
cscf
service service_name
serving-cscf
lir-failure
route-list route_list_name
no
lir-failure route-list
end
signalling-bearer-loss
This command enables
or disables signalling bearer loss.
configure
context context_name
cscf
policy name policy_name
service-policy-rules
[ no ] signalling-bearer-loss
de-register
end
Modified SCM Commands
This section
identifies SCM commands modified in release 14.0.
clear cscf service
The following command
clears all statistics related to ATCF access transfers.
clear cscf service statistics
name p-cscf_name atcf
clear cscf service
The following command
clears all statistics related to emergency access transfers.
clear cscf service statistics
name e-cscf_name eatf
cscf ifc-filter-criteria
This command creates
Initial Filter Criteria (iFC) filter criteria for shared iFC functionality. New
keywords include-reg-request and include-reg-response are
added to enable inclusion of UE's REGISTER and 200OK to be included
in 3rd party registration.
configure
context context_name
cscf
ifc-filter-criteria id fc_id priority priority [ profile-part-indicator { registered | unregistered } ] app-server
uri scheme { sip | sips } as as-default-handling { session-continue | session-terminate } [ -noconfirm ] [ include-reg-request ] [ include-reg-response ] [ service-info info ] [ trigger-point tp_id ]
no
cscf ifc-filter-criteria id fc_id
end
custom reason-header-cause-code
This command configures
SIP Reason header cause value.
configure
context context_name
cscf
service service_name
custom
reason-header-cause node-type node_type node-number node_num base-cause-code cause_code
no
custom reason-header-cause node-type
end
ps-cs-alerting
This command determines
if ATCF shall support access transfer of call in alerting state
from PS-CS. The keyword allow has
been removed from this command.
configure
context context_name
atcf
policy name policy_name
[ no ] ps-cs-alerting
end
qos bandwidth
This command configures
QoS bandwidth settings for uplink and downlink specific to media
types.
configure
context context_name
cscf
policy policy_name
service-policy-rules
qos
bandwidth { media-type { audio | other | video } }
end
show cscf service
Displays configuration
and/or statistical information for Call Session Control
Function (CSCF) services on this system. New keyword has been added
for ATCF support.
show cscf service statistics p-cscf_name atcf
show cscf service
Displays configuration
and/or statistical information for Call Session Control
Function (CSCF) services on this system. New keywords have been
added for EATF support.
show cscf service statistics e-cscf_name [ eatf equip-id | eatf-statistics ]
Deprecated SCM Commands
This section
identifies deprecated SCM commands that are no longer supported
in release 14.0.
SCM Performance Indicator
Changes as of May 31, 2013
This section
provides information on SCM performance indicator changes in release 14.0.
IMPORTANT:
For more information
regarding bulk statistics and output fields and counters in this
section, refer to the Statistics
and Counters Reference for this release.
New SCM Bulk Statistics
This section
identifies new SCM bulk statistics available in release 14.0.
The following bulk
statistics are new in this release:
CSCF Schema
EATF Statistics
- eatf-fail-480
- eatf-fail-488
- eatf-fail-4XX
- eatf-fail-500
- eatf-fail-5XX
- eatf-fail-internal
ATCF/ATGW
Statistics
IMPORTANT:
These statistics have been
implemented as lab quality.
- at-att-rx
- at-att-tx
- at-succ-rx
- at-succ-tx
- at-fail-rx
- at-fail-tx
- at-fail-404-rx
- at-fail-404-tx
- at-fail-488-rx
- at-fail-488-tx
- at-fail-500-rx
- at-fail-500-tx
- at-fail-4xx-rx
- at-fail-4xx-tx
- at-fail-5xx-rx
- at-fail-5xx-tx
- at-fail-6xx-rx
- at-fail-6xx-tx
Modified SCM Bulk
Statistics
This section
identifies deprecated SCM bulk statistics that are no longer supported
in release 14.0.
Deprecated SCM Bulk
Statistics
This section
identifies SCM bulk statistics modified in release 14.0.
New SCM Output Fields
and Counters
This section
identifies new SCM show command output fields and counters available
in release 14.0.
show cscf service
statistics name <service_name> all
The following fields
have been added to this command for EATF support:
-
- Total Emergency call
Access Transfer Request
- Total Emergency call
Access Transfer Success
- Total Emergency call
Access Transfer Failure
- 480 Error responses
- 488 Error responses
- 500 Error responses
- 4xx Error responses
- 5xx Error responses
- Internal Error responses
-
- Access Transfer Attempts
- Access Transfer Success
- Access Transfer Failures
- 404 Error responses
- 500 Internal Error
- 488 Responses
- 4xx Responses
- 5xx Responses
- 6xx Responses
show snmp trap statistics
The following fields
have been added to this command when an NPDB connection goes down
and comes up:
Modified SCM Output
Fields and Counters
This section
identifies modified SCM show command output fields and counters
available in release 14.0.
Deprecated SCM Output
Fields and Counters
This section
identifies deprecated SCM show command output fields and counters
that are no longer supported in release 14.0.
SCM Feature Changes
as of February 20, 2013
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.
Modified SCM Features
This section
identifies SCM features modified in release 14.0.
Custom Header Should
be Used to Route the Call Even for Local Subscriber
When term-S-CSCF received
custom header and the user was registered, then instead of routing
the call to MGCF, term-S-CSCF forwarded the call to the destination
user. Per customer requirement, it should be routed based on custom
header.
Term-SCSCF now routes
the call to MGCF based on custom header, even though user is registered
locally and should not forward the call to destination user.
IMPORTANT:
Routing is done based
on custom header only for local translation.
Previous Behavior:
After LIR/LIA, Orig-S/ICSCF added custom header
to received request if the TLDN was present in LIA and it did servername
plus TLDN routing only if the received server name was not local.
If the received server name was local and the translation was local,
then the S-CSCF did term user processing. If the destination user
was not registered, then it did SAR/SAA and terminated
the user IFC processing. Finally, it routed the call to the MGCF
based on custom header.
New Behavior: Term-SCSCF
now routes the call to MGCF based on custom header, even though
the user is locally registered and should not forward the call to
destination user address. If there is no matching route entry based
on custom header, then a request should be rejected irrespective
of the user registration status.
This feature has been implemented.
SCM Configuration
Management Changes as of February 20, 2013
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.
allow
This command specifies
policy behavior.
ATCF/ATGW-Policy
Configuration Mode
allow ps-cs-alerting
no ps-cs-alerting
IMPORTANT:
ATCF/ATGW
support has been implemented as lab quality.
atcf
This command enables
ATCF functionality for the context and enters the ATCF/ATGW-Policy
Configuration Mode. Default is disabled.
Context Configuration
Mode
[ no ] atcf
policy name policy_name
IMPORTANT:
ATCF/ATGW
support has been implemented as lab quality.
atcf-atgw
This command enables
ATCF functionality for the P-CSCF and enters the CSCF ATCF/ATGW
Configuration Mode. Default is disabled.
CSCF Proxy-CSCF Configuration
Mode
[ no ] atcf-atgw
IMPORTANT:
ATCF/ATGW
support has been implemented as lab quality.
call-linger-timer
This command enables
and disables call linger timer after call termination request.
CSCF ATCF/ATGW
Configuration Mode
call-linger-timer seconds
[ default | no ] call-linger-timer
IMPORTANT:
ATCF/ATGW
support has been implemented as lab quality.
criteria
This command enables
criteria to invoke ATCF functionality.
ATCF/ATGW-Policy
Configuration Mode
criteria { access-type { 3gpp-e-utran-fdd | 3gpp-e-utran-tdd | 3gpp-geran | 3gpp-utran-fdd | 3gpp-utran-tdd | cellular | docsis | dsl | ethernet | wlan } | all | any | ics-capability | roaming }
default criteria access-type
no criteria { access-type { 3gpp-e-utran-fdd | 3gpp-e-utran-tdd | 3gpp-geran | 3gpp-utran-fdd | 3gpp-utran-tdd | cellular | docsis | dsl | ethernet | wlan } | ics-capability | roaming }
IMPORTANT:
ATCF/ATGW
support has been implemented as lab quality.
eatf
This command enables
emergency call access transfers (EATF) functionality for the service and
enters the EATF Configuration Mode. Default is disabled.
CSCF Emergency-CSCF
Configuration Mode
[ no ] eatf
IMPORTANT:
EATF support has been
implemented as lab quality.
e-stn-sr
CSCty42203
This command adds the
Emergency Session Transfer Number for Single Radio (E-STN-SR) to
the EATF.
CSCF EATF Configuration
Mode
e-stn-sr number
no e-stn-sr
IMPORTANT:
EATF support has been
implemented as lab quality.
mgmt-uri
This command supports
PSI-based routing mode in I-CSCF.
CSCF ATCF/ATGW
Configuration Mode
mgmt-uri uri
default mgmt-uri
IMPORTANT:
ATCF/ATGW
support has been implemented as lab quality.
plani
Sets parameters associated
with P-LANI (P-Last-Access-Network-Info) header.
This command is used
to identify location aging of subscriber is within acceptable limits.
CSCF Emergency-CSCF
Configuration Mode
plani age seconds
[ default | no ] plani age
policy
This command assigns
or removes an existing ATCF policy.
CSCF ATCF/ATGW
Configuration Mode
[ no ] policy
name name
IMPORTANT:
ATCF/ATGW
support has been implemented as lab quality.
stn-sr
This command specifies
a STN-SR for the ATCF.
CSCF ATCF/ATGW
Configuration Mode
stn-sr stn-sr
no stn-sr
IMPORTANT:
ATCF/ATGW
support has been implemented as lab quality.
trusted
This command specifies
a list of trusted SCC-AS.
CSCF ATCF/ATGW
Configuration Mode
[ no ] trusted
scc-as scc-as
IMPORTANT:
ATCF/ATGW
support has been implemented as lab quality.
Modified SCM Configuration
Commands
This section
identifies SCM commands modified in release 14.0.
Deprecated SCM Configuration
Commands
This section
identifies deprecated SCM commands that are no longer supported
in release 14.0.
SCM Performance Management
Changes as of February 20, 2013
This section
provides information on SCM performance management changes in release 14.0.
SCM Security Management
Changes as of February 20, 2013
This section
provides information on SCM security management changes in release 14.0.
SCM Feature Changes
as of January 31, 2013
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.
Modified SCM Features
This section
identifies SCM features modified in release 14.0.
Audio-Video Call
Interworking Support (Trace Purpose)
Customer requirement
for Rf ACR records to have call start and end time set so that only video
call duration is reflected in total call duration. A new CLI command
has been added to control this new behavior.
-
The VT call type check
using
custom cdf-selection CLI
command should be overwritten so that for all types of calls an attempt
is made to use the CDF (AAA Grp) selected at registration. The CDF
selection feature before introducing VT call check should be applicable.
-
The AVP RF-LGUPLUS-End-Time
should be modified to:
- audio only call: End
Time = Call Start Time
- video call with no
call conversion: End Time = Call End Time
- call with conversion
between audio-only and video: End Time = Call start time + (sum
of call durations of video part of call: the values for interim
are updated until the last audio-video call conversion)
Previous Behavior:
-
Accounting (Rf): The
AAA Group obtained from CDF selection feature was used for “VT” calls
only.
-
Customer AVP had current
time. In ACR-STOP, the current time gives the call end time.
New Behavior:
-
The AAA Group obtained
from CDF selection Feature is now used for all calls.
-
Customer AVP, in ACR-STOP
and ACR-INTERIM, should be the sum of Call Start Time and duration
of video part of the call.
For INTERIM, the duration
of video call is now calculated until the last time the call was converted
from video to audio-only. If the current part of the call is of
type video, this duration will be accounted either when call converts
to audio (INTERIM) or call ends (STOP).
E-CSCF Shall Alarm
Upon LDAP Bind or Re-bind Failures
Previous Behavior:
SPRServerReachable and SPRServerUnreachable traps indicated only
the server's IP address.
New Behavior: SPRServerReachable
and SPRServerUnreachable traps now indicate instance ID along with
server's IP address.
New Display Option
for SFTP in psap-file CLI Command
Previous Behavior:
SFTP option was not visible in the options for psap-file CLI command.
New Behavior: SFTP
option is now displayed, along with FTP and file options, for psap-file
CLI command.
SCM Configuration
Management Changes as of January 31, 2013
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.
custom fc-route-uri-param
Enables customizing
of URI in route header entry of AS. Default is disabled.
CSCF Service Configuration
Mode
[ no ] custom
fc-route-uri-param
custom rf-video-duration
Enables customizing
of Rf call duration for video sessions. Default is disabled.
When disabled, the CDF
selected during registration shall be used for all calls.
CSCF Service Configuration
Mode
[ no ] custom
rf-video-duration
Modified SCM Configuration
Commands
This section
identifies SCM commands modified in release 14.0.
psap-file
Sets the location of
the PSAP-Database file to maintain and access the ESRK-Ranges provided
by the operator for the E-CSCF. The following SFTP file format is
now supported when specifying the PSAP-Database file:
sftp://[username]:[password]@host[/directory]/<filename>
- URL
CSCF Emergency-CSCF
Configuration Mode
Deprecated SCM Configuration
Commands
This section
identifies deprecated SCM commands that are no longer supported
in release 14.0.
SCM Performance Management
Changes as of January 31, 2013
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.
The following bulk
statistics are new in this release:
CSCF Schema
- access-transfer-attrx
- access-transfer-atttx
- access-transfer-succrx
- access-transfer-succtx
- access-transfer-failrx
- access-transfer-failtx
- eatf-request
- eatf-success
- eatf-failures
- total-unsup-volte-saa-attempt
- total-unsup-volte-reg-attempt
- total-unsup-volte-reg-success
- total-unsup-volte-reg-failure
Modified SCM Bulk
Statistics
This section
identifies SCM bulk statistics modified in release 14.0.
Deprecated SCM Bulk
Statistics
This section
identifies deprecated SCM bulk statistics that are no longer supported
in release 14.0.
New SCM Performance
Commands
This section
identifies new SCM performance commands available in release 14.0.
Modified SCM Performance
Commands
This section
identifies SCM performance commands modified in release 14.0.
Deprecated SCM Performance
Commands
This section
identifies deprecated SCM performance commands that are no longer
supported in release 14.0.
SCM Security Management
Changes as of January 31, 2013
This section
provides information on SCM security management changes in release 14.0.
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
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
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
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
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
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
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
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:
From/PAI
Header
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
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
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
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
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:
- If it is request, it
will be rejected with 500 server internal error.
- 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
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
Previous Behavior:
- SAR is sent for all deregistrations.
- 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:
- 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.
- 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
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
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
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
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
S-CSCF Cx communication
is being enhanced.
Previous Behavior:
- If the S-CSCF receives
user data greater than 24k, then it accepted the register and no further
Cx interaction took place.
- If S-CSCF receives no
user data, register was rejected with a 403 and no further Cx interaction
took place.
New Behavior:
- 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.
- 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
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
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
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
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
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.
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.
Modified SCM Bulk
Statistics
This section
identifies SCM bulk statistics modified in release 14.0.
Deprecated SCM Bulk
Statistics
This section
identifies deprecated SCM bulk statistics that are no longer supported
in release 14.0.
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:
-
-
-
Total
-
TCP Connections Attempted
-
TCP Connections Successful
-
-
-
NPDB Connections Attempted
-
NPDB Connections Successful
-
-
-
-
-
BIND_ACK Messages
Received
-
-
PING_PONG Retry
Messages Sent
-
PING_PONG_ACK
Messages Received
-
-
QUERY Retry Messages
Sent
-
QUERY_ACK Messages
Received
-
-
REL_RES Messages
Received
-
-
ERRREP_ACK
Messages Received
-
-
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:
Deprecated SCM Performance
Commands
This section
identifies deprecated SCM performance commands that are no longer
supported in release 14.0.
SCM Security Management
Changes as of September 28, 2012
This section
provides information on SCM security management changes in release 14.0.