Alberto Gonzalez Trastoy

In my case I did `npm install --unsafe-perm`

To fix that error I created a hasDescription function, it might be related with an update in sip.js. The following fixed it for me ``` KurentoMediaHandler.prototype = { // ......

You should add it inside this: https://github.com/agilityfeat/kurento-asterisk/blob/master/server.js#L132

@anaxdev probably is a little bit late but you should configure asterisk for webrtc by enabling Asterisk http server: https://wiki.asterisk.org/wiki/display/AST/Setting+up+the+Asterisk+HTTP+server

I tried both changes at the same time, the decoding seems to work fine but there is an unexpected behavior. In some situations more than one JSON is sent to...

**Update:** I had this consistently working with this changes of kurento-jsonrpc-js and this https://github.com/progre/reconnect-ws/pull/1 Also npm audit of kurento-client-js returns 0 vulnerabilities

[Here](https://github.com/Mupati/peermetrics/blob/feature/add-authentication/README.md#how-to-run-locally) says "How to run locally" and gives an explanation. And then later again another approach to run locally but for development. The first approach doesn't really work unless you...

nvm, I already push the [changes](https://github.com/peermetrics/api/commit/a6af476c0f528c83becd50e79e3c4e359320a399), so you can just directly test generating an api image from scratch and it shouldn't throw any errors