Radianta solutions for CUAE

So last night me, the IT Director, CAO and Hospital IT manager met with the folks from RADIANTA. I have to say I was pretty impressed. These guys are partnered with CISCO to provide some great solutions and enable the CISCO VoIP phones to do some neat tricks they should have been able to do from the start, Such as Paging, Call Back and Notification, Call Recording and even Time Card features!

We had a small demo on the suite containing all these core features, it is called "Beacon Office". Now that Radianta are CISCO partners Cisco will be selling this product now directly and tossing a cut to Radianta for development.

Another great thing about this is since they have a true partnership Cisco TAC will actually support this CUAE as if it was their own.


People were waiting for a long time for CISCO to make use of it's Cisco Unified Application Environment but the wait was just too long and Radianta stepped up to supply this solution that worked so great CISCO thought why invent the wheel when these guys are already rolling?!

Since we already have and use Call Manager this software will work and intergrate with everything we have currently without the purchase of anything additional since we already have the setup.


We are going to implement and install this at our hospital very soon I can't wait to get started and I will keep you posted on all the details !!!


For more info:
www.radianta.com

Cisco Call Manager Attendant Problem

The Story:

I got a call while I was sleeping early about 6AM. The IT Director was calling to tell me that the operators at the hospital could not log in to the Cisco Attendant. First thing I thought of was the user name and passwords were wrong that is the most common issue when they can not log in. The Cisco Call Attendant reflects off the users Active Directory account - they use their regular domain account to log in but this time that was NOT the issue... The user names and passwords were correct. Turns out the Attendant service needed to be restarted on the Call Manager server, this time it was not just a password problem...

The Problem:

Users can not log in to the Attendant.

Example: PBX (operators) the users there log in to the Attendant to call and organize calls. If they get errors and can NOT login

The Solution:

1) Account Problem :

Reset password. The logins are based off the AD accounts. Sometimes users might have the wrong password, the account could be locked in Active Directory or they might just be trying the wrong user name.

2) The service has failed:

There is a “Cisco Call Manager Attendant Console Server” service inside the call manager. Sometimes this service can fail and will need to be restarted. Here is how to restart it.

Login to call manager http://XXXXXXXXX

Navigate to “Cisco Unified Serviceability” and click GO (top right of the screen)

From the menu go to Tools and “Control Center –Feature Services”

Select server “192.X.X.X” from the drop down menu and click GO

Under “CTI Services” Select the –Cisco CallManager Attendant Console Server- button, scroll down to the bottom of the left screen and click “RESTART”.

This is a good thing to note because you can also restart other critical services from here as well.. Also when I spoke to cisco they told me secretly it is good practice to restart any services that have been running for over 60 Days. Of course they would not advertise that with their products but thats what they honestly do recommend.