Jump to: navigation, search

GVP MCP:sip:timer-ci proceeding

m (1 revision imported)
Line 1: Line 1:
−
----
+
{{PubOption
−
__NOTOC__
 
−
 
 
−
<!-- ==================== -->
 
−
<!-- DO NOT EDIT -->
 
−
=Published=
 
−
{{Optionstmp
 
−
|internalformid=1 (DO NOT EDIT THIS VALUE)
 
−
|fromxml=true
 
−
|docstatus=Published
 
−
|fromxml=true
 
−
|parameter=timer.ci_proceeding
 
−
|urlparameter=timer-ci_proceeding
 
−
|displayname=Client Invite Proceeding Timer
 
 
|hidden=false
 
|hidden=false
 
|default=120000
 
|default=120000
Line 18: Line 5:
 
|takeseffect=At start/restart
 
|takeseffect=At start/restart
 
|shortdesc=Defines the client INVITE proceeding timer in milliseconds, default value is 120000. The timer starts after a 1xx response is received for a client INVITE. If a final response is not received before the timer expires, the SIP session and dialog will be destroyed without further notice to the UAS. Note that the CI proceeding timer should be configured to be greater than the connect timeout of the outbound call (depending on how the outbound call is initiated, the connect timeout can be specified in the transfer tag, or in the remdial command). Otherwise, the Client Invite Proceeding Timer will be triggered before the connect timeout occurs, which overrides the connect timeout as a result.
 
|shortdesc=Defines the client INVITE proceeding timer in milliseconds, default value is 120000. The timer starts after a 1xx response is received for a client INVITE. If a final response is not received before the timer expires, the SIP session and dialog will be destroyed without further notice to the UAS. Note that the CI proceeding timer should be configured to be greater than the connect timeout of the outbound call (depending on how the outbound call is initiated, the connect timeout can be specified in the transfer tag, or in the remdial command). Otherwise, the Client Invite Proceeding Timer will be triggered before the connect timeout occurs, which overrides the connect timeout as a result.
 +
}}
 +
{{DraftOption}}
 +
{{PubExtended}}
 +
{{DraftExtended}}
 +
{{OptionCreate
 +
|component=GVP_MCP
 +
|compshort=GVP_MCP
 +
|prodshort=GVP
 +
|configobject=Application
 
|section=sip
 
|section=sip
−
|urlsection=sip
+
|parameter=timer.ci_proceeding
−
|groupid=grpSIP
 
−
|groupname=SIP
 
−
|format=numeric
 
−
|prodshort=GVP
 
−
|component=GVP_MCP
 
−
|compshort=MediaControlPlatform
 
−
}}
 
−
[[Category:GVP_MCP_options]]
 
−
 
 
−
<!-- DO NOT EDIT -->
 
−
<!-- ==================== -->
 
−
 
 
−
==Extended Description==
 
−
 
 
−
{{Extended
 
−
|internalformid=1 (DO NOT EDIT THIS VALUE)
 
−
|docstatus=
 
−
|mandatory=
 
−
|introduced=
 
−
|modified=
 
−
|discontinued=
 
−
|feature=
 
−
|relatedoptions=
 
−
|relatedlinks=
 
−
|configobject=
 
−
|moredesc=
 
 
}}
 
}}
  
−
=Draft=
+
[[Category:GVP_MCP_options]]
−
 
 
−
{{Optionstmp
 
−
|internalformid=2 (DO NOT EDIT THIS VALUE)
 
−
|docstatus=
 
−
|parameter=
 
−
|displayname=
 
−
|hidden=
 
−
|default=
 
−
|valid=
 
−
|takeseffect=
 
−
|shortdesc=
 
−
|section=
 
−
|groupid=
 
−
|groupname=
 
−
|format=
 
−
|prodshort=
 
−
}}
 
−
 
 
−
==Extended Description==
 
−
 
 
−
{{Extended
 
−
|internalformid=2 (DO NOT EDIT THIS VALUE)
 
−
|docstatus=
 
−
|mandatory=
 
−
|introduced=
 
−
|modified=
 
−
|discontinued=
 
−
|feature=
 
−
|relatedoptions=
 
−
|relatedlinks=
 
−
|configobject=
 
−
|moredesc=
 
−
}}
 

Revision as of 03:19, October 31, 2016


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

timer.ci_proceeding

Default Value: 120000
Valid Values: sip.timer.ci_proceeding must be an integer that is greater than 0 and less than or equal to the maximum integer as defined by the Genesys Administrator Help.
Changes Take Effect: At start/restart


Defines the client INVITE proceeding timer in milliseconds, default value is 120000. The timer starts after a 1xx response is received for a client INVITE. If a final response is not received before the timer expires, the SIP session and dialog will be destroyed without further notice to the UAS. Note that the CI proceeding timer should be configured to be greater than the connect timeout of the outbound call (depending on how the outbound call is initiated, the connect timeout can be specified in the transfer tag, or in the remdial command). Otherwise, the Client Invite Proceeding Timer will be triggered before the connect timeout occurs, which overrides the connect timeout as a result.

Draft Option

No draft option

Comments or questions about this documentation? Contact us for support!