> PCC-Service Configuration Mode Commands
> The PCC-Service Configuration Mode is used to link, consolidate and manage the policy logic for the network. It defines the authorization of resources for a subscriber’s data usage under various conditions and policies in the PCC-service.
> Important: This configuration mode is supported from StarOS Release 12.1 onward
> action-set
> This command is used to create a new set of action, action-set, or modify a previously configured action set and enters the PCC-Action-Set Configuration Mode. This command can also be used to delete an existing PCC-Action-Set.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> action-set act_set_name [-noconfirm]
> no action-set act_set_name
> no
> Removes the configured PCC-Action-Set from this PCC-service instance for IPCF configuration.
> act_set_name
> Identifies the name of the PCC-Action-Set which is to be created or modified through this command.
> The act_set_name must be an alphanumerical string from 1 through 63 characters.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Use this command to create/remove/configure an action-set in a PCC-service instance for IPCF Configuration.
> An Action-set indicates the policy and charging as well as event generation related decisions that will get activated when the corresponding Condition-Group is evaluated to TRUE within a subscriber policy/profile.
> A maximum of 512 PCC-Action-Sets can be configured in 1 instance of PCC-Service.
> Entering this command results in the following prompt:
> [context_name]hostname(config-pcc-action-set)
> Important: For more information on PCC-Action-Set configuration, refer PCC-Action-Set Configuration Mode Commands.
> Example
> Following command creates a PCC-action-set named pcc_act1 with in a PCC-service.
> action-set pcc_act1
> Following command removes a pre-configured PCC-action-set named pcc_act1 from a PCC-service.
> no action-set pcc_act1
> charging method
> This command defines the charging method selection parameters in a PCC-service instance for IPCF.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> charging method {both-offline-and-online | offline | online}
> [default | no] charging method
> default
> Sets the charging method to “no” in a PCC-service instance on IPCF node.
> no
> Removes the configured charging method from a PCC-service instance on IPCF node.
> both-offline-and-online
> Default: Disabled.
> Defines that this PCC-service instance is configured for both, online and offline, charging method for IPCF configuration.
> offline
> Default: Disabled.
> Defines that this PCC-service instance is configured only for offline charging method for IPCF configuration.
> online
> Default: Disabled.
> Defines that this PCC-service instance is configured only for online charging method for IPCF configuration.
> Usage
> Use this command to define the charging method selection parameters in a PCC-service instance for IPCF. Charging method used can be online, offline or both.
> Example
> Following command defines the charging method for a PCC-service instance as both, online and offline:
> default charging method
> charging server
> This command defines the charging server parameters in a PCC-service instance for IPCF.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> charging server server_name function {offline | online} {primary | secondary}
> no charging server {all | function {offline | online} {primary | secondary}
> no
> Removes/disables the charging server parameters in a PCC-service instance for IPCF configuration.
> server_name
> Identifies the name of the charging server which is to be configured with these parameters in a PCC-service instance for IPCF configuration.
> The server_name must be an alphanumerical string from 1 through 63 characters.
> offline
> Sets the specific charging server to be used as offline server in a PCC-service instance for IPCF configuration.
> online
> Sets the specific charging server to be used as online server in a PCC-service instance for IPCF configuration.
> primary
> Sets the specific charging server to be used as primary charging server for offline or online charging method in a PCC-service instance for IPCF configuration.
> secondary
> Sets the specific charging server to be used as secondary charging server for offline or online charging method in a PCC-service instance for IPCF configuration.
> all
> This keyword is used with no keyword only. It removes the all configured charging server parameters from a PCC-service instance for IPCF configuration.
> Usage
> Use this command to configured the online or offline charging servers to be used as primary or secondary in a PCC-service instance for IPCF configuration.
> Example
> Following command configures the online charging server named Gx1 as primary for online charging method for a PCC-service instance:
> charging server Gx1 function online primary
> Following command removes the all, online/offline/primary/secondary, type of charging servers from a PCC-service instance:
> no charging server function all
> condition-group
> This command creates a new group of conditions, condition-group, or modify a previously configured condition-group and enters the PCC-Condition-Group Configuration Mode. This command can also be used to delete an existing PCC-Condition-Group.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> condition-group cond_grp_name [-noconfirm]
> no condition-group cond_grp_name
> no
> Removes the configured PCC-condition-group from a PCC-service instance for IPCF configuration.
> cond_grp_name
> Identifies the name of the PCC-condition-group which is to be created or modified through this command.
> The cond_grp_name must be an alphanumerical string from 1 through 63 characters.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Use this command to create/remove/configure a group of condition, condition-group, in a PCC-service instance for IPCF configuration.
> A Condition-group is a collection of conditions that identify a network or state constraint represented as an logical expression. A condition-group may use another condition-group within with the nesting level limited to 3.
> Within a condition-group the conditions and condition-groups can either be linked with an AND or an OR relation. A Condition is built using predefined keywords representing unique service conditions such as user-location, app-service etc.
> A maximum of 1024 PCC-Condition-Groups can be configured in 1 instance of PCC-Service.
> Entering this command results in the following prompt:
> [context_name]hostname(config-pcc-condition-group))#
> The commands configured in this mode are defined in the PCC-Condition-Group Configuration Mode Commands chapter of Command Line Interface Reference.
> Caution: This is a critical configuration. The PCC-Condition Group can not be configured without this configuration. Any change to this configuration would lead to removing or disabling configuration parameters defined here.
> Example
> Following command creates a PCC-condition-group named cond_grp1 with in a PCC-service instance.
> condition-group cond_grp1
> Following command removes a pre-configured PCC-condition-group named cond_grp1 from a PCC-service instance.
> no condition-group cond_grp1
> data-service
> This command creates a new service for data, data-service, or modify a pre-configured data-service and enters the PCC-Data-Service Configuration Mode. This command can also be used to delete an existing PCC-Data-Service.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> data-service data_svc_name [-noconfirm]
> no data-service data_svc_name
> no
> Removes the configured PCC-Data-Service from a PCC-service instance for IPCF configuration.
> data_svc_name
> Identifies the name of the PCC-Data-Service which is to be created or modified through this command.
> The data_svc_name must be an alphanumerical string from 1 through 63 characters.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Use this command to create and configure a PCC-data-service in a PCC-service instance for IPCF configuration.
> A PCC-Data-Service defines the flows for the media data as well as corresponding attributes that are necessary for the charging as well as policy enforcement decisions for the kind of media represented by its Service-Flows.
> A maximum of 256 PCC-Data-Services can be configured in 1 instance of PCC-Service.
> Entering this command results in the following prompt:
> [context_name]hostname(config-pcc-data-service))#
> The commands configured in this mode are defined in the PCC-Data Service Configuration Mode Commands chapter of Command Line Interface Reference.
> Caution: This is a critical configuration. The PCC-Data-service can not be configured without this configuration. Any change to this configuration would lead to removing or disabling configuration parameters defined here.
> Example
> Following command defines a PCC-data-service named pcc_data_svc1 in a PCC-service instance without any confirmation prompt.
> data-service pcc_data_svc1 -noconfirm
> Following command removes a pre-configured PCC-data-service named pcc_data_svc1 from a PCC-service instance without any confirmation prompt.
> no data-service pcc_data_svc1 -noconfirm
> end
> Exits the current configuration mode and returns to the Exec mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Use this command to return to the Exec mode.
> exit
> Exits the current mode and returns to the parent configuration mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Use this command to return to the parent configuration mode.
> map-profile priority
> This command defines the parameter and key priorities to match the profile condition for a subscriber in a PCC-service instance for IPCF configuration.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> [no] map-profile priority map_prio_value apn [apn_name profile-policy name pcc_prof_name]
> [no] map-profile priority map_prio_value profile-policy name pcc_prof_name]
> [no] map-profile priority map_prio_value subscription-attribute name subs_attrib_name [value] subs_attrib_value profile-policy name pcc_prof_name]
> no
> Removes/disables the set priority value of specific profile mapping parameters.
> map_prio_value
> Identifies the priority value of specific profile mapping parameters.
> The map_prio_value must be an integer value from 1 through 1024.
> apn apn_name
> This keywords associates a pre-configured/defined APN name to map with specific profile mapping priority.
> The apn_name specifies the name of the APN configured for subscriber session to which a priority value is set for profile mapping and must be an alphanumerical string from 1 through 63 characters.
> condition-group cond_grp_name
> This keywords associates a pre-configured/defined PCC-Condition-Group configured in PCC-Service Configuration mode to map with specific profile making priority.
> The cond_grp_name is pre-configured PCC-Condition-Group and must be an alphanumerical string from 1 through 63 characters.
> Important: For more information on PCC-Condition-Group configuration, refer condition-group command in this chapter.
> spr-profile-not-found
> This keyword set the condition based on unavailability of subscriber profile on SSC.
> This support is provided to select a pre-configured profile policy pcc_prof_name if subscriber’s SPR profile is not available and to allow operator to have different policies for such Subscribers.
> If operator does not want to map a separate profile but treat such Subscribers differently, then a condition based on this criteria can be configured in PCC-Condition-Group Configuration Mode.
> subscription-attribute name subs_attrib_name
> This keywords associates a pre-configured/defined subscription attributes to map with specific profile making priority.
> The subs_attrib_name specifies the subscription attribute name set/configured for the subscriber to which a priority value is set for profile mapping and must be an alphanumerical string from 1 through 63 characters.
> value subs_attrib_value
> This keywords associates a pre-configured/defined subscription attributes value associated with a subscription attribute name to map with specific profile making priority.
> The subs_attrib_value specifies the subscription attribute value associated with a subscription attribute name set/configured for the subscriber to which a priority value is set for profile mapping and must be an alphanumerical string of 1 through 63 characters.
> profile-policy pcc_prof_name
> This keywords associates a pre-configured/defined PCC-Service-Profile configured in PCC-Service Configuration mode to map with specific profile making priority.
> The pcc_prof_name is pre-configured PCC-Service-Profile and must be an alphanumerical string from 1 through 63 characters.
> Important: For more information on PCC-Service-Profile configuration, refer profile-policy command in this chapter.
> Usage
> Use this command to identify the keys used to match the profile for a subscriber in a PCC-service instance for IPCF configuration.
> The profile map is used when the subscriber session established. It is based on the priority of map and condition matches the corresponding named profile is used for the subscriber session.
> Important: For a subscriber session, only a single profile will match.
> Example
> Following command configures the profile mapping priority to 2 for an APN named apn_ipcf1 with PCC-Service-Profile named pcc_prof1 with in a PCC-service instance.
> map-profile priority 2 apn apn_ipcf1 profile-policy name pcc_profile1
> Following command configures the profile mapping priority to 0 for all sessions with PCC-Service-Profile named pcc_prof2 with in a PCC-service instance.
> map-profile priority 2 profile-policy name pcc_profile2
> monitoring-key
> This command creates a monitoring key and sets the threshold to provide the facility for tracking and dynamic Policy control based on subscriber usage in a PCC-service instance for IPCF configuration.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> monitoring-key {any | mon_key_value grant-size grant_volume
> [no]monitoring-key mon_key_value
> [default] monitoring-key any
> no
> Removes/disables the configured Monitoring Key in IPCF.
> any
> Default: Enabled
> This keywords sets the threshold size for ANY monitoring key to configured grant volume size. IPCF uses the configured grant size while installing a Monitoring Key in PCEF.
> mon_key_value
> This keywords configures the Monitoring Key with a configurable grant volume size. IPCF installs this Monitoring Key in PCEF for usage tracking.
> mon_key_value must be an integer between 1 through 65535.
> grant-size grant_volume
> Default: 1024
> This keywords associates a configurable grant size volume in Kilo Bytes for specific usage Monitor Key on IPCF to install on PCEF.
> The grant_volume specifies the threshold volume in Kilo Bytes for any usage Monitoring Key and must be an integer between 1 through 4294967296.
> Usage
> Use this command to allow operator to configure the threshold size for a monitoring key in a PCC-service instance in IPCF. IPCF uses the configured grant size while installing a Monitoring Key in PCEF. The configured grant size value is configurable to reduce the amount of usage over shooting any of the usage conditions.
> PCEF when instructed by IPCF keeps track of usage per Monitoring Key and also reports the usage when either thresholds reached or requested by IPCF.
> To allow operator to have dynamic Policy control, the IPCF uses objects called as Usage Monitor. Currently an Usage Monitor has single attribute of Volume-limit only. Operator can “associate” different Monitoring Keys to these usage monitors. It can be a Many-To-Many relationship between Usage-Monitor and Monitoring-Key.
> Operator has option to set usage conditions on Usage Monitors instead of Monitoring Keys directly.
> Example
> Following command configures the Monitoring Key 2 for a grant size of 2048 Kilo Bytes with in a PCC-service instance.
> monitoring-key 2 grant-size 2048
> multiple-pcef-per-subscriber
> This command enables the IPCF to support more than one Gx-session for single subscriber session coming from multiple PCEF in a PCC-service instance.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> [no | default] multiple-pcef-per-subscriber
> no
> Default: Disabled
> Removes the multiple Gx session for a single subscriber from a PCC-service instance for IPCF configuration.
> default
> Sets the PCC-service instance to default setting to accept the multiple Gx session for a single subscriber for IPCF configuration.
> Usage
> Use this command to enable multiple Gx session and multiple PCEF support for a single subscriber in a PCC-service instance for IPCF configuration.
> By default this feature is enabled.
> Example
> Following command sets the IPCF to accept multiple Gx sessions from multiple PCEFs for a single subscriber with in a PCC-service instance.
> multiple-pcef-per-subscriber
> profile
> This command creates a new PCC-Service-Profile or modifies a previously configured policy profile and enters the PCC-Service-Profile Configuration Mode. This command can also be used to delete an existing PCC-Service-Profile.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> profile pcc_prof_name [-noconfirm]
> no profile pcc_prof_name
> no
> Removes the configured PCC-Service-Profile from a PCC-service instance for IPCF configuration.
> pcc_prof_name
> Identifies the name of the PCC-Service-Profile which is to be created or modified through this command.
> The pcc_prof_name must be an alphanumerical string from 1 through 63 characters. A maximum of 32 profiles can be configured in a PCC-service instance.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Use this command to create/remove/configure a PCC-Service-Profile for managing the policy requirement and objectives for network specific to a group of subscribers in the network in a PCC-service instance for IPCF configuration.
> A profile manages multiple Condition-Groups and associated Action-Sets pairs in an ordered manner. On internal or external triggers that cause the profile evaluation, the PCC-rules-engine, evaluates the conditions within the Condition-Groups in the specified priority. Corresponding actions performed for Condition-Groups that evaluates to TRUE. Once a TRUE match found the evaluation of Condition-Groups does not continue further.
> A maximum of 32 PCC-Service-Profiles can be configured in 1 instance of PCC-Service.
> Entering this command results in the following prompt:
> [context_name]hostname(config-pcc-profile))#
> The commands configured in this mode are defined in the PCC-Service-Profile Configuration Mode Commands chapter of Command Line Interface Reference.
> Caution: This is a critical configuration. The PCC-Service-Profile can not be configured without this configuration. Any change to this configuration would lead to removing or disabling configuration parameters defined here.
> Example
> Following command creates a PCC-Service-Profile named pcc_prof1 with in a PCC-service instance.
> profile pcc_prof1
> Following command removes a pre-configured PCC-Service-Profile named pcc_prof1 from a PCC-service instance.
> no profile pcc_prof1
> qos-profile
> This command creates a new PCC-QoS-Profile for QoS parameters or modify a pre-configured PCC-QoS-Profile and enters the PCC-QoS-Profile Configuration Mode. This command can also be used to delete an existing PCC-QoS-Profile.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> qos-profile qos_prof_name [-noconfirm]
> no qos-profile qos_prof_name
> no
> Removes the configured PCC-QoS-Profile from a PCC-service instance for IPCF configuration.
> qos_prof_name
> Identifies the name of the PCC-QoS-Profile which is to be created or modified through this command.
> The qos_prof_name must be an alphanumerical string from 1 through 63 characters.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Use this command to create and configure a PCC-QoS profile in a PCC-service instance for IPCF configuration.
> A PCC-QoS-Profile represents a resource requirement identified by means of the corresponding QoS attributes such as:

