> CSCF Serving-CSCF Configuration Mode Commands
> The Serving-CSCF Configuration Mode is used to set various commands supporting the role of the CSCF service as a Serving CSCF.
> Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
> 3gpp
> Enables/disables functionality related to 3GPP Release 8 support. This command is disabled by default.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> 3gpp Rel8 Cx { alias-indication | dynamic-password-change | ims-restoration | num-auth-vectors value }
> [ default | no ] 3gpp Rel8 Cx { alias-indication | dynamic-password-change | ims-restoration | num-auth-vectors }
> Rel8 Cx
> Specifies functionality related to 3GPP Release 8 support.
> alias-indication
> Enables alias indication functionality, a collaborative information exchange between the S-CSCF and HSS. Use this command to display alias information from the HSS.
> If both the HSS and the S-CSCF support this feature, Alias Group IDs will be displayed in the output of the show subscribers cscf-only full command.
> dynamic-password-change
> Enables dynamic password change support on the S-CSCF service, as per 3GPP 33.203 release 8 version 8.8.0.
> ims-restoration
> Enables IMS restoration procedures on the S-CSCF service. Use this command to enable IMS REGISTER and INVITE restoration procedures defined in 3GPP TS 23.820.
> num-auth-vectors value
> Enables configurable value for SIP-Number-Auth-Items in MAR.
> value must be an integer from 1 to 3. Default is 1.
> SCSCF can retrieve multiple authentication vectors from HSS by setting SIP-Number-Auth-Items to an appropriate value. Previously, S-CSCF always set this value to “1”. Using higher values helps to reduce MAR-MAA transactions.
> default | no
> Disables specified 3GPP Release 8 support feature.
> Usage
> Use this command to configure the S-CSCF to support 3GPP Release 8 functionality.
> Example
> The following command enables 3GPP Release 8 alias indication functionality on this service:
> 3gpp Rel8 Cx alias-indication
> The following command disables 3GPP Release 8 dynamic password change support on this service:
> no 3gpp Rel8 Cx dynamic-password-change
> allow rfc3261-ua-interworking
> Enables the function to allow IMS interworking with RFC3261 SIP User Agents.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> [ no ] allow rfc3261-ua-interworking
> no
> Disables the interworking capability.
> Usage
> Use this command to enable the S-CSCF to allow IMS interworking with RFC3261 SIP User Agents.
> as-call invite-request-uri update
> Enabling this command causes request-URIs in INVITE messages to be updated with the result of the translation before being passed to an Application Server (AS). This command is disabled by default.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> [ default | no ] as-call invite-request-uri update
> default | no
> The translation result is ignored.
> Usage
> Use this command to update the request-URI in INVITE messages with the result of the translation before passing it to an AS.
> authentication
> Configures the authentication method used by the S-CSCF service.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> authentication { aka-v1 value | allow-auth-rsp-failure re-register | allow-hss-failure re-register | allow-noauth [ invite | re-register| register ] | allow-noipauth [ invite | re-register| register ] | allow-skip-sar re-register | allow-unsecure | aor-auth | custom-md5 value | md5 value }
> no authentication { aka-v1 | allow-auth-rsp-failure re-register | allow-hss-failure re-register | allow-noauth [ invite | re-register| register ] | allow-noipauth [ invite | re-register| register ] | allow-skip-sar re-register | allow-unsecure | aor-auth | custom-md5 | md5 }
> aka-v1 value
> Specifies that AKA-v1 algorithm is used as the authentication type when accessing the CSCF service. value specifies a preference - the lower the value, the higher the preference. value must be an integer from 1 to 1000.
> Important: In order to change a priority level, you must remove the original value and configure a new one.
> allow-auth-rsp-failure re-register
> Specifies that S-CSCF will not validate authorization received from UE for challenge re-register. If enabled, S-CSCF will send SAR without validating authentication; after receiving SAA, it will send 200 OK for register.
> allow-hss-failure re-register
> Specifies that S-CSCF should send 200 OK for re-register in case of HSS failure.
> When S-CSCF receives register, it sends MAR/SAR to HSS to authenticate the user when authentication is enabled and to get the subscriber profile. When S-CSCF fails to receive response MAA/SAA from HSS, it sends 500 error response to UE. When allow-hss-failure is enabled, S-CSCF sends 200 OK for register instead of 500 response.
> allow-noauth [ invite | re-register| register ]
> Specifies that access to the S-CSCF service is allowed if authentication fails.
> invite: Specifies that access to the S-CSCF service is allowed if authentication fails on INVITE requests only.
> re-register: Specifies that access to the S-CSCF service is allowed if authentication fails on RE-REGISTER requests when the request is integrity-protected only.
> registration: Specifies that access to the S-CSCF service is allowed if authentication fails on REGISTER requests only.
> allow-noipauth [ invite | re-register| register ]
> Specifies that access to the S-CSCF service is allowed if early IMS-based IP authentication fails.
> invite: Specifies that access to the S-CSCF service is allowed if early IMS-based IP authentication fails on INVITE requests only.
> re-register: Specifies that access to the S-CSCF service is allowed if authentication fails on RE-REGISTER requests when the request is integrity-protected only.
> registration: Specifies that access to the S-CSCF service is allowed if early IMS-based IP authentication fails on REGISTER requests only.
> allow-skip-sar re-register
> Specifies that S-CSCF should skip SAR to HSS for re-register.
> When S-CSCF receives re-register/challenge for re-register, it sends SAR to HSS to get subscriber profile. To avoid overloading HSS, enabling allow-skip-sar allows S-CSCF to skip SAR for re-register.
> allow-unsecure
> Specifies that un-secure access is allowed to the S-CSCF service.
> aor-auth
> Specifies that authentication is based on the AoR when accessing the S-CSCF service.
> custom-md5 value
> Specifies that custom algorithm HTTP-Digest-MD5 is used as the authentication type for accessing the S-CSCF service. value specifies a preference - the lower the value, the higher the preference. value must be an integer from 1 to 1000.
> Important: In order to change a priority level, you must remove the original value and configure a new one.
> md5 value
> Specifies that the MD5 algorithm is used as the authentication type for accessing the S-CSCF service.
> value specifies a preference - the lower the value, the higher the preference. value must be an integer from 1 to 1000.
> Important: In order to change a priority level, you must remove the original value and configure a new one.
> no authentication { aka-v1 | allow-auth-rsp-failure re-register | allow-hss-failure re-register | allow-noauth [ invite | re-register| register ] | allow-noipauth [ invite | re-register| register ] | allow-skip-sar re-register | allow-unsecure | aor-auth | custom-md5 | md5 }
> Disables the specified authentication method for the S-CSCF service.
> Usage
> Use this command to configure the authentication method used by the S-CSCF service.
> Important: The S-CSCF supports multiple authorization schemes, but this requires disabling all authorization configured in the S-CSCF service so that it will send “Unknown” in the Sip-Authorization-Scheme AVP. This allows the HSS to dictate authorization. The following commands disable all authorization configured in the S-CSCF service to allow HSS to control authorization:
> authentication allow-noipauth
> allow rfc3261-ua-interworking
> no authentication aka-v1
> no authentication md5
> Example
> The following command configures the authentication method used by the S-CSCF service to MD5 with a preference of 3:
> authentication md5 3
> bgcf-proxy
> Enables SIP BGCF proxy for the service.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> bgcf-proxy [ port value | transport { tcp | udp } port value ] ]
> [ default | no ] bgcf-proxy
> port value
> Configures port value for SIP BGCF proxy.
> value must be an integer from 1 to 65534.
> transport
> Enables the specific transport protocol for BGCF proxy.

