> CSCF Peer Server Monitoring Configuration Mode Commands
> The CSCF Peer Server Monitoring Configuration Mode is used to configure an individual peer server’s monitoring parameters and operational mode. It also associates a network session template with the server.
> Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
> dummy-as
> Sets a response code for Dummy-AS peer server.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> dummy-as custom-response-code SIP_response_code
> default dummy-as custom-response-code
> custom-response-code SIP_response_code
> If the peer server is configured as dummy-as and it is chosen as per routing table configured, a UMM response message will be formed with the response code configured and sent as reply to incoming MESSAGE/PUBLISH requests.
> SIP_response_code must be an integer from 200 to 699.
> Important: The response code can be 2xx/4xx/5xx/6xx; 3xx,401,and 407 are not allowed.
> default dummy-as custom-response-code
> Sets the response code to 200.
> Usage
> Use this command to configure a response code for Dummy-AS. If this mode is selected, then MESSAGE/PUBLISH requests will be responded to by S-CSCF with configured response code.
> Example
> The following command configures AS as Dummy-AS with a corresponding response code of 425:
> dummy-as custom-response-code 425
> 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.
> ims-capable
> Indicates whether the peer server belongs to a 3GPP/IMS network or a non-IMS network such as the Internet. This command is used to determine at the S-CSCF whether SIP signaling inter-working is needed when the calls are forwarded to external networks.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> [ no ] ims-capable
> no
> Removes the identification of “IMS capable” from the selected peer server.
> Usage
> Use this command to identify a peer server as IMS capable allowing the S-CSCF to use SIP signalling inter-working when forwarding calls to non-IMS capable networks.
> lro-selection-profile
> Binds a CSCF last route profile with the peer server.
> Product
> SCM
> Privilege
> Administrator
> Syntax
> lro-selection-profile name profile_name
> no lro-selection-profile
> lro-selection-profile name profile_name
> profile_name must be an existing CSCF last route profile and be from 1 to 79 alpha and/or numeric characters.
> no lro-selection-profile
> Removes CSCF last route profile from the peer server group.
> Usage
> Use this command to identify a CSCF last route profile to use for finding the correct Public Safety Answering Point (PSAP) during emergency calls.
> Example
> The following command assigns a CSCF last route profile named lro1 to the peer server group:
> lro-selection-profile name lro1
> The following command removes a CSCF last route profile from the peer server group:
> no lro-selection-profile
> mode
> Sets the peer server mode to either active or standby. By default, peer servers are in active mode.
> Product
> SCM
> Privilege
> Administrator
> Syntax
> mode { active | standby }
> active
> Defines the mode of the CSCF peer server as active.
> standby
> Defines the mode of the CSCF peer server as standby.
> Usage
> Use this command to set the peer server mode to either active or standby.
> Example
> The following command sets the peer server’s mode to standby:
> mode standby
> monitor-status
> Sets parameters for monitoring the status of peer servers.
> Product
> SCM
> Privilege
> Administrator
> Syntax
> monitor-status { max-response-codes negative max | [ monitor-interval seconds ] [ monitor-message options [ max-forwards max | response-timer seconds ] ] [ monitor-response-timer seconds ] | response-code { positive SIP_response_code | negative SIP_response_code } | timer [ mark-out-of-service seconds ] [ unavailable-monitor-interval seconds ] [ unavailable-notification seconds ] }
> no monitor-status { monitor | response-code [ negative | positive ] [ SIP_response_code ] }
> max-response-codes negative max
> Default: 1
> Specifies the maximum number of negative response codes to receive to mark server unavailable.
> max must be an integer from 1 to 10.
> monitor-interval seconds
> Default: 30
> Specifies the interval that peer server monitoring will occur.
> seconds must be an integer from 1 to 65535.
> monitor-message options [ max-forwards max | response-timer seconds ]
> Specifies that SIP message (OPTIONS) are to be sent periodically after each monitoring interval.
> max-forwards max: Max-forwards in number of hops. max must be an integer from 0 to 70.
> response-timer seconds: Response wait timer in seconds. seconds must be an integer from 1 to 65535.
> monitor-response-timer seconds
> Default: 180
> Specifies the interval that the CSCF will wait for responses from the peer server.
> seconds must be an integer from 1 to 65535.
> response-code { positive SIP_response_code | negative SIP_response_code }
> Specifies the Options Message response codes.
> negative: Negative response codes. SIP_response_code must be an integer from 300 to 699.
> positive: Positive response codes. SIP_response_code must be an integer from 200 to 299.
> timer mark-out-of-service seconds
> Default: 864000
> Timer to mark server out-of-service from unavailable state.
> seconds must be an integer from 0 to 2147483646.
> timer unavailable-monitor-interval seconds
> Periodic monitor interval to be used when server is marked as unavailable.
> seconds must be an integer from 0 to 2147483646.
> timer unavailable-notification seconds
> Default: 180
> Time after which to send notification to operations administrator.
> seconds must be an integer from 0 to 2147483646.
> no monitor-status { monitor | response-code [ negative | positive ] [ SIP_response_code ] }
> Disables peering server status monitoring.
> Usage
> Use this command to set parameters for monitoring the status of a peer server.
> Example
> The following command sets the monitoring interval to three minutes (180 seconds) and the response timer to six minutes (360 seconds):
> monitor-status monitor-interval 180 monitor-response-timer 360
> nw-session-template
> Specifies a session template for sessions terminating from the peer server group.
> Product
> SCM
> Privilege
> Administrator
> Syntax
> nw-session-template name template_name
> no nw-session-template
> name template_name
> template_name must be an existing session template created in the Session Template Configuration Mode.
> no
> Removes session template from the peer server group.
> Usage
> Use this command to identify a session template to use for sessions terminating from the peer server group.
> Example
> The following command identifies a session template named template-25 to use for sessions terminating from the peer server group:
> nw-session-template template-25
> registration
> This command specifies whether the S-CSCF skips third party registration to the Application Server (AS) by a configured time after initial registration.
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> registration skip-count count
> no registration skip-count
> skip-count count
> Number of times to skip third party registration.
> count must be an integer from 0 (default) to 60.
> no registration skip-count
> The S-CSCF does not skip third party registration to the AS by a configured time after initial registration.
> Usage
> Use this command to specify whether the S-CSCF skips third party registration to the Application Server (AS) by a configured time after initial registration. After skipping the configured number of times, the third party register should be sent again to AS to reduce overload on AS.
> Example
> The following command sets the number of times to skip third party registration to 25:
> registration skip-count 25
> tps-rate
> Controls the rate of messages based on Transactions Per Second (TPS) from S-CSCF towards the peer server application server (AS).
> Product
> SCM (S-CSCF)
> Privilege
> Administrator
> Syntax
> tps-rate rate [ exclude Register ]
> no tps-rate
> rate
> TPS from S-CSCF towards the peer server AS.
> rate must be an integer from 1 to 1000.
> exclude Register
> Specifies that for Register method, TPS rate need not be applied.
> no
> TPS rate not applied from S-CSCF towards the peer server AS.
> Usage
> Use this command to control the TPS towards the peer server AS. If TPS rate is exceeded, the incoming requests will be rejected with 500 error response; Retry-After Header specifies the number of seconds before UE should retry.
> Example
> The following command sets the TPS rate towards the AS to 25:
> tps-rate 25

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