Dial Plan Enhancements including support for Feature Server Dial Plan

[Iteration 88. In review]

FDS: https://intranet.genesys.com/display/RDSIPS/Dial+plan+for+routed+calls+FDS

This enhancement lets you control how SIP Server applies the dial plan to the destination of TRouteCall and/or to multi-site (ISCC) calls that are routed through an External Routing Point.

By configuring the rp-use-dial-plan option, the default behavior of the dial plan can be changed to any one of the following:

• SIP Server does not apply any dial plan.
• SIP Server applies only the digit translation to a dial plan target.
• SIP Server applies the digit translation and forwarding rules to a dial plan target.

The rp-use-dial-plan option applies to both SIP Server and SIP Feature Server dial plans. If the UseDialPlan key-value pair is present in AttributeExtensions of TRouteCall, then it takes priority over the rp-use-dial-plan option.

The enable-iscc-dial-plan option enables SIP Server to apply the dial plan to the target destination when a call is routed from an External Routing Point to a DN at the destination site.

Feature Server Dial Plan Advantages

In general, the Feature Server dial plan offers several advantages:

• User-based calling preferences for Call Waiting and Call Forwarding (including Find-Me-Follow-Me)
• Flexible rules for choosing a trunk for outgoing calls
• Better support for deployments where voicemail mailboxes are assigned to users (not DNs)

SIP Server Dial Plan Advantages

The SIP Server dial plan offers these advantages:

• Rich set of options for customizing dial plan rules, such as “onbusy”
• Does not require SIP Feature Server (smaller footprint, less complexity)
• Can be used jointly with the Feature Server dial plan for some functionality (take it out or leave it?)

Feature Configuration

Using Feature Server Dial Plan

1. Configure the SIP Feature Server dial plan as described in the SIP Feature Server Administration Guide.
2. Configure SIP Server as described in the SIP Feature Server Deployment Guide.
3. If required, configure the following options in the SIP Server Application object, on the Options > TServer tab:
   • rp-use-dial-plan—Set this option to a value suitable for your environment.
   • enable-iscc-dial-plan—Set this option to true to enable SIP Server to apply the dial plan to multi-site (ISCC) calls that are routed through an External Routing Point.
4. (Optional) In a routing strategy, set the UseDialPlan key extension in TRouteCall. The key extension setting takes priority over configuration options.

Using SIP Server Dial Plan

1. Configure the Dial Plan feature as described in the Framework 8.1 SIP Server Deployment Guide.
2. If required, configure the following options in the SIP Server Application object, on the Options > TServer tab:
   • rp-use-dial-plan—Set this option to a value suitable for your environment.
   • enable-iscc-dial-plan—Set this option to true to enable SIP Server to apply the dial plan to multi-site (ISCC) calls that are routed through an External Routing Point.
3. (Optional) In a routing strategy, set the UseDialPlan key extension in TRouteCall. The key extension setting takes priority over configuration options.

Configuration Options

rp-use-dial-plan

Section: [TServer], Application level
Default Value: default
Valid Values: default, full, partial, false
Changes Take Effect: Immediately

Specifies how SIP Server applies the dial plan:

• default—For a SIP Server dial plan, the same as the false value. For a Feature Server dial plan, the same as the partial value.
• full—The dial plan is applied to the destination of TRouteCall, including the digit translation and forwarding rules.
• partial—Valid for both SIP Server and SIP Feature Server dial plans. Only the digit translation is applied to a dial-plan target. Forwarding rules, such as forwarding on no answer (ontimeout), forwarding on busy (onbusy), forwarding on DND (ondnd), forwarding on no response (onunreach), and forwarding on not SIP registered (onnotreg) are not applied.
• false—No dial plan is applied to the destination of TRouteCall.

Note: If the SIP Server dial plan is used, SIP Server selects the dial plan assigned to the caller instead of the dial plan assigned to the Routing Point. This is the dial plan configured for the DN/Agent Login of the DN for internal calls, or the Trunk DN for inbound calls, or the Application-level option if no DN/Agent-Login-level dial plan is configured.

enable-iscc-dial-plan

Section: [TServer], Application level
Default Value: true
Valid Values: true, false
Changes Take Effect: At the next call

Specifies whether SIP Server applies the dial plan to the agent destination of multi-site (ISCC) calls that are routed through an External Routing Point (cast-type=route-notoken), as follows:

• If set to true, the dial plan (full, including the digit translation and forwarding rules) is applied.
• If set to false, the dial plan is not applied.

This option must be configured on the remote (destination) site. SIP Server applies the dial plan when a call is routed from an External Routing Point to a DN at the destination site.

Note: SIP Server will still apply the dial plan to the External Routing Point destination of multi-site (ISCC) calls, and this will take priority over the agent DN destination dial-plan rule regardless of the setting of enable-iscc-dial-plan.

AttributeExtensions

Key: UseDialPlan
Type: String
Values: full, partial, false
Request: TRouteCall

Specifies how SIP Server applies the dial plan:

• full—The dial plan is applied to the destination of TRouteCall, including the digit translation and forwarding rules.
• partial—Valid for both SIP Server and SIP Feature Server dial plans. Only the digit translation is applied to a dial-plan target. Forwarding rules, such as forwarding on no answer (ontimeout), forwarding on busy (onbusy), forwarding on DND (ondnd), forwarding on no response (onunreach), and forwarding on not SIP registered (onnotreg) are not applied.
• false—No dial plan is applied to the destination of TRouteCall.