> • | tcp: Enables TCP transport protocol for BGCF proxy.

> • | udp: Enables UDP transport protocol for BGCF proxy.

> default | no
> Disables SIP BGCF proxy for the service.
> Usage
> Use this command to enable or disable SIP BGCF proxy for the service.
> Example
> The following command enables a SIP BGCF proxy on port 561 for this service:
> bgcf-proxy port 561
> The following command disables SIP BGCF proxy for this service:
> no bgcf-proxy
> diversion-info
> Enabling this command prompts the service to add a diversion header (draft-levy-sip-diversion-08) when the call is diverted to a different endpoint due to a call feature. By default, diversion-info is disabled.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> [ default | no ] diversion-info
> default | no
> The service will not add a diversion header.
> Usage
> Use this command to enable the service to add a diversion header to call setup packets when calls are diverted due to the application of call features.
> end
> Exits the current mode and returns to the Exec Mode.
> Product
> All
> Privilege
> Administrator
> Syntax
> end
> Usage
> Change the mode back to the Exec mode.
> exit
> Exits the current mode and returns to the previous mode.
> Product
> All
> Privilege
> Administrator
> Syntax
> exit
> Usage
> Return to the previous mode.
> forking
> Controls the default-request forking-type in S-CSCF.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> forking { parallel | serial }
> [ default | no ] forking
> parallel | serial
> Defines the fork type for request forking.

> • | parallel: Perform parallel forking of request.

> • | serial: Perform serial forking of request.

