-
Notifications
You must be signed in to change notification settings - Fork 751
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disconnected event does not deliver data object #511
Comments
True. This happens due to this line in https://github.com/versatica/JsSIP/blob/master/lib/Transport.js#L163 There we are calling |
Oh I see. I noticed it, because I was upgrading to the latest version. In the old version the disconnect event was called with data. |
True, the
http://jssip.net/documentation/3.2.x/api/socket/#event_ondisconnect Thanks for reporting, I'll update it. |
In fact, the payload of the |
Can you point it in the code? |
Not in the code but in the doc: http://jssip.net/documentation/3.2.x/api/ua/#event_disconnected |
That's true. The documentation differs from the actual code. |
Aha, true. I'll synchronise it ASAP. |
So there will be no more parameters for the disconnect event? |
Those documented here: http://jssip.net/documentation/3.2.x/api/ua/#event_disconnected |
After reviewing the doc I see that it's aligned with the implementation. Such event does not assume |
If there's any comment on this regard, please speak up. |
jssipInstance.on('disconnected', function(data) { // code here });
The data object is undefined. Concerning the documentation there should be at least socket, error, code and reason in the data object.
The text was updated successfully, but these errors were encountered: