Hi.

I have a client that has an Auto Attendant in Unity when a client press 0 fo
r
operator we transfer the call to a Pilot Point that is handle by AC and a us
er
logs on the Attendant Console application and received the calls without any
problem.

Now we enable queuing for that particular pilot point. Now when unity transf
er
[release to switch] the call to the Pilot Point if the operator is idle 
she
can received the calls but if she is busy the caller is put on hold [que
ue]
and it remains on hold forever even if the operator is idle again. The call
doesn't get to the operator if is put on queue first.

But If I call directly to the pilot point from any other phone CCM put the
caller on hold and when the operator is available it transfer the call to th
e
operator as it should do. Because of that I'm thinking that my problem is
related with the Unity transfer.

I haven't capture ccm traces for this but I want to know if someone has any 
idea.

Thanks in advanced,
-Jose

[ Post a follow-up to this message ]

We had an issue similar to this. We upgraded to sr3a and it did fix
our issues..

----- Original Message -----
From: Wes Sisk <wsisk@cisco.com>
Date: Wednesday, April 26, 2006 11:07 am
Subject: Re: [cisco-voip] CCM 4.1(3)sr2 - Unity 4.0(4)sr1 with es58
and Attendant Console problems
To: Jose Mujica <jose.mujica@netxar.com>
Cc: cisco-voip@puck.nether.net

> Sounds like CSCsc79529, CSCsc50139 to me.  Fixed in CM 4.1(3)sr3
>
> /Wes
>
> Jose Mujica wrote: 
> client press 0 for 
> AC and a user 
> without any 
> unity transfer 
> is idle she 
> hold [queue] 
> again. The call 
> CCM put the 
> the call to the 
> problem is 
> someone has any idea. 
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]