Provide Your Users with QoS.VC Quality


Integrate QoS.VC in your WebRTC or SIP Client


Deploy Your Cloud Service on QoS.VC



QoS.VC provides a wide range of possibilities for developers in terms of what you can do with the QoS.VC Global Network Platform.

Some service providers and vendors may integrate the QoS.VC Relay Address or QoS.VC TURN in their video conferencing endpoints, clients and VMRs/MCUs.

Other service providers and vendors may QoS.VC enable their own cloud service with QoS.VC Virtual Machines, Colocation, or Cross Connect.

Integrating QoS.VC Redirect Address
Description

QoS.VC is a basic SIP URI Redirect/Rewrite Service distributed in all QoS.VC nodes / PoPs.

Service Providers and resellers can integrate the QoS.VC Redirect Address as alternative SIP URIs for video conferencing endpoints, clients and virtual meeting rooms.

The service can be made available for all users or presented as a quality network upgrade feature.

Contact developers @ mns.vc to discuss further how you may leverage the QoS.VC Redirect Address.

Pricing

QoS.VC pricing for service providers and vendors can be provided per User, per Mbps, or per Gb. Let's discuss which model fits your business best.

Integrating QoS.VC TURN
Description

To embed the QoS.VC distributed STUN/TURN in your video conferencing endpoint, client, MCU or service (SIP or WebRTC), it is recommended the standards listed below are followed and that a slight adjustment to ICE behavior is implemented.

STUN/TURN Service
QoS.VC provides a globally distributed STUN/TURN service. The service is accessed using IP anycast, ensuring an optimal media path from all parts of the world. The STUN/TURN servers are compliant with the following IETF RFCs:

  • RFC 5389 Session Traversal Utilities for NAT (STUN)
  • RFC 5766 Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
  • RFC 5780 NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)
  • RFC 6156 Traversal Using Relays around NAT (TURN) Extension for IPv6
ICE Considerations
In addition to providing clients with NAT traversal assistance, QoS.VC utilizes TURN as a mechanism to attract media into the QoS.VC Global Network Platform.

In order to take full advantage of this service, and ensure media is routed via QoS.VC when placing calls outside the user's local network, a slight adjustment to standard ICE behavior is needed. By simply disabling the server-reflexive ICE candidate one make sure that media is routed via the QoS.VC TURN servers whenever a call is placed outside the user's local network.

APIs
APIs are available for creation/management of TURN users and extraction of TURN traffic records.

Developer Credentials
Email developers @ mns.vc to obtain free developer credentials and start testing/embedding the QoS.VC distributed STUN/TURN service.

Pricing

QoS.VC pricing for service providers and vendors can be provided on per User, per Mbps, or per Gb. Let's discuss which model fits your business best.

Deploying with QoS.VC VM or Colo
Description

Service providers and vendors can deploy their cloud service on the QoS.VC Global Network Platform, either by QoS.VC Virtual Machines or by QoS.VC Colocation, in one or more QoS.VC PoPs.

Pricing

QoS.VC pricing for service providers and vendors can be provided on per User, per Mbps, or per Gb. Let's discuss which model fits your business best.


For commercial matters, please contact sales (at) mns.vc