[cisco-voip] Attendant Console and CCM 5.1.1

[Jonathan Charles]

It works now... weird... it just started working...

This is bass ackwards... why tell me how to do something since CallManager
3.0 and now you change it?





Jonathan

On 2/24/07, Justin Steinberg <jsteinberg at gmail.com> wrote:
>
> Sounds right.  Is your pilot point registered?  if not, restart AC
> service.
>
> On 2/24/07, Jonathan Charles <jonvoip at gmail.com > wrote:
> >
> > Yep, did both of that... the actual groups are called:
> >
> > Standard CTI Allow Control of All Devices<http://ccmadmin/userGroupEdit.do?key=ee26a45b-e424-468a-a656-22e480e0c19f>
> >
> > and
> >
> >  Standard CTI Allow Call Park Monitoring<http://ccmadmin/userGroupEdit.do?key=47b0de74-db3a-4be9-aa92-47a7921e0f26>
> >
> > Those are the groups I found...
> >
> > and I added the ac and the ACD dude to both...
> >
> >
> >
> > Jonathan
> >
> > On 2/24/07, Justin Steinberg <jsteinberg at gmail.com> wrote:
> > >
> > > You assign CTI and call park via user groups.  Goto user groups and
> > > find CTI master and call park and assign to app user ' AC '.
> > >
> > > Passwords 12345 for both App and ACDeviceAuthenticationUser
> > >
> > > Justin
> > >
> > > On 2/24/07, Jonathan Charles <jonvoip at gmail.com > wrote:
> > > >
> > > > OK, I created the ACDeviceAuthenticationUser user as an App User and
> > > > assigned all the phones and the AC Pilot to them...
> > > >
> > > > I also deleted the AC user as an enduser and made him an App User...
> > > >
> > > > There is still no place (Under APP user) to assign CTI or call park
> > > > retrieval rights...
> > > >
> > > > Still call control is failing...
> > > >
> > > > What am I missing...
> > > >
> > > > On 2/24/07, Justin Steinberg < jsteinberg at gmail.com > wrote:
> > > > >
> > > > > AC with 5.1.1 is a bit different than 4.x
> > > > >
> > > > > Goto system parameters for the AC Server service
> > > > >
> > > > > There are two accounts there.  The AC account and another account,
> > > > > i forgot the name.
> > > > >
> > > > > The AC account needs to be setup as a App User with CTI master
> > > > > rights, call park, etc.  It does not need to be associated with your pilot
> > > > > point or AC IP phones.
> > > > >
> > > > > The other account needs to be an App User and associated with your
> > > > > receptionist's IP phones.
> > > > >
> > > > > I've also had to restart the AC service (they changed name from
> > > > > TCD to AC) when I make alot of pilot point changes.
> > > > >
> > > > > HTH,
> > > > >
> > > > > Justin
> > > > >
> > > > > On 2/24/07, Jonathan Charles < jonvoip at gmail.com> wrote:
> > > > > >
> > > > > > Oh, one thing is says to check is to enable call park retrieval,
> > > > > > there is no such thing in CCM 5 that I can find... CTI app use is enabled,
> > > > > > BTW...
> > > > > >
> > > > > > On 2/24/07, Jonathan Charles <jonvoip at gmail.com> wrote:
> > > > > > >
> > > > > > > So, I set up a hunt group (just one number in it, the customer
> > > > > > > just has one attendant)... created the ac user (I created ac as both an
> > > > > > > end-user and attendant console user), gave the password of 12345... I also
> > > > > > > associated EVERY phone and the AC Pilot to the ac user...
> > > > > > >
> > > > > > > And I can login to AC, but I get the ubiquitous
> > > > > > > "Initialization of Call Control Failed, retrying..."
> > > > > > >
> > > > > > > Yet the troubleshooting for this basically says to check
> > > > > > > everything I listed...
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Jonathan
> > > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > cisco-voip mailing list
> > > > > > cisco-voip at puck.nether.net
> > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070224/4fb7fa50/attachment.html