> CSCF SIP Proxy Configuration Mode Commands
> The SIP Proxy Configuration Mode is used to set various commands supporting the role of the CSCF service as a RFC3261-compliant SIP proxy server.
> Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
> as-call
> 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. 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 CSCF service.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> authentication { aka-v1 value | allow-noauth [ invite | re-register| register ] | allow-noipauth [ invite | re-register| register ] | allow-unsecure | aor-auth | md5 value }
> no authentication { aka-v1 | allow-noauth [ invite | re-register| register ] | allow-noipauth [ invite | re-register| register ] | allow-unsecure | aor-auth | 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-noauth [ invite | re-register| register ]
> Specifies that access to the CSCF service is allowed if authentication fails.
> invite: Specifies that access to the CSCF service is allowed if authentication fails on INVITE requests only.
> re-register: Specifies that access to the CSCF service is allowed if authentication fails on RE-REGISTER requests when the request is integrity-protected only.
> registration: Specifies that access to the CSCF service is allowed if authentication fails on REGISTER requests only.
> allow-noipauth [ invite | re-register| register ]
> Specifies that access to the CSCF service is allowed if early IMS-based IP authentication fails.
> invite: Specifies that access to the CSCF service is allowed if early IMS-based IP authentication fails on INVITE requests only.
> re-register: Specifies that access to the CSCF service is allowed if authentication fails on RE-REGISTER requests when the request is integrity-protected only.
> registration: Specifies that access to the CSCF service is allowed if early IMS-based IP authentication fails on REGISTER requests only.
> allow-unsecure
> Specifies that un-secure access is allowed to the CSCF service.
> aor-auth
> Specifies that authentication is based on the AoR when accessing the CSCF service.
> md5 value
> Specifies that the MD5 algorithm is used as the authentication type for 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.
> no authentication { aka-v1 | allow-noauth [ invite | re-register| register ] | allow-noipauth [ invite | re-register| register ] | allow-unsecure | aor-auth | md5 }
> Disables the specified authentication method for the CSCF service.
> Usage
> Use this command to configure the authentication method used by the 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 CSCF service to MD5 with a preference of 3:
> authentication md5 3
> 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.
> emergency
> Configures the function to allow or disallow the emergency-session or emergency-registration of a particular type.
> Product
> SCM (P-CSCF, A-BG, SIP Proxy)
> Privilege
> Administrator
> Syntax
> [ default | no ] emergency { registration [ visited-ue ] | session [ 3gpp-ims-xml-body | anonymous | non-emergency-registered | sdp-cs-media | visited-ue ] }
> default
> Specifies that the emergency-session or emergency-registration of a particular type can be allowed.
> no
> Disallows the emergency-session or emergency-registration of a particular type.
> registration
> Allow emergency-registration. By default, it's allowed.
> visited-ue: Allow emergency-registration from a visited UE. By default, it's allowed.
> session
> Specifies the type of emergency-session to be allowed or disallowed. By default, all are allowed.
> 3gpp-ims-xml-body: Allow 3GPP IM CN XML body to be added in 380 response messages.
> anonymous: Allow anonymous subscribers (unregistered UEs) to initiate emergency sessions.
> non-emergency-registered: Allow non-emergency registered subscribers to initiate emergency sessions.
> sdp-cs-media: Allow emergency calls with SDP CS Media.
> visited-ue: Allow emergency calls from visited UE.
> Usage
> Use this command to configure the function to allow or disallow the emergency-session or emergency-registration of a particular type.
> Example
> The following command configures the function to allow non-emergency registered subscribers to initiate emergency sessions:
> emergency session non-emergency-registered
> 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.
> registration
> Configures a registration lifetime for all subscribers to the service.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> registration lifetime { default sec | max sec | min sec }
> default registration lifetime
> { default 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 is 3600. default sec must be < or = to max sec and > or = to min sec.
> 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 is 86400. 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 is 60. min sec must be < or = to max sec.
> default registration lifetime
> 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:
> 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 200OK 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
> The following command disables the reliability of provisional responses feature:
> no reliable-prov-resp
> 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 SIP Proxy.
> Usage
> Use this command to configure the SIP Proxy to share iFC functionality.
> If both the HSS and the SIP Proxy 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 SIP Proxy. The SIP Proxy uses a locally administered database to map the downloaded identifiers onto the shared iFC sets.
> If the SIP Proxy 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.
> sigcomp
> Enables signaling compression for the SIP Proxy service and enters the Signaling Compression Configuration Mode.
> Product
> SCM (S-CSCF, SIP Proxy)
> Privilege
> Administrator
> Syntax
> [ no ] sigcomp
> no
> Disables signaling compression for the CSCF service.
> Usage
> Use this command to enable signaling compression for the SIP Proxy service and enter the CSCF Signaling Compression Configuration Mode.
> Entering this command results in the following prompt:
> [context_name]hostname(config-sigcomp)#
> Signaling Compression Configuration Mode commands are defined in the CSCF Signaling Compression Configuration Mode Commands chapter in this guide.
> tas
> Configures the SIP Proxy 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 SIP Proxy.
> Usage
> Use this command to configure the SIP Proxy 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
> [ default | 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.
> default | no
> Removes the TAS name from the SIP Proxy configuration.
> Usage
> Use this command to identify the name of the service configured on the system performing TAS functions.
> The ims-sh-service commands are defined in the Context Configuration Mode Commands chapter in this guide.
> Example
> The following command identifies the TAS service name as scscf3:
> tas-service scscf3

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