> CSCF Proxy-CSCF Configuration Mode Commands
> The Proxy-CSCF Configuration Mode is used to enable Diameter policy control within the service.
> Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
> allow rfc3261-ua-interworking
> Enables the function to allow IMS interworking with RFC3261 SIP User Agents.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] allow rfc3261-ua-interworking
> no
> Disables the interworking capability.
> Usage
> Use this command to enable the P-CSCF/A-BG to allow IMS interworking with RFC3261 SIP User Agents.
> core-reg-expiry-time
> Configures Registration Expiry Timer Handling in P-CSCF/A-BG to keep pin holes open in B2BUA mode.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> core-reg-expiry-time sec
> [ default | no ] core-reg-expiry-time
> sec
> Expiry age should be less than or equal to the maximum in seconds. Must be an integer from 300 to 86400.
> default
> Sets the core-reg-expiry-time to 3600 seconds.
> no
> Disables the timer.
> Usage
> Use this command to configure Registration Expiry Timer Handling in P-CSCF/A-BG to keep pin holes open in B2BUA mode.
> Example
> The following sets the core-reg-expiry-time to 4000 seconds:
> core-reg-expiry-time 4000
> diameter
> This command:

> • | configures the Diameter dictionary used in this function.

> • | configures the policy control origin endpoint used in this function.

> • | enables the selection of a Diameter policy control peer server providing Rx/Tx/Gq applications for this service.

> • | configures the Diameter requested timeout value used in this function.

> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> diameter location-info { dictionary { e2custom01 | e2custom02 | e2custom03 | e2custom04 | e2custom05 | e2custom06 | e2custom07 | e2custom08 | e2custom09 | e2standard } | origin endpoint endpoint_name | peer-select peer peer_name [ peer-realm realm_name ] [ secondary-peer peer_name [ sec-peer-realm realm_name ] ] | request-timeout sec }
> diameter policy-control { dictionary { Gq-custom | Gq-standard | Rq-custom| Rx-rel8 | Rx-standard | Tx-standard | custom01 | custom02 | custom03 | custom04 | custom05 | custom06 | custom07 | custom08 | custom09 } | origin endpoint endpoint_name | peer-select peer peer_name [ peer-realm realm_name ] [ secondary-peer peer_name [ sec-peer-realm realm_name ] ] | request-timeout sec }
> In StarOS v12.2 and later:
> diameter policy-control { dictionary { gq-custom | gq-standard | rq-custom | rx-custom01 | rx-custom02 | rx-custom03 | rx-custom04 | rx-custom05 | rx-rel8 | rx-standard | tx-standard } | origin endpoint endpoint_name | peer-select peer peer_name [ peer-realm realm_name ] [ secondary-peer peer_name [ sec-peer-realm realm_name ] ] | request-timeout sec }
> default diameter { location-info | policy-control } { dictionary | request-timeout }
> no diameter { location-info | policy-control } [ origin endpoint | peer-select ]
> location-info
> Defines the E2 interface for location information.
> dictionary { e2custom01...e2custom09 | e2standard }
> custom01...custom09: Specifies that a customer-specific (custom) dictionary is to be used for expansion and behaviors.
> e2standard: Specifies that the E2-Standard-Dictionary is to be used.
> Important: If this keyword is not configured, the system defaults to the default dictionary (e2standard). In the Proxy-CSCF configuration, at any time, the location-info dictionary can either be an explicitly configured dictionary or the default dictionary. Hence, there is no corresponding “no” CLI to disable the location-info dictionary setting.
> policy-control
> Defines external policy control.
> dictionary { Gq-custom | Gq-standard | Rq-custom | Rx-rel8 | Rx-standard | Tx-standard | custom01...custom09 }
> Gq-custom: Specifies that the Gq Operax dictionary is to be used for Operax-specific behavior.
> Gq-standard: Specifies that the Gq standard dictionary is to be used.
> Rq-custom: Specifies that the Rq custom dictionary is to be used.
> Rx-rel8: Specifies that the Rx Release 8 dictionary is to be used.
> Rx-standard: Specifies that the Rx standard dictionary is to be used.
> Tx-standard: Specifies that the Tx standard dictionary is to be used.
> custom01...custom09: Specifies that a customer-specific (custom) dictionary, for customer-specific expansion and behaviors, is to be used.
> dictionary { gq-custom | gq-standard | rq-custom | rx-custom01 | rx-custom02 | rx-custom03 | rx-custom04 | rx-custom05 | rx-rel8 | rx-standard | tx-standard }
> gq-custom : Specifies that the Gq Operax dictionary is to be used for Operax-specific behavior.
> gq-standardd: Specifies that the Gq standard dictionary is to be used.
> rq-custom: Specifies that the Rq custom dictionary is to be used.
> rx-custom01...rx-custom05: Specifies that a customer-specific (custom) dictionary, for customer-specific expansion and behaviors, is to be used.
> rx-rel8: Specifies that the Rx Release 8 dictionary is to be used.
> rx-standard: Specifies that the Rx standard dictionary is to be used.
> tx-standard: Specifies that the Tx standard dictionary is to be used.
> origin endpoint endpoint_name
> Specifies the Diameter location-info or policy control endpoint name.
> endpoint_name must be the endpoint’s name and an alpha and/or numeric string of 1 through 63 characters in length.
> peer-select peer peer_name
> Specifies the name of the Diameter location-info or policy control peer server.
> peer_name must be from 1 to 63 alpha and/or numeric characters in length.
> Diameter peer servers are configured through the diameter endpoint command in the Context Configuration Mode. The diameter endpoint command is a generic command and can be found in the Cisco ASR 5000 Series Command Line Interface Reference.
> peer-realm realm_name
> Specifies the realm name for which the Diameter location-info or policy control peer server has responsibility.
> realm_name must be from 1 to 63 alpha and/or numeric characters in length.
> Important: If this keyword is not configured, the system defaults to the realm name configured for the selected peer server.
> secondary-peer peer_name
> Specifies the name of the secondary Diameter location-info or policy control peer server.
> peer_name must be from 1 to 63 alpha and/or numeric characters in length.
> sec-peer-realm realm_name
> Specifies the realm name for which the secondary Diameter location-info or policy control peer server has responsibility.
> realm_name must be from 1 to 63 alpha and/or numeric characters in length.
> Important: If this keyword is not configured, the system defaults to the realm name configured for the selected peer server.
> Important: The “diameter location-info peer-select peer <primary_peer> peer-realm <primary_peer_realm> secondary-peer <secondary_peer> sec-peer-realm <secondary_peer_realm>” CLI configures Peer Switching—selecting which peers the Diameter messages are routed to. When the secondary peer is configured, in case the primary fails, request messages are rerouted to the secondary. Note that the “no diameter location-info peer-select” CLI command will remove the entire Peer Switching CLI from the configuration.
> request-timeout sec
> Specifies the Diameter location-info or policy control requested timeout value in seconds.
> sec must be an integer from 1 to 300.
> Default: 10
> Important: If this keyword is not configured, the system defaults to the default setting (10 seconds). In the Proxy-CSCF configuration, at any time, the request-timeout setting can either be an explicitly configured value or the default value. Hence, there is no corresponding “no” CLI to disable the request-timeout setting.
> default
> Sets the Diameter’s location-info or policy control dictionary or requested timeout value as the default.
> no
> Removes the Diameter location-info or policy control origin endpoint or Diameter peer from the service.
> Usage
> Use this command to:

