[cisco-voip] Attendant Console Errors

[pnowicki at neo.rr.com]

A lot of times, I'll also have to stop and restart the TCD service in 
order to get it to kick in...

----- Original Message -----
From: Ryan Ratliff <rratliff at cisco.com>
Date: Sunday, December 18, 2005 8:46 pm
Subject: Re: [cisco-voip] Attendant Console Errors

> Is your hunt pilot an AC or CM controlled pilot?
> The AC pilot is created via Service->Callmanager Attendant Console-
> 
> >Pilot Point.   The CM pilot is done via Route Plan->Route/Hunt- 
> >Hunt Pilot.
> 
> You don't need CTI Super Provider, might as well take it off the 
user.
> 
> What are your hunt group members?  The AC hunt group will either 
> have  
> AC user line numbers or dn/partition combinations.    If it only 
> has  
> AC user line numbers then you'll need to have an AC user with the  
> console up and running.
> 
> -Ryan
> 
> On Dec 16, 2005, at 6:06 PM, Paul Yago wrote:
> 
> Thanks for the response Ryan.
> 
> I have a user named "ac" with the following checked.
> 1) Enable CTI Application Use
> 2) Enable CTI Super Provider
> 3) Call Park
> 
> And the pilot point and 2 hunt group members are all associated with
> "ac". Password and Pin are 12345.
> 
> I'm still getting the fast busy though when calling the pilot 
> point. Any
> other suggestions?
> 
> Thanks,
> Paul
> 
> 
> 
> -----Original Message-----
> From: Ryan Ratliff [mailto:rratliff at cisco.com]
> Sent: Friday, December 16, 2005 12:09 PM
> To: Paul Yago
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Attendant Console Errors
> 
> The AC user is used by Telephony Call Dispatcher to logon to CTI.  It
> does not need to be configured other than be in the directory with
> "CTI Use" and "Call Park Retrieval Allowed" check boxes ticked.  The
> password and PIN should be 12345 and the device associations should
> be any AC hunt pilot and any phone to be controlled by the people
> using the AC desktop client.
> 
> AC does not need to be an Attendant Console user.
> 
> -Ryan
> 
> On Dec 16, 2005, at 2:46 PM, Paul Yago wrote:
> 
> Hello, does anyone with Attendant Console experience know why I'm
> seeing this error (below)?
> 
> 
> 
> I'm trying to configure a hunt group with 2 DNs and 1 pilot point. I
> created an "ac" user as both an Attendant Console User and CCM user,
> with association to both DNs and the Pilot Point. In the
> documentation, it's not clear to me how the "ac" user should be used.
> Does he need to be part of the AC hunt group?
> 
> 
> 
> Any help is very much appreciated.
> 
> Thanks.
> 
> Paul
> 
> 
> 
> 
> 
> 
> 
> 50621 12/16 11:35:22.806 ERROR HuntGroups:
> 
> pkid: 0xAE5672C0728C86458CAE73F87025E57E, name: New_JTAPI, dn: 6500,
> fkDevice: 0x8FCBD68266333C4D98325062886C69DB, fkCSS:
> 0x5563A64BB3195843A5E2A5FBD113AFE6, huntingAlgorithm: 1,
> dbHuntingAlgorithm: 1, owner: 0, active: 2, queueEnabled: false,
> queueSize: 32, holdTime: 0, CMs: CM_LABCM01-
> 
> Lines:
> 
>       DN: 5750, AlwaysRoute: true, Online: true, LineActive: true,
> RoutingCall: false, Waiting: false, LS: Active, Idle Time:
> 1134697714514, RouteUnknown: true
> 
>       DN: 7017, AlwaysRoute: true, Online: true, LineActive: true,
> RoutingCall: false, Waiting: false, LS: Idle, Idle Time:
> 1134697737624, RouteUnknown: true
> 
> HuntGroupsUsers:
> 
> pkid: 0xAF326A961CFAEF419870B74D4BB27478, userid: ac, passwd: *****
> 
> Sessions:
> 
> Active Sessions:
> 
> Deactive Sessions:
> 
> _______________________________________________
> 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
>