Attendant Console Standard

[ReallyRotten]

I've installed attendant console standard but have no idea how to assign an extension (BIG DUH). I've used my own extension and assigned the attendant console access group but still no luck. I see "the extension you have entered is invalid" error. The documentation doesn't really tell me what to do next. Since this is AC standard, there is no server (so I'm thinking no need for a CTI port). The AC version is 10.6, CUCM is 10.5.2.

Any ideas?

 

[whykap]

Do you have your phone assigned to the application user you created for CUACS?
Does the application user have the proper roles assigned?
Firewall off on your PC?

 

[ReallyRotten]

Yes - my phone shows in the controlled devices under the application user
No firewall
I created an access control group with the application user assigned to the group. The roles assigned to the group: standard axl api access, std CTI allow call park monitoring, std CTI allow calling number modification, std CTI allow control of all devices, std CTI allow reception of SRTP key material, std CTI enabled.

Also assigned to the application user is Standard CCM Super Users.

Do I need a unique extension?

 

[whykap]

have you assigned the phone in the valid device list:

Managing Sign In Devices
Attendants can only sign in to Cisco Unified Atte
ndant Console Standard using a valid Cisco device,
with a device name, extension and line number. For attendants to be able to make calls, the device must
also be associated with th
e Application User/End user configured in the Cisco TSP.
System administrators define which devices are availabl
e for attendants to use; these devices constitute
the
Device List
, which is accessible using
File > Options > Device List
. At start-up and during
execution, the appli
cation checks whether the devices in the
Device List are associated with the
Application User/End User configured in the Cisco TSP.
•
If they are not, they are marked as
invalid
. These have a lighter color in the list, and attendants
cannot make calls using them.
•
If they were previously marked as invalid, but are now associated with the Application/End user,
they are marked as valid, and attendants can make calls using them.
Administrators can either manually add devices to the list, or import them from CSV files.
While importing sign in devices from a CSV file, the
application checks that ea
ch device is associated
with the Application/End User configured in the Cisco TSP. If a device is not associated, it is shown as
invalid in the Device List.
If additional lines are later associated with a sign in device (using Cisco Unified Communications
Manager), they get added to the Device List. After these
changes, attendants will still be able to sign in
using the old extension