> • | QoS class identifier

> • | Maximum Requested bandwidth for uplink (UL)

> • | Maximum Requested bandwidth downlink (DL)

> • | Guaranteed bandwidth for uplink (UL)

> • | Guaranteed bandwidth downlink (DL)

> • | Allocation and Retention Priority (ARP)

> A maximum of 256 PCC-QoS-Profiles can be configured in 1 instance of PCC-Service.
> Entering this command results in the following prompt:
> [context_name]hostname(config-pcc-qos-profile))#
> The commands configured in this mode are defined in the PCC-QoS-Profile Configuration Mode Commands chapter of Command Line Interface Reference.
> Caution: This is a critical configuration. The PCC-QoS-Profiles can not be configured without this configuration. Any change to this configuration would lead to removing or disabling configuration parameters defined here.
> Example
> Following command creates a PCC-QoS-Profile named qos_profile1 with in a PCC-service instance.
> qos-profile qos_profile1
> Following command removes a pre-configured PCC-QoS-Profile named qos_profile1 from a PCC-service instance.
> no qos-profile qos_profile1
> spr-failure
> This command defines SSC session failure handling policies in a PCC-service instance on an IPCF node.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> spr-failure after-auth {continue | terminate}
> [default] spr-failure after-auth
> default
> Sets the configured SSC session failure handling parameters and actions to default action of continue with a PCC-service instance for IPCF configuration.
> after-auth {continue | terminate}
> This keyword is used to set the PCC-service to take decision on SSC communication failure after authorization of session.
> Following actions are initiated on SSC session failure after authorization:

