Forums
« Back to Installation

desk phone control mode

Combination View Flat View Tree View
Threads [ Previous | Next ]
desk phone control mode
Answer
11/22/12 2:00 PM
Hi,
 

<!--[if !supportLists]-->1.      
<!---->Is the server-side
component (node.csf) required for desk phone control or would the C++ native
plugin be sufficient for registering to CUCM and making calls to pre-programmed
DNs?
<!--[if !supportLists]-->2.      
<!---->Is phone device
configuration download optional when Jabber SDK is deployed with an external
Cisco 6921 IP phone (desk phone control)?
<!--[if !supportLists]-->3.      
<!---->Is the CSF device on
CUCM permanently registered while the browser session is open from the Jabber
SDK client? Or does CUCM unregister the CSF after a call is completed or some
timer expires?
<!--[if !supportLists]-->4.      
<!---->Can the same login
credentials be used from multiple Jabber SDK clients (ECP<yourusername>)
in desk phone control mode?
<!--[if !supportLists]-->5.      
<!---->Can you send me the
steps of a sample Jabber SDK registration and call/hangup sequence in desk
phone control mode, please? I’d like to understand the difference between
softphone and desk control mode, please?
 
Thanks,
George
Flag

RE: desk phone control mode
Answer
11/22/12 2:33 PM as a reply to George Boda.
Hi George,
These are good questions, I will try to answer all of them!
[1] The server-side component (node.csf) is NOT required for deskphone control. As you say, the native plugin connects directly to CUCM to control another device.
[2] I am not 100% sure, I think the answer is yes, the configuration download is optional.
[3] The CSF device is used in softphone mode only. It is registered after the client (browser) successfully calls registerPhone (cwic JavaScript API) and remains registered until the application calls unregisterPhone or switchPhoneMode to switch to deskphone control. In the released SDK 2.0, CUCM never unregisters a CSF device automatically. We are working on better "multi-registration" support, which will allow a client to force the CSF device to be unregistered before registering again from a different PC for example.
[4] ECP<yourusername> is the default name of the CSF device used by the SDK in softphone mode, it is not used in deskphone mode. In deskphone mode, the same user can connect from multiple clients to control the same device simultaneously.
[5] From a cwic API perspective, the main difference is the mode parameter ("SoftPhone" or "Deskphone") passed to the registerPhone function. In deskphone mode the user password is mandatory, it can be bypassed in softphone mode (empty password string along with authenticate: false). Once registered, a call is started by calling startConversation and ended by calling endConversation. Same for call updates.
Hope this replies to your questions,
Thomas
Flag

RE: desk phone control mode
Answer
11/22/12 3:14 PM as a reply to Thomas Vanier.
Hi Thomas,
 
Thanks for the quick reply.
 
What UCL licenses are required on CUCM in the following scenarios?
1. Jabber SDK in softphone registering to CUCM v8.6.
2. Jabber SDK in phone control mode with 6921 phone?
3. Jabber SDK in phone control mode with 89xx/99xx phone?
 
Thanks.
George
Flag

RE: desk phone control mode
Answer
11/27/12 1:33 PM as a reply to George Boda.
George Boda:
Hi Thomas,
 
Thanks for the quick reply.
 
What UCL licenses are required on CUCM in the following scenarios?
1. Jabber SDK in softphone registering to CUCM v8.6.
2. Jabber SDK in phone control mode with 6921 phone?
3. Jabber SDK in phone control mode with 89xx/99xx phone?
 
Thanks.
George

 
Response from my local SE:      From a CUCM licensing perspective the same rules apply for Jabber SDK clients as for the packaged Jabber clients (Jabber for Windows/Mac).
 
 
 
Jabber SDK as soft phone with no other device requires one Enhanced UCL license per client.
 
Jabber SDK controlling physical phone – No License Required (uses Physical Phone license).
 
JAB-SDK8-K9 - Cisco Jabber SDK 8.6 Browser plugin
LIC-CUCM-USR-A  - Unified Communications Manager Enhanced Single User-Under 1K
 
The same rules apply for the Jabber SDK as it does for Jabber.
 
Jabber SDK as soft phone with no other device requires Enhanced UCL
Jabber SDK as soft phone but secondary device requires Adjunct license
Jabber SDK controlling physical phone – No License Required
 
 
Jabber SDK cannot be monitored by CUOM
Flag