> default
> Perform parallel forking of request.
> no
> Do not perform any forking of request.
> Usage
> Use this command to control the default-request forking-type in S-CSCF. This configuration will be effective in the absence of “Request-Disposition” header in the message.
> Example
> The following command enables serial forking of request:
> forking serial
> The following command disables any forking of request:
> no forking
> interrogating-cscf-role
> Enables the function to also perform as an Interrogating-CSCF.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> [ no ] interrogating-cscf-role
> no
> Disables the Interrogating-CSCF role in this function.
> Usage
> Use this command to enable the S-CSCF to also perform as an Interrogating-CSCF.
> local-call-features
> Enables/disables local call features. This command is disabled by default.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> [ default | no ] local-call-features
> default | no
> Disables local call features for this S-CSCF.
> Usage
> Use this command to enable local call features.
> network-id
> Configures the Network Identifier.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> network-id id
> no network-id
> id
> The Network Identifier of the entity.
> id must be from 1 to 79 alpha and/or numeric characters in length.
> no
> Removes the configured Network Identifier of the entity.
> Usage
> The Network Identifier is used to compare with the P-Visited-Network-ID header received from P-CSCF to decide home or roaming subscriber at S-CSCF service.
> Example
> Sets the Network Identifier to pcscf01.company.com:
> network-id pcscf01.company.com
> npdb-client
> Creates an NPDB (Number Portability Data Base) client under CSCF and enters the CSCF NPDB Client Configuration Mode.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> npdb-client client_name [ -noconfirm ]
> no npdb-client
> client_name
> Specifies the name of the NPDB client.
> client_name must be from 1 to 79 alpha and/or numeric characters.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> no
> Deletes NPDB client under CSCF.
> Usage
> Use this command to enable the NPDB client feature and enter the NPDB Client Configuration Mode.
> Entering this command results in the following prompt:
> [context_name]hostname(config-npdb-client)#
> NPDB Client Configuration Mode commands are defined in the CSCF NPDB Client Configuration Mode Commands chapter in this guide.
> Example
> The following command creates an NPDB client named npdb1 and enters NPDB Client Configuration Mode:
> npdb-client npdb1
> policy
> Configures the policy for Served User Routing in this S-CSCF service.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> [ default | no ] policy allow p-served-user-routing
> default | no
> Disables Served User Routing functionality for this S-CSCF.
> allow p-served-user-routing
> Enables Served User Routing functionality for this S-CSCF.
> Usage
> Use this command to enable/disable the policy for Served User Routing.
> Example
> The following command enables Served User Routing on this service:
> policy allow p-served-user-routing
> The following command disables Served User Routing on this service:
> no policy allow p-served-user-routing
> registration lifetime
> Configures a registration lifetime for all subscribers to the service.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> registration lifetime { default sec | implicit sec | max sec | min sec }
> default registration lifetime
> { default sec | implicit sec | max sec | min sec }
> default sec: Specifies the default amount of time that a registration can exist on the system.
> sec must be an integer from 60 to max sec -1.
> Default: 3600
> Important: default sec must be < or = to max sec and > or = to min sec.
> implicit sec: Specifies the implicit amount of time that a registration can exist on the system. sec must be an integer from 60 to 1209600.
> Default: 0
> max sec: Specifies the maximum amount of time that a registration can exist on the system.
> sec must be an integer from 60 to 1209600.
> Default: 86400
> Important: max sec must be > or = to min sec.
> min sec: Specifies the minimum amount of time that a registration can exist on the system.
> sec must be an integer from 60 to max sec -1.
> Default: 60
> Important: min sec must be < or = to max sec.
> default
> Returns the command to the default settings.
> Usage
> Use this command to control the amount of time registrations are allowed to exist on this service.
> The system responds to registrations in the following manner:
> If implicit-timer is configured (>0), and if UE expires time < min expires time, respond with 200 OK with Expires-header set to configured implicit-expires time.
> If implicit timer is not configured (=0), the service will respond with a 423 Interval Too Small message.
> Using default values:

> • | If a registration with an expiration value lower than the service’s minimum (60) is received, the service will respond with a 423 Interval Too Small message.

> • | If a registration with an expiration value higher than the service’s maximum (2147483646) is received, the service will automatically reduce the expiration value to the default value.

> • | If a registration is received missing the “Expires” value, or the value is malformed, the service will automatically respond with 3761 in the 200 OK message.

