Forums
« Back to Installation

server side node.js application installation issue

Combination View Flat View Tree View
Threads [ Previous | Next ]
We were looking at CUCM authentication at server side. I came across your node.js application, i installed node.js and tried installing application ,I came across following error

npm ERR! fetch failed https://registry.npmjs.org/ldapjs/-/ldapjs-0.6.2.tgz
npm ERR! Error: tunneling socket could not be established, cause=getaddrinfo ENOENT

Also attaching log for your reference. Is this the only way possible for server side authentication? .

I also came across  unauthenticated registrations by passing "authenticate: false" and "password: ''".  Is this supported?
It is not working on shared sandbox.

Thanks in Advance
Attachments: npm-debug.zip (10.0k)

Hi swaroop,
Regarding the node installation problem, is your machine behind a proxy ? Some proxy settings should be configured for the npm (node package manager) tool, see here https://github.com/isaacs/npm/issues/2677
The authenticate:false/password:"" combination is supported in softphone mode (SIP) only, user must authenticate when connecting in deskphone mode (CTI). Are you trying to bypass authentication, or to implement it on the server ?
Thanks, Thomas

Hi Thomas ,
Yes you were right. After i configured proxy for npm it got installed without any problem.
Im looking at both options actually bypass authentication and implement it on the server. I tried  unauthenticated registrations  in softphone mode only, on CUCM IP 10.10.30.1 with username: user ,password: "", server auth checkbox: unchecked but the login failed on shared sandbox.
Sorry to bother with one more question
Does the end user has to install  Cisco Jabber SDK browser plugin separately or is there provision to detect unavailability of plugin and download on the go?

Yes, the end user must install the Cisco Jabber SDK.  We are working on ways to detect that the plug in is not available, and then initiate the installation of the plug-in from a web page.  It will be available in a future release.

Hi swaroop,
Glad to hear you could install the SDK node after configuring your proxy in the npm settings. What is the exact login error when passing an empty password ? Could you check in the browser console the actual values of the user, password and authenticate parameters passed to registerPhone ? By default the unauthenticated login expects a CUCM device of type CSF with name ECP<user>, this can be overriden when calling cwic init.
Regarding your last question, the SDK leaves the plugin installation up to the application. Some admins prefer to "push" the plugin to clients, while some applications will silently ignore a missing plugin. Your application could call cwic init with both a success and error callbacks. If the error one is called with the PluginNotAvailable, you could prompt the user for downloading and installing the plugin.
Thomas

Thanks Shawn O'Rourke and Thomas Vanier for clarification
And regarding unauthenticated registration error
The login error is   Unable to login: Login Error eUnknownFailure
I also put console.log in login function .Following are the parameters passed
user: user, password: (an empty string), cucm:10.10.30.1, auth:false, phoneMode: SoftPhone
  Following is the console log    
 
registerPhone: 1 cucm addresses
10.10.30.1
["10.10.30.1"]
registerPhone of user=user (authenticate=false) in mode="SoftPhone"
eUnknownFailure
 
Object { code=20, message="Login Error"}
Login Error
Object {
code: 20
details: ["eUnknownFailure"]
message: "Login Error"
registration: Object{
authenticate: false
devices: Object {}
forceRegistration: false
mode: "SoftPhone"
useCcmcip: undefined
user: "user"
}
}
 
unregisterPhone
[Object { forceLogout=true}]
 

Hi swaroop,
This type of error can happen when the CUCM host name is not resolvable from the client machine. Even though the 10.10.30.1 IP address is passed to registerPhone, the SDK stack wil use the CUCM "server name" configured by the admin when registering. For more information see the bottom of this post
http://developer.cisco.com/web/jabber-developer/jabber-voice-forum/-/message_boards/message/5786367
Thomas

Hi Thomas Vanier,
Thanks for your help.
I have added
10.10.30.1 ucm
in hosts file and I can successfully ping ucm.
But still the same problem exist.