[cisco-voip] CCM 4.1(3)sr2 - Unity 4.0(4)sr1 with es58 and Attendant Console problems

[pnowicki at neo.rr.com]

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

----- Original Message -----
From: Wes Sisk <wsisk at 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 at netxar.com>
Cc: cisco-voip at puck.nether.net

> Sounds like CSCsc79529, CSCsc50139 to me.  Fixed in CM 4.1(3)sr3
> 
> /Wes
> 
> Jose Mujica wrote:
> > Hi.
> >
> > I have a client that has an Auto Attendant in Unity when a 
> client press 0 for
> > operator we transfer the call to a Pilot Point that is handle by 
> AC and a user
> > 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 transfer
> > [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 [queue]
> > 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 the
> > 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
> >
> > _______________________________________________
> > 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
>