Teams Cloud Video Interoperability Service

Important Information – Teams CVI Retirement

The Teams Cloud Video Interoperability (CVI) service was retired on 28 October 2022 at 19:00.

What does this mean?
Video conferencing devices that utilise the Teams CVI Service will no longer be able to connect to Teams meetings. This means that users will be unable to join a meeting using the “join with a video conferencing device” details.

What do I need to do?

Organisations should communicate this change to their users. Users should be advised to update meeting invitations where Teams CVI joining details were included.

To continue using Teams in a video conference room setting, your organisation should use a Teams Room compatible device with appropriate licensing.

Please follow the guidance below to setup a Teams Room compatible device Adding a device to MS Teams – NHSmail Support.

Organisations should review and remove their firewall rules that may have been implemented as part of your local configuration when Teams CVI was setup and are now no longer needed. For reference, please see the firewall rules that were required as part of the implementation in the table below. 

Outbound Rules – From Endpoint to Conferencing Nodes (H.323)

Source Address Source Port Dest. Address Dest. Port Protocol Notes
VTC Any Conferencing Node <Any> 80 TCP (HTTP) Web browser
VTC Any Conferencing Node <Any> 443 TCP (HTTPS) Web / Infinity Connect client / Meeting Invite
VTC Any Conferencing Node <Any> 1719 UDP H.323 (RAS signalling)
VTC Any Conferencing Node <Any> 1720 TCP H.323 (H.225/Q.931 signalling)
VTC Any Conferencing Node <Any> 33000-39999 TCP H.323 (H.245 signalling)
VTC Any Conferencing Node <Any> 40000–49999 TCP RTP / RTCP / RDP / VbSS / DTLS / STUN / TURN
VTC Any Conferencing Node <Any> 40000–49999 UDP RTP / RTCP / RDP / VbSS / DTLS / STUN / TURN

Outbound Rules – From Endpoint to Conferencing Nodes (SIP) 

Source Address Source Port Dest. Address Dest. Port Protocol Notes
VTC Any Conferencing Node <Any> 80 TCP (HTTP) Web browser
VTC Any Conferencing Node <Any> 443 TCP (HTTPS) Web / Infinity Connect client / Meeting Invite
VTC Any Conferencing Node <Any> 5060 TCP SIP
VTC Any Conferencing Node <Any> 5061 TCP SIP/TLS
VTC Any Conferencing Node <Any> 40000–49999 TCP RTP / RTCP / RDP / VbSS / DTLS / STUN / TURN
VTC Any Conferencing Node <Any> 40000–49999 UDP RTP / RTCP / RDP / VbSS / DTLS / STUN / TURN

Inbound Rules – From Conferencing Nodes to Endpoints (H.323) 

Source Address Source Port Dest. Address Dest. Port Protocol Notes
Conferencing Node <Any> 33000–39999 VTC 1719 UDP H.323 (RAS signalling)
Conferencing Node <Any> 33000–39999 VTC 1720 TCP H.323 (H.225/Q.931 signalling)
Conferencing Node <Any> 33000–39999 VTC Any TCP H.323 (H.245 signalling)
Conferencing Node <Any> 40000–49999 VTC Any TCP/UDP RTP / RTCP / RDP / VbSS / DTLS / STUN / TURN

Inbound Rules – From Conferencing Nodes to Endpoints (SIP)

Source Address Source port Dest. Address Dest. Port Protocol Notes
Conferencing Node <Any> 33000–39999 VTC 5060 TCP/UDP SIP/TCP
Conferencing Node <Any> 33000–39999 VTC 5061 TCP SIP/TLS
Conferencing Node <Any> 40000–49999 VTC Any TCP/UDP RTP / RTCP / RDP / VbSS / DTLS / STUN / TURN

 

 

Last Reviewed Date 28/10/2022
Updated on 28/10/2022
Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support
back to top