> • | define the Diameter dictionary to use for the service.

> • | specify the Diameter origin endpoint.

> • | specify a Diameter location-info or policy control peer server to support Rx/Tx/Gq applications.

> • | specify the Diameter requested timeout value for this service.

> Example
> The following command configures the system to use the Tx standard Diameter dictionary for this service:
> diameter policy-control dictionary Tx-standard
> The following command sets the Diameter location-info origin endpoint to test:
> diameter location-info origin endpoint test
> The following command selects a Diameter policy control peer server with a name of diam-2 and a realm name of realm-6:
> diameter policy-control peer-select peer diam-2 peer-realm realm-6
> 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 [ visited-ue ]
> Allow emergency-registration. By default, it's allowed.
> visited-ue: Allow emergency-registration from a visited UE. By default, it's allowed.
> session [ 3gpp-ims-xml-body | anonymous | non-emergency-registered | sdp-cs-media | visited-ue ]
> 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
> emergency-call-mode
> Enables the P-CSCF/A-BG service to add “P-Emergency-Call-Mode-Preference” header in 200OK to REGISTER message. By default, this command is disabled.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> emergency-call-mode { 3gpp-cs | 3gpp-ims }
> [ default | no ] emergency-call-mode
> 3gpp-cs | 3gpp-ims
> 3gpp-cs: Specifies 3GPP CS access preference in header.
> 3gpp-ims (default): Specifies 3GPP IMS access preference in header.
> default
> Specifies 3GPP IMS access preference in header.
> no
> Disables “P-Emergency-Call-Mode-Preference” header insertion for the P-CSCF/A-BG service.
> Usage
> Enabling this command allows the P-CSCF or A-BG to add a “P-Emergency-Call-Mode-Preference” header in 200OK to REGISTER message.
> Example
> The following command enables “P-Emergency-Call-Mode-Preference” header insertion with a 3GPP CS access preference defined:
> emergency-call-mode 3gpp-cs
> 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.
> interrogating-cscf-role
> Enables the function to also perform as an Interrogating-CSCF.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] interrogating-cscf-role
> no
> Disables the Interrogating-CSCF role in this function.
> Usage
> Use this command to enable the P-CSCF/A-BG to also perform as an Interrogating-CSCF.
> Important: All Interrogating-CSCF functions have been moved to the Serving-CSCF exclusively in v10.0 and beyond.
> message-max-size
> Configures the maximum message body size in MESSAGE method.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> message-max-size limit
> [ default | no ] message-max-size
> limit
> Default: 1024
> Configures the maximum SIP message size limit in bytes for any SIP message buffer.
> limit must be an integer from 512 to 65535.
> Important: Message body size should be less than the max-sipmsg-size set in the CSCF Service Configuration Mode.
> default | no
> Returns/sets the maximum SIP message size to 1024 bytes.
> Usage
> Use this command to configure the maximum SIP message size for any SIP message buffer.
> Example
> The following command limits the SIP message size to 4000 bytes:
> message-max-size 4000
> network-id
> Configures the Network Identifier.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] network-id id
> no
> Removes the configured Network Identifier of the entity.
> id
> The Network Identifier of the entity.
> id must be from 1 to 79 alpha and/or numeric characters in length.
> Usage
> The Network Identifier is used by the P-CSCF or A-BG to fill the P-Visited-Network-ID header.
> Example
> Sets the Network Identifier to pcscf01.company.com:
> network-id pcscf01.company.com
> pcrf-policy-control
> Enables enables external policy control via PCRF through the Rx Diameter interface and enters the PCRF-Policy-Control Configuration Mode. Default is disabled.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] pcrf-policy-control
> no
> Disables external policy control via PCRF for this service. P-CSCF/A-BG will not establish any Diameter session with PCRF, even though the PCRF is configured. This option disables both authorization and subscription to PCRF during Registration and VOIP call.
> Usage
> Use this command to enable PCRF policy control and enter the PCRF-Policy-Control Configuration Mode. It enables authorization and subscription to PCRF during Registration and VOIP calls. If the P-CSCF cannot connect to the PCRF server (due to wrong configuration in CSCF or PCRF unavailability), then P-CSCF/A-BG does not authorize media and VOIP calls will be rejected due to auth failure. Registrations will be handled normally.
> Entering this command results in the following prompt:
> [context_name]hostname(config-pcrf-policy-control)#
> PCRF-Policy-Control Configuration Mode commands are defined in the CSCF PCRF-Policy-Control Configuration Mode Commands chapter in this guide.
> peer-sbc
> Configures peer Session Border Controller (SBC) addresses from where the P-CSCF/A-BG service can receive requests.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] peer-sbc ip_address
> no
> Removes the IP address of a peer SBC from this P-CSCF/A-BG service.
> ip_address
> Specifies the IP address of a peer SBC for this P-CSCF/A-BG service.
> ip_address is expressed in standard dotted decimal notation for IPv4 or colon notation for IPv6.
> Usage
> Use this command to specify peer Session Border Controller (SBC) addresses from where the P-CSCF/A-BG service can receive requests.
> Important: This command must be entered multiple times if more than one SBC is present.
> Example
> The following commands identify three peer SBCs for a single P-CSCF/A-BG service:
> peer-sbc 200.6.2.3
> peer-sbc 200.6.2.10
> peer-sbc 200.6.2.11
> The following command removes the peer SBC with IP address 200.6.2.10 from the P-CSCF/A-BG service:
> no peer-sbc 200.6.2.10
> plmn-id
> Configures location specific mobile network identifiers used to help translate local emergency and service-related numbers. Default is disabled.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> plmn-id mcc code mnc code
> no plmn-id
> mcc code
> Specifies the Mobile Country Code for the mobile access network. code must be a three-digit integer from 200 to 999.
> mnc code
> Specifies the Mobile Network Code for the mobile access network. code must be a two or three-digit integer from 00 to 999.
> no
> Removes the access network configuration for this P-CSCF/A-BG service.
> Usage
> Use this command to help match location specific emergency/service numbers when configuring translations.
> The mcc and mnc values are compared against those received in p-access-network-info headers as per 3GPP TS 24.229. If mnc is not provided in the criteria only mcc is compared.
> Example
> The following command identifies the mobile network with a MCC of 123 and a MNC of 12:
> plmn-id mcc 123 mnc 12
> reg-preloaded-route
> Enables the function to use the preloaded-route-headers received in REGISTER for routing at P-CSCF.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ default | no ] reg-preloaded-route
> default | no
> Disables the ability to use preloaded-route-headers for routing REGISTER.
> Usage
> Use this command to enable or disable usage of preloaded-route-headers for routing REGISTER.
> reg-service-route
> Enables the function to use service routes when routing re-registrations.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] reg-service-route
> no
> Disables the ability to use service routes for re-registration.
> Usage
> Use this command to enable the P-CSCF/A-BG service to use service routes when routing re-registrations.
> reliable-prov-resp
> Enables/disables the reliability of provisional responses feature.
> Product
> SCM (P-CSCF, A-BG)
> 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
> restoration-procedure
> Enables the P-CSCF/A-BG service to reject with a 504 response when it receives 3xx, 480, or “no response” to service request. This feature is disabled by default.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] restoration-procedure
> no
> Disables restoration procedure on the P-CSCF/A-BG service.
> Usage
> Restoration procedure is intended to handle unreachability of service-route header content. Enabling this command allows the P-CSCF/A-BG service to reject with a 504 response when it receives 3xx, 480, or “no response” to service request.
> Example
> Enables restoration procedure on the P-CSCF/A-BG service:
> restoration-procedure
> Disables restoration procedure on the P-CSCF/A-BG service:
> no restoration-procedure
> security-parameters
> Enters the Security Configuration Mode in which Denial of Service (DOS) prevention commands can be configured.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> security-parameters
> Usage
> Use this command to enter the Security Configuration Mode.
> Entering this command results in the following prompt:
> [context_name]hostname(config-security-parameters)#
> Security Configuration Mode commands are defined in the CSCF Security Configuration Mode Commands chapter in this guide.
> sigcomp
> Enables signaling compression for the P-CSCF/A-BG service and enters the Signaling Compression Configuration Mode.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] sigcomp
> no
> Disables signaling compression for the P-CSCF/A-BG service.
> Usage
> Use this command to enable signaling compression for the P-CSCF/A-BG 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.
> sip-header
> Enable SIP header insertion for the P-CSCF/A-BG service. SIP header insertion is disabled by default.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] sip-header insert { p-access-network-info | p-cust1-prid-info | p-user-database }
> no
> Disables SIP header insertion for the P-CSCF/A-BG service.
> insert { p-access-network-info | p-cust1-prid-info | p-user-database }
> p-access-network-info: Inserts P-Access-Network-Info (PANI) header in received request/response.
> p-cust1-prid-info: Inserts a custom header, P-LGUPlus-PRID-Info, which contains the private user id of the user sending any dialogue creating request or any standalone requests, to be added in the message toward nexthop. Addition of the header will be done when P-CSCF forwards this message.
> p-user-database: Inserts P-User-Database (PUD) header in SIP (REGISTER) message and Invite from I-CSCF to S-CSCF.
> Usage
> Enabling this command allows SIP header insertion on the P-CSCF or A-BG.
> Important: Use the access-type command to configure a ue-ip-address-range per access type. CSCF Service Configuration Mode commands are defined in the CSCF Service Configuration Mode Commands chapter in this guide.
> Example
> Enables SIP PANI header insertion for the P-CSCF/A-BG service:
> sip-header insert p-access-network-info
> sip-param
> Enable the addition of “integrity-protected” parameter in the authorization header of a SIP (REGISTER) message for the P-CSCF/A-BG service.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] sip-param insert integrity-protected [ transparent ]
> no
> Disables the addition of “integrity-protected” parameter in the authorization header of a SIP (REGISTER) message for the P-CSCF/A-BG service.
> insert integrity-protected
> Inserts “integrity-protected” parameter in the authorization header of a SIP (REGISTER) message for the P-CSCF/A-BG service.
> transparent
> Pass the “integrity-protected” parameter received from the previous node unmodified.
> Usage
> Enabling this command allows the P-CSCF or A-BG to add the “integrity-protected” parameter in the authorization header of a SIP (REGISTER) message. The parameter will be used by the S-CSCF to decide which authentication mode to use to authenticate the user.
> Example
> Enables the addition of integrity-protected parameter:
> sip-param insert integrity-protected
> Disables the addition of integrity-protected parameter:
> no sip-param insert integrity-protected
> store-session-path
> Enables the P-CSCF or A-BG to store and process the session path information, which includes the Route list, Record-Route list, Service-Route list, and ViaList.
> Product
> SCM (P-CSCF, A-BG)
> Privilege
> Administrator
> Syntax
> [ no ] store-session-path
> no
> Disables the storing of session path information by the P-CSCF or A-BG. In addition, the P-CSCF/A-BG will not overwrite the Route list, Record-Route list, Service-Route list, or ViaList in the in-dialog request and responses.
> Usage
> Enabling this command allows the P-CSCF or A-BG to store and process the session path information.
> Example
> Enables the storage and processing of session path information:
> store-session-path
> Disables the storage and processing of session path information:
> no store-session-path

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