[cisco-voip] Unity Connection Call handlers transerring to ahunt group

Wed Nov 11 12:11:34 EST 2009

Look at your hunt pilot # options for Forward Hunt No Answer and Forward
Hunt Busy, it could be directing back to Unity.

I think by selecting supervised transfer it will add the second or 2 of
music while it figures out if it can transfer.

I don't use that option and set it on the Hunt Pilot (FHNA and FHB) to
determine where to send the call on those conditions.

The main greeting should use attempt to transfer to TransferToSales call
handler under caller input.

TransferToSales call handler should use Call Transfer options, no caller
input setting defined.

John

From: O'Brien, Neil [mailto:nobrien at datapac.com] 
Sent: Wednesday, November 11, 2009 11:51 AM
To: Truelove_John; Pat Hayes
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Call handlers transerring to
ahunt group

Hi John,

Ok that worked, however I needed to set the "attempt transfer" instead
of "direct to greetings" for the handler handing off to it.  I'm still
not sure it's 100% though.  I tried to do a supervised transfer in case
the extn/huntgroup was busy and set it to put the user on hold.  I hear
hold music for less than a second then I'm prompted that the extn is
unavailable and asked to leave a message.  I've no idea where this
message is going or where it's set to take a message because everything
I've looked though is not set to take a message.

Any idea?

Thanks again,

Neil

From: Truelove_John [mailto:JTruelove at aetinc.com] 
Sent: 11 November 2009 16:32
To: O'Brien, Neil; Pat Hayes
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Call handlers transerring to
ahunt group

Try setting the TransferToSales call handler like this:

Standard-

Yes, ring this extension 3586  (if your extensions are define as
xxx3586, you should put xxx3586)

Check Do not play "Wait..."

Release to switch

Then go in and make the others transfer rules the same (Alternate and
Closed) and enable them.

If I remember correctly, I had some of the same weirdness until I set
all transfer rules the same and enabled them.

John

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of O'Brien, Neil
Sent: Wednesday, November 11, 2009 11:11 AM
To: Pat Hayes
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unity Connection Call handlers transerring to
ahunt group

Hi Guys,

OK So I'm getting somewhere with this, I just don't know where.
Confused.com!

The way I understand it is:

1)  Define my Originating call handler - "Thank you for calling....."

2)  Define the second call handler that the originating one hands off to
- "Press 1 for sales......."

3)  I press one for sales and what I want to happen is that it goes to
the sales hunt group 3586.

4)  So I define another handler called TransferToSales and send the
caller input for "1" in the second handler to go to the TransferToSales
handler.  I set the transfer options in this handler, under the standard
option to transfer to extn 3586.  The way I have interpreted the
transfer options is that if it's set to greeting, it will transfer to
the greeting of that handler.  If it's set to extension, it will skip
the greetings associated with that handler and immediately try the
configured extn.

I'm getting a lot of different conflicting results for the
TransferToSales handler in that it won't transfer directly to the extn.
Changing the settings in the standard greetings for this handler seems
to affect what happens, so my theory of it skipping the handler
greetings when the transfer options are set to extension must be wrong??

An absolute mess of an email but I hope you can follow!!

Thanks again for your help,

Neil

-----Original Message-----
From: pat at wcyv.com [mailto:pat at wcyv.com] On Behalf Of Pat Hayes
Sent: 11 November 2009 15:17
To: O'Brien, Neil
Cc: lelio at uoguelph.ca; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unity Connection Call handlers transerring to
a hunt group

That sounds like the transfer is going to the system greeting.

Sometimes it helps to watch the call flow through the (remote) port

status monitor, to spot where things go wrong.

A couple of reasons this would happen:

1. On the originating call handler where you configured the caller

input, you selected 'go directly to greeting' instead of 'attempt

transfer'

2. On the dummy call handler, make sure you are configuring the

correct transfer rule - if active, the alternate and closed rules will

take priority over the standard. Whichever rule is active, ensure it

is configured to send to Extension and not Greeting.

3. You configured UC correctly and the transfer is actually attempted

but fails due to CSS problem on CUCM - check the CSS of ports (skinny)

or the Rerouting CSS (SIP) and ensure it includes the partition of the

DN you are trying to transfer to.

Finally, an alternate configuration on UC 7.1(2)ish and later is,

under caller input on the originating call handler, select call action

"Transfer to alternate contact number" and enter the extension you

wish to transfer to. This eliminates the need for the dummy call

handler/user, but can only be done as a release/blind transfer (no

supervised option).

On Wed, Nov 11, 2009 at 8:50 AM, O'Brien, Neil <nobrien at datapac.com>
wrote:

> Hi Lelio,

> 

> 

> 

> It doesn't appear to work.  I've set up a new CH and linked it into
the

> AutoAttendant, and set it's transfer options to transfer to an
extension

> instead of the greeting however each time I do this it just tells me
the

> "extension is not available" regardless of whether it's the hunt group
or an

> extension that definitely works (my extn#). But it does work if I use
the

> Caller input and transfer to a "User with mailbox" extn.

> 

> 

> 

> Any ideas off the top of your head - I'll continue to play around with
it,

> although it doesn't make much sense to me.

> 

> 

> 

> Thanks for your help,

> 

> Neil

> 

> 

> 

> 

> 

> 

> 

> From: lelio at uoguelph.ca [mailto:lelio at uoguelph.ca]

> Sent: 11 November 2009 10:39

> To: O'Brien, Neil

> Cc: cisco-voip at puck.nether.net

> Subject: Re: [cisco-voip] Unity Connection Call handlers transerring
to a

> hunt group

> 

> 

> 

> You'll need to create another call handler first, say

> "TransferTo-ExampleHG-CH", and configure that call handler to transfer
to

> the appropriate DN. Then from within any other call handler, you can

> reference it. This has advantages, you only have to change the DN in
one

> spot if changes are ever required.

> 

> Lelio Fulgenzi, Senior Analyst

> 

> Computing & Communications

> 

> University of Guelph

> 

> 519-824-4120 x56354

> 

> ...sent from my iPod - please pardon my fat fingers ;)

> 

> [XKJ2000]

> 

> On 2009-11-11, at 5:06 AM, "O'Brien, Neil" <nobrien at datapac.com>
wrote:

> 

> Hi there,

> 

> 

> 

> I'm setting up some auto attendants for a customer and I'm having
trouble

> with what I thought  was the easiest part.  Each handler option needs
to

> transfer out of unity to a CallManager hunt group.  However, the only

> options I appear to have are to transfer to a "User with a Mailbox".
I

> think unless I create a mailbox for the huntgroup extn# it won't give
me the

> option.

> 

> 

> 

> I don't understand what the "Transfer Options" are within the call
handler

> or if I need to use that.  The transferring to hunt groups is
controlled by

> the caller input options.

> 

> 

> 

> I simply want to transfer out to a hunt group.

> 

> 

> 

> Thanks in advance,

> 

> 

> 

> Neil

> 

> 

> 

> _______________________________________________

> cisco-voip mailing list

> cisco-voip at puck.nether.net

> https://puck.nether.net/mailman/listinfo/cisco-voip

> 

> _______________________________________________

> cisco-voip mailing list

> cisco-voip at puck.nether.net

> https://puck.nether.net/mailman/listinfo/cisco-voip

> 

> 

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091111/41c4adc4/attachment.html>