You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am able to use my own jingle-session subclass to establish a WebRTC connection between two web pages using stanza.io for signaling. It works fine in the absence of errors and I'm now trying to ensure it behaves properly when errors are present.
In the case where the receiving side declines to make the connection (using session.decline()), things work fine - I catch that with a terminated event on the initiating jingle-session. But in the case where the receiving side drops its connection and is unavailable, the XMPP server replies to the jingle session-initiate iq with an error, e.g.:
I don't see a way at the jingle-session level to detect that. Does one exist?
At the moment I am detecting failed connections using a timeout, but this occurs much later than the failure actually occurs. I could parse the XML traffic but that is pretty tedious. I'm hoping there is some other mechanism I have overlooked.
The text was updated successfully, but these errors were encountered:
I am able to use my own
jingle-session
subclass to establish a WebRTC connection between two web pages using stanza.io for signaling. It works fine in the absence of errors and I'm now trying to ensure it behaves properly when errors are present.In the case where the receiving side declines to make the connection (using
session.decline()
), things work fine - I catch that with aterminated
event on the initiating jingle-session. But in the case where the receiving side drops its connection and is unavailable, the XMPP server replies to the jinglesession-initiate
iq with an error, e.g.:I don't see a way at the
jingle-session
level to detect that. Does one exist?At the moment I am detecting failed connections using a timeout, but this occurs much later than the failure actually occurs. I could parse the XML traffic but that is pretty tedious. I'm hoping there is some other mechanism I have overlooked.
The text was updated successfully, but these errors were encountered: