Announcement for Hunt Pilot with CUC

[b.winter]

Symptoms

This is article describes a possible solution, the play a customized greeting, before the call is routed to a hunt pilot.
Here, Unity Connection is used as the entity, to play the greeting.

A lot of my customers have this simple solution, which is sufficient enough for them and which is also a very frequent question in the forum.

Some assumptions to start with:

• Incoming calls are arriving via a SIP Trunk, let's call it "GW-Trunk".
  The trunk has the incoming CSS "Incoming-GW"
• A SIP Trunk is used, to connect CUCM and CUC, let's call it "Unity-Trunk"
• All directory numbers are placed in the Partition "Internal"
• There is a special Partition for numbers, which shouldn't be called from external "Internal-No-DID"
• There is a special Partition for numbers, which are directly routed to CUC "Internal-To-CUC"

Solution

1) The CSS "Incoming-GW" of the "GW-Trunk" has the partition "Internal" and "Internal-To-CUC" assigned.

2) Create a route pattern in partition "Internal-To-CUC" for the number \+4920001000 and point it via the "Unity-Trunk" to Unity.

3) Configure a call handler "CH-1000" without any extension (we don't need an extension).

4) Configure a direct routing rule with "Dialed number equals +4920001000" and point it to the call handler "CH-1000", going directly to the greetings.

5) In the standard greeting of the call handler "CH-1000", upload the recording.
The after-greeting action refers to itself, but now to attempt transfer.

6) The transfer rule of the call handler "CH-1000" routes to the number +4920001000.
This number shouldn't be assigned to any User, call handler, ... in Unity Connection.

7) The CSS "Incoming-CUC" of the "Unity-Trunk" has the partitions "Internal" and "Internal-No-DID".
=> Assign the CSS in the Trunk to the "Calling Search Space", "Rerouting Calling Search Space" and "Out-Of-Dialog Refer Calling Search Space" in the SIP Trunk config page.

Create a hunt Pilot with the number \+4920001000 in the partition "Internal-No-DID".

So, when a call comes in via the GW-Trunk, it sees +4920001000 only in Partition "Internal-To-CUC".
The corresponding route pattern sends the call to Unity.
In Unity, the direct routing rule routes the call to the call handler's greeting.
After the greeting, the transfer rule routes the call back to CUCM.
The Unity-Trunk only sees the number +4920001000 in the partition "Internal-No-DID" and routes the call to the hunt pilot.

Add tags

Call Handler - Standard Greeting Settings:

Call Handler - Standard Transfer Rule Settings:

Direct Routing Rule Settings:

 Hope, this helps.

[Maren Mahoney]

I'm curious to know what you feel the benefit would be of this method over configuring the Hunt Pilot with Native Call Queuing with an announcement?

Maren