> • | continue: IPCF allows session to continue.

> • | terminate: IPCF terminates the session for subscriber.

> Usage
> Use this command to set the PCC-service to take decision on SSC communication failure after authorization of session.
> Example
> Following command sets the session failure handling policy with SSC to terminate the session on failure of communication with SSC after authorization in a PCC-service instance.
> spr-failure after-auth terminate
> ssc-usage-update-policy
> This command provides the configuration to manage the SSC update frequency over Sp interface for usage reports received from PCEF over Gx interface in a PCC-service instance for IPCF configuration.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> [default] ssc-usage-update-policy {always | average-tps tps | on-terminate}
> default
> Sets the PCC-service to configure the SSC update frequency to always over Sp interface for usage reports received from PCEF over Gx interface in a PCC-service instance for IPCF configuration.
> always
> Default: Enabled
> This keyword sets the PCC-service instance to generate SSC usage update every time PCC-service instance received Usage Report from PCEF over Gx interface for IPCF configuration.
> average-tps tps
> Default: Disabled
> This keyword generates the SSC usage update towards the SSC over Sp interface for Usage Reports received by IPCF from PCEF over Gx interface only when average transaction-per-second exceeds the configured threshold tps.
> The tps specifies the average transactions-per-second on IPCF and must be an integer from 1 through 5000.
> on-terminate
> Default: Disabled
> This keyword generates the SSC usage update towards the SSC over Sp interface for Usage Reports received by IPCF from PCEF over Gx interface only when IP-CAN session terminates.
> Usage
> Use this command to configure the PCC-service to manage the SSC update frequency over Sp interface for Usage Reports received from PCEF over Gx interface in a PCC-service instance for IPCF configuration.
> Example
> Following command configures the SSC usage update over Sp interface every time when a usage report is received over Gx interface in a PCC-service instance.
> default ssc-usage-update-policy
> timedef
> This command creates a new Time Definition (TimeDef), or modify a pre-configured Timedef and enters the PCC-TimeDef Configuration Mode. This command can also be used to delete an existing PCC-TimeDef.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> [no] timedef timedef_name [-noconfirm]
> no
> Removes the configured PCC-TimeDef from a PCC-service instance for IPCF configuration.
> timedef_name
> Identifies the name of the PCC-TimeDef which is to be created or modified through this command.
> The timedef_name must be an alphanumerical string from 1 through 127 characters.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Use this command to create and configure a PCC-Time Definition (TimeDef) in a PCC-service instance for IPCF configuration.
> The PCC-TimeDefs can be used to configured date and time for triggering the event for policy related procedures as well.
> Entering this command results in the following prompt:
> [context_name]hostname(config-pcc-timedef))#
> A maximum of 512 PCC-TimeDefs can be configured in 1 instance of PCC-Service.
> The commands configured in this mode are defined in the PCC-TimeDef Configuration Mode Commands chapter of Command Line Interface Reference.
> Caution: This is a critical configuration. The PCC-TimeDefs can not be configured without this configuration. Any change to this configuration would lead to removing or disabling configuration parameters defined here.
> Example
> Following command creates a PCC-TimeDef named time_day1 with in a PCC-service instance.
> timedef time_day1
> Following command removes a pre-configured PCC-TimeDef named time_day1 from a PCC-service instance.
> no timedef time_day1
> timeout idle
> Configures the idle timeout duration for subscriber session and also sets the action to be taken by system on expiry of timeout duration .
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> timeout idle idle_dur [action reauthorize]
> no timeout idle
> default timeout idle
> no
> Removes the configured idle timeout value and action set in in PCC Service instance.
> default
> Sets the the idle timeout duration to the default value of ‘0’ which disables the idle timeout configuration in PCC Service instance.
> idle_dur
> Default: 0
> Designates the maximum duration of the session, in seconds, after the expiry of which the system considers the session as dormant or idle and invokes the reauthorization of session action, if configured.
> idle_dur must be a value in the range from 0 through 4294967295.
> The special value 0 disables the timeout specified.
> action reauthorize
> This optional keyword sets the system to trigger the reauthorization of session after expiry of the timeout duration configured through idle_dur value.
> Usage
> Use this command to set the idle time duration for subscriber session to determine the dormant session.
> This is configuration sets the time in seconds for idle session (sessions with no activity/signaling). On expiry of this timeout duration action of reauthorization of session shall be triggered. In case of reauthorization request failure, session termination shall be triggered.
> Refer to the timeout long-duration command in this chapter for additional information.
> Important: Reduce the timeout duration to free session resources faster for use by new requests.
> Example
> Following command sets the idle timeout duration to 450 seconds.
> timeout idle 450
> timeout setup
> Configures the timeout duration for IPCF setup session.
> Product
> IPCF
> Privilege
> Security Administrator, Administrator
> Syntax
> timeout setup setup_dur
> no timeout setup
> default timeout setup
> no
> Removes the configured setup timeout value and action set in in PCC Service instance.
> default
> Sets the the setup timeout duration to the default value of 60. The special value of ‘0’ disables the setup timeout configuration in PCC Service instance.
> setup_dur
> Default: 60
> Designates the maximum duration for the IPCF session setup, in seconds, after the expiry of which the system considers the IPCF session setup as failure and terminates the setup process.
> setup_dur must be a value in the range from 0 through 120.
> The special value 0 disables the setup timeout specified.
> Usage
> Use this command to set the time duration for IPCF session setup to determine the failure of IPCF setup process.
> Example
> Following command sets the IPCF session timeout duration to 30 seconds.
> timeout setup 30

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