Howto:Guidelines for Testing 3rd Party SIP Terminal Devices

From innovaphone wiki
Revision as of 17:24, 2 May 2018 by Ckl (talk | contribs) (New page: <internal> innovaphone supports use of 3rd party SIP devices connected to the innovaphone PBX. In fact, when connecting 3rd party devices, SIP (or SIPS) is the recommended protocol. We d...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

<internal> innovaphone supports use of 3rd party SIP devices connected to the innovaphone PBX. In fact, when connecting 3rd party devices, SIP (or SIPS) is the recommended protocol. We do not recommend to use H.323 for this purpose.

Although innovaphone usually does no 3rd party SIP device compatibility tests, vendors can do them on their own. Such tests may be documented in our wiki in so-called referral product pages. See What it means in What is a "3rd Party Product"? for more information on referral products.

If you intend to test your device for innovaphone SIP compatibility, here are some notes you should consider

STUN/TURN
STUN and TURN are required. Although we do not strictly require 3rd party devices to support it, it is needed in cloud and anywhere workplace scenarios. Failing to support STUN/TURN limits use of the 3rd party device to LAN or VPN scenarios
ICE
again, for cloud and anywhere workplace scenarios, we also use ICE as the general mechanism to negotiate the best media connection between 2 devices. Failing to support it limits use of the 3rd party device to LAN or VPN scenarios
DTLS
we do support use of DTLS, which is a end-to-end media encryption scheme. Although we do not strictly require 3rd party devices to support it, it is needed for WebRTC compatibility. 3rd party devices which fail to support it will not be able to talk to WebRTC compliant endpoints (i.e. Web Browsers)
LDAP
the innovaphone infrastructure relies on LDAP for access to directory data. Although 3rd parties my provide their own contact infrastructure, not supporting LDAP results in an inconsistant
SIP SUBSCRIBE
TBD

Anything else? </internal> TBD