Revision as of 00:33, December 29, 2015 by Sschlich (talk | contribs) (Feature Limitations)
Jump to: navigation, search

No-Answer Supervision: After Routing Timeout Action

[Approved by Nina. Iteration 76]

FDS: https://intranet.genesys.com/display/RDSIPS/%5BFDS%5D+After+routing+timeout+action


Starting with SIP Server release 8.1.102.01, you can define SIP Server's default action for setting the state of an agent who was not able to answer the routed call if after the after-routing-timeout expires. Enable this feature with the new configuration option, after-routing-timeout-action or the AFTER_ROUTING_TIMEOUT_ACTION key in AttributeExtensions of TRouteCall enables this feature.

Use the agent-no-answer-timeout option with the corresponding action specified by the agent-no-answer-action option, is used to control direct calls to an agent.

Important
Enable this behavior with the after-routing-timeout-action feature:
Using No-Answer Supervision when the divert-on-ringing configuration option is set to false does not require the value of no-answer timeout options to be smaller than the value of the after-routing-timeout option. The value of no-answer timeout options can be bigger than the value of the after-routing-timeout option.

Feature Configuration

To enable the feature, either configure the after-routing-timeout-action option at the SIP Server Application level, or set (in a routing strategy) the AFTER_ROUTING_TIMEOUT_ACTION key extension in TRouteCall must be set in a routing strategy. The key extension setting takes priority.

after-routing-timeout-action

Default Value: none
Valid Values:

  • none—SIP Server takes no action.
  • notready—If an agent is logged in to a routing destination that had not answered the call, SIP Server sets this agent to NotReady state.
  • logout—If an agent is logged in to a routing destination that had not answered the call, SIP Server logs this agent out.

Changes Take Effect: For the next call

Defines SIP Server's default action if the after-routing-timeout expires. If after-routing-timeout is disabled (set to 0), then SIP Server ignores the after-routing-timeout-action value is ignored.

When you set this option is set to a valid non-default value, it takes priority over the agent-no-answer-action and no-answer-action parameters, which are not applied to an agent logged in to a routing destination if after-routing-timeout expires or is in progress.

When you set this option is set to a valid non-default value, it takes priority over the agent-no-answer-action and no-answer-action parameters, which are not applied to an agent logged in to a routing destination if the after-routing-timeout expires. In addition, neither of the following parameters are applied if the after-routing-timeout is in progress: agent-no-answer-overflow, no-answer-overflow, or extn-no-answer-overflow.


after-routing-timeout

Default Value: 10
Valid Values: Any integer
Changes Take Effect: For the next call

Specifies the length of time (in seconds) that SIP Server waits before diverting the call from the Routing Point DN to the destination DN after TRouteCall was processed. When the call is not diverted before the specified value, the EventError message is issued. It will contain the Reference ID of the TRouteCall request.
Set the value of the option to 0 (zero) to disable this functionality.

AttributeExtensions

Key: AFTER_ROUTING_TIMEOUT_ACTION
Type: String
Values:

  • none—SIP Server takes no action.
  • notready—If an agent is logged in to a routing destination that had not answered the call, SIP Server sets this agent to NotReady state.
  • logoutIf When an agent is logged in to a routing destination that had does not answered the call, SIP Server logs this agent out.

Requests: TRouteCall

If set, the value of this key overrides any value set in the after-routing-timeout-action configuration option for the current call.

Feature Limitations

  • After routing timeout action SIP Server does not support AFTER_ROUTING_TIMEOUT_ACTION at destinations where there are no agents logged in.
  • After routing timeout action SIP Server does not support AFTER_ROUTING_TIMEOUT_ACTION for multi-site call routing.
  • After routing timeout action SIP Server does not support AFTER_ROUTING_TIMEOUT_ACTION for Shared Call Appearance or Hunt Groups.
  • When SIP Server is operating in Cluster mode and when a DN specified by the no-response-dn option...[I am not sure how to revise this and what is required to include...]
  • In case of a switchover, the after-routing-timeout timer is restarted at the new primary SIP Server.
Comments or questions about this documentation? Contact us for support!