FAQ
Beacon Office FAQ
Q: Does Beacon Office work with Communications Manager 4.x?
No. Beacon Office is only supported on Cisco Unified Communications Manager 5 and above. We are in process of creating a version for Communications Manager 4.2, but it will be a separate product.
Q: Why does my call go into a personal queue when it was only intended to be recorded?
A: There is an inherent conflict between the recording application and Personal Queue. This stems from the fact that both of these apps trigger on calls placed from many phones, some of which may even want to use both applications concurrently. The way to get these two to play nice is to create an additional route point for the recording application. This is entered into both the CUAE and Communications Manager. Then, on Communications Manager only, create a line on that route point which represents all possible dialed numbers (”*”). Assign that route point to a new partition, such as “Recording”. Then add a new calling search space, such as “Recording CSS”, which only contains the Recording partition. All phones wishing to participate in recording should then be assigned the “Recording CSS” calling search space. Now, whatever the phones dial will result in a call to the route point which is registered by CUAE. This call triggers the Recording application which in turn makes a call out to that same number. Because the outbound call is H.323, it routes normally to the intended destination.
Q: I ran the Beacon Office installer, but none of the applications seem to work.
A: After installation, the applications may show as disabled in the CUAE. You may have to manually enable each of them.
Q: After locking my phone, some line appearances are still able to place calls.
A: Phone lock will not work completely if individual phone lines are configured with a calling search space. In order for phone lock to work most effectively, the phone device should have a calling search space and all the lines will default to that if left unconfigured.
Q: I cannot unlock my phone after locking it.
A: Phone Lock does not unlock the phone properly if no calling search space is defined for the phone. This is considered an edge scenario since best practice dictates that all phones should be assigned a CSS.
Q: Web Extension Mobility fails to log me in and I know the credentials are correct.
A: The Communications Manager application interface for Extension Mobility is case-sensitive. Both the administrative and user credentials are required for the application to work. For example, if the administrator user is entered in Communications Manager as “administrator” but is in Beacon Office as “Administrator”, the extension mobility request will fail even though “Administrator” may work successfully to log into the Communications Manager Administrative console.
Q: Why doesn’t Personal Queue show a call which was transferred to me by another person or auto-attendant?
This is a known issue which is currently being worked with Cisco. Check back here for a link to the patch when it is available.
Q: Can I use the Call Recording app for incoming calls or record randomly or force all calls to be recorded, etc?
The Call Recording application is only intended to be used to record outbound calls. The person making the call makes the decision whether or not to record the call. It does not provide any additional recording features.
Q: I’m happy with how the Call Recording feature works, but can I deploy it to my entire organization of 5,000 phones?
You could, but it is not recommended as the cost in Cisco gear would be enormous. The Call Recording application uses two RTP ports on the media engine for each call from each enabled phone. As such, a fully-licensed CUAE media engine will only support 120 Call Recording users. Increasing beyond that number would require an additional physical media engine.
Q: Isn’t there any other way to do call recording without using so many resources?
Yes there is, but you must have Communications Manager 6.x and TNP phones (i.e. the model number ends in “1″ or “5″). If you meet these requirements and would like to investigate a more scalable call recording solution, please contact Radianta at sales@radianta.com.
