05-17-2016 03:07 PM
Hey Everyone,
I'm trying to implement Jabber SDK Node Component 11.0.1 and running into some difficulty.
I'm running Windows 10, GCC complier from MinGW, and using NVM to try different version of node while following the steps on page 35 and onward of:
https://developer.cisco.com/fileMedia/download/006949a5-ae49-47f3-978c-7ab9fe4cb4f3
I've also tried this on a Ubuntu VM as well. On both operating systems I've used the latest version of node (v6.1.0) and the exact version in the documentation (v0.10.5).
I can run the csf.js file with the default configuration, but I can't get the module to accept a configuration file. I've tried passing it in as a parameter as shown in the documentation. I've tried renaming the file to what the module expects: node.csf.cfg. In both of those cases I always get a "csf - cannot read ./node.csf.cfg" error as express starts up.
I've also tried editing the config variable in the csf.js file itself. However, when I do that I get the following error:
events.js:72
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at errnoException (net.js:884:11)
at TCP.onread (net.js:539:19)
Does anyone have any ideas of what I might be doing wrong or can point me in the right direction?
Thanks,
Kyle
05-19-2016 03:45 PM
Seems to work on my ubunto 16.04 system (though the logger output has some kind of undefined variable problem:)
$ tar -xzf ~/Download/csf-11.0.1-102.tar.gz
$ npm install csf-11.0.1-102.tar.gz
$ node node_modules/csf/csf.js node_modules/csf/config/csf.cfg
I edited the csf.cfg from what came in the package, to remove the phoneConfig module, which was throwing an error about ports/permissions since I didn't fully set it up. The config file path/name passed in to the command line should be just whatever the actual config file path/name is on disk.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide