Whole bridge terminates upon Unknown endpoint jvb error about jicofo

[bgrozev]

Makes sense. I think there's two parts to the solution:

1. Adding a Colibri2Error with a new UNKNOWN_ENDPOINT Reason to error responses from the bridge.
2. Recognizing these errors in jicofo and handling them differently (only re-invite that single endpoint)

[mykhailo-ua]

Makes sense. I think there's two parts to the solution:

1. Adding a Colibri2Error with a new UNKNOWN_ENDPOINT Reason to error responses from the bridge.
2. Recognizing these errors in jicofo and handling them differently (only re-invite that single endpoint)

Should it be a new condition in this case for first part? as jvb during generation exception has the comment that it should be Condition.item_not_found but this conflicts with some error codes from the Muc.

[bgrozev]

Item_not_founds is fine, as long as it also has a colibri2 error extension specifying that it's about an endpoint

[mykhailo-ua]

Item_not_founds is fine, as long as it also has a colibri2 error extension specifying that it's about an endpoint

do we need return specific endpoint id from the jvb?

• how to include? Is it possible to use Colibri2Endpoint extension like
  
• because there some batch operations where multiple endpoints can be used
  
  
• jvb will abort on the first unknown endpoint so will not work anyway with multiple endpoints - https://github.com/jitsi/jitsi-videobridge/blob/4bbb81e23e779d948d6c92d54315ea282cb86598/jvb/src/main/kotlin/org/jitsi/videobridge/colibri2/Colibri2ConferenceHandler.kt#L72

[mykhailo-ua]

Added proposed prs

• jitsi/jitsi-xmpp-extensions#93
• jitsi/jitsi-videobridge#1999
• #1048

[bgrozev]

The PRs have been merged now, thanks @mykhailo-ua !