Closed yaducam2 closed 10 years ago
'esl::event::**'
will catch auth success and error events, which do not send an event object with it. Maybe this is causing your issue?
EDIT:
I have fixed those events to pass along their event objects as well in the latest master
, mind trying that and seeing if it fixes the issue?
Hi, thanks for the quick feedback, I would be happy to test.. But I'm pretty new to node.js and i don't know how to updload the latest master. I tried "npm update modesl" but this doesn't update connection.js with the latest changes.. If i manually download & replace connection.js will it be enough to test ?
npm only knows to use what is in the npm registry, what you can go is delete the one you have in your node modules, git clone from this repo into your node modules folder, and npm install the dependencies of the module:
cd node_modules/
rm -rf modesl
git clone https://github.com/englercj/node-esl.git modesl
cd modesl
npm install
You should be able to run normally after that
Closing since this should have been fixed by the change I made.
Hi,
Looking at modesl documentation : https://github.com/englercj/node-esl/wiki/Event-API :
The two "event catchers" have the same callback definition. However, when i try to use the serialize method on the esl.Event callback
..is processed correctly by the node engine
BUT..
...will return this error :
Is that an issue/regression ?
regards,
Julien