Howto:MyApps Cloud - Connecting 3rd-party SIP devices (general considerations): Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 22: Line 22:


For the following 3-rd party devices, a specific description is available, describing details of the respective configuration:
For the following 3-rd party devices, a specific description is available, describing details of the respective configuration:
* Howto:V13 MyApps Cloud - connecting Yealink-phone
* [http://wiki.innovaphone.com/index.php?title=Howto:V13_MyApps_Cloud_-_connecting_Yealink-phone Howto:V13 MyApps Cloud - connecting Yealink-phone]




== 3-rd party SIP devices without STUN support ==
== 3-rd party SIP devices without STUN support ==
If a 3rd-party SIP device (e.g. doorphone) does not meet the above defined minimum requirements, an additional local gateway (edge component) on the customers premises is needed, to connect the device to the myApps Cloud platform.
If a 3rd-party SIP device (e.g. doorphone) does not meet the above defined minimum requirements, an additional local gateway (edge component) on the customers premises is needed, to connect the device to the myApps Cloud platform.

Revision as of 14:37, 3 March 2021

Applies To

This information applies to

  • myApps Cloud v13
  • General considerations on 3rd-party SIP devices


Disclaimer

This article is presenting a summary of our experience, connecting 3rd-party devices to the myApps Cloud platform. As innovaphone is not able to track all changes in functionality or firmware of 3rd-party SIP devices, this document is meant to be an orientation to our certified partners. In any case, it is recommended to the partner to verify the functionality of a 3rd-party product. As such innovaphone is not liable for any malfunction of, or caused through a 3rd-party product, even if the respective product is listed in this article.


Requirements to 3-rd party SIP devices, when connecting to the myApps Cloud

By default, the myApps Cloud service relies on the ICE protocol to establish peer-to-peer media communication between connected 3rd-party SIP devices. Thus, the connecting SIP device has to be able to support STUN, TURN and the ICE mechanism.

  • In case ICE is not supported by the SIP device, the absolute minimum requirement is STUN support. (in such case, the respective PBX User Object has to enable Media-Relay). In this scenario the media stream is always routed through the PBX (instead of peer-to-peer routing, when using the default ICE mechanism as described above).

To provide a secure data connection, the myApps Cloud is by default using TLS for encryption (e.g. SIPS or SIP/TLS). Thus, we recommend to select a 3rd-party SIP device supporting TLS. For this reason, the myApps Cloud platform already includes the root certificates of the following 3-rd party manufacturers:

  • Yealink


Howto articles, for selected 3-rd party SIP devices

For the following 3-rd party devices, a specific description is available, describing details of the respective configuration:


3-rd party SIP devices without STUN support

If a 3rd-party SIP device (e.g. doorphone) does not meet the above defined minimum requirements, an additional local gateway (edge component) on the customers premises is needed, to connect the device to the myApps Cloud platform.