> Example
> The following command configures the maximum registration lifetime to 43200 (12 hours):
> registration lifetime max 43200
> reliable-prov-resp
> Enables/disables the reliability of provisional responses feature.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> reliable-prov-resp { mandatory | optional }
> no reliable-prov-resp
> mandatory | optional
> mandatory: Both inbound and outbound will request reliability.
> optional (default): Reliability is imposed by inbound side. Only if inbound call requests reliability will outbound also request reliability.
> no
> Disables the reliability of provisional responses feature.
> Usage
> Use this command to enable/disable the reliability of provisional responses feature.
> Example
> The following command sets the reliability of provisional responses feature to mandatory:
> reliable-prov-resp mandatory
> server-name
> Enables/disables filling the server name AVP in MAR and SAR for Cx interface with configured server name. This command is disabled by default.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> server-name server_name
> no server-name
> server_name
> Configures the name that will be used to fill the server name AVP in MAR and SAR for Cx interface.
> name must be from 1 to 63 alpha and/or numeric characters.
> no
> S-CSCF uses configured cscf-hostname or bind IP address to fill the server name AVP in MAR and SAR for Cx interface. This is the default CSCF behavior.
> Usage
> Use this command to enable/disable filling the server name AVP in MAR and SAR for Cx interface with configured server name.
> Example
> The following command configures the CSCF server name as stp-c-scscf1.cisco.co.kr:
> server-name stp-c-scscf1.cisco.co.kr
> sifc
> Enables Shared Initial Filter Criteria (SiFC) functionality. This command is disabled by default.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> [ default | no ] sifc
> default | no
> Disables shared iFC functionality for this S-CSCF.
> Usage
> Use this command to configure the S-CSCF to share iFC functionality.
> Important: 48 SiFC IDs are supported per subscriber.
> If both the HSS and the S-CSCF support this feature, subsets of iFC may be shared by several service profiles. The HSS downloads the unique identifiers of the shared iFC sets to the S-CSCF. The S-CSCF uses a locally administered database to map the downloaded identifiers onto the shared iFC sets.
> If the S-CSCF does not support this feature, the HSS will not download identifiers of shared iFC sets.
> Important: When using this feature option, the network operator is responsible for keeping the local databases in the S-CSCFs and HSSs consistent.
> sip-header insert
> Enable SIP header insertion for the S-CSCF service. SIP header insertion is disabled by default.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> [ no ] sip-header insert { p-cust1-prid-info | p-user-database }
> no
> Disables specific SIP header insertion for the S-CSCF service.
> p-cust1-prid-info
> Inserts a custom header, P-LGUPlus-PRID-Info, which contains the private user id of the user sending the REGISTER request, to be added in the REGISTER message toward AS during third party registration.
> p-user-database
> Inserts PUD header in SIP (REGISTER) message and Invite from I-CSCF to S-CSCF.
> Usage
> Enabling this command allows header insertion in SIP (REGISTER) message.
> Example
> The following command disables insertion of custom header, P-LGUPlus-PRID-Info, in SIP (REGISTER) message:
> no sip-header insert p-cust1-prid-info 5
> The following command enables insertion of PUD header in SIP (REGISTER) message and Invite from I-CSCF to S-CSCF:
> sip-header insert p-user-database 5
> sip-request
> Configures SIP Request-related configuration in this S-CSCF service.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> sip-request re-route { max-attempts attempts | response-code code }
> default sip-request re-route max-attempts
> no sip-request re-route response-code code
> re-route
> Specify SIP Request re-route related configuration.
> max-attempts attempts
> Specifies the maximum number of re-route attempts that a S-CSCF should allow for a given call before passing the negative response upstream.
> attempts must be an integer from 1 to 10.
> Default: 2
> response-code code
> Specifies the list of Response codes that will be considered as re-routable responses to a call attempt.
> code must be a three-digit integer from 400 to 699.
> Important: You may configure a maximum of five response code values per S-CSCF service.
> default
> Specifies a maximum number of two re-route attempts that a S-CSCF should allow for a given call before passing the negative response upstream.
> no
> Disables the specified Response code.
> Usage
> Use this command to configure:

> • | list of Response codes that will be considered as re-routable responses to a call attempt.

> • | the maximum number of re-route attempts that a S-CSCF should allow for a given call before passing the negative response upstream.

> Example
> The following command configures the maximum number of re-route attempts to 5:
> sip-request re-route max-attempts 5
> tas
> Configures the S-CSCF to perform Telephony Application Server (TAS) functions.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> [ default | no ] tas
> default | no
> Disables the TAS feature for this S-CSCF.
> Usage
> Use this command to configure the S-CSCF to perform TAS functions.
> tas-service
> Identifies the name of the service configured on the system performing Telephony Application Server (TAS) functions.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> tas-service name
> no tas-service
> name
> Specifies the name of the service configured on the system performing TAS functions.
> name must be from 1 to 63 alpha and/or numeric characters and be an existing service.
> no
> Removes the TAS name from the S-CSCF configuration.
> Usage
> Use this command to identify the name of the service configured on the system performing TAS functions
> Example
> The following command identifies the TAS service name as scscf3:
> tas-service scscf3
> user-authorization
> Enables sending user-authorization to HSS. User-authorization is disabled by default.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> [ default | no ] user-authorization
> default | no
> Disables sending user-authorization to HSS.
> Usage
> If this command is enabled, and I-CSCF role is enabled in S-CSCF, I-CSCF will send UAR/UAA diameter message to HSS.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883