Howto:Guidelines for Testing 3rd Party SIP Terminal Devices: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 12: Line 12:
; DTMF : various features in the PBX are controlled via DTMF tones.  Endpoints are required to send DTMF either using RFC  2976 (''SIP INFO'') or RFC 2833 (''RTP DTMF'').  The PBX will not recognize in-band DTMF audio  tones
; DTMF : various features in the PBX are controlled via DTMF tones.  Endpoints are required to send DTMF either using RFC  2976 (''SIP INFO'') or RFC 2833 (''RTP DTMF'').  The PBX will not recognize in-band DTMF audio  tones
; LDAP : the innovaphone infrastructure relies on [https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol LDAP] for access to directory data.  Although 3rd parties my provide their own contact infrastructure, not supporting LDAP results in an inconsistent user experience
; LDAP : the innovaphone infrastructure relies on [https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol LDAP] for access to directory data.  Although 3rd parties my provide their own contact infrastructure, not supporting LDAP results in an inconsistent user experience
; CTI : can be test using a myApps, myPBX or TAPI
:* Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list)
:* Answer incoming incoming call
:* Hold/Retrieve
:* Transfer


For more information regarding implemented RFCs, see [[Reference:Supported SIP Features and List of RFC's]]
For more information regarding implemented RFCs, see [[Reference:Supported SIP Features and List of RFC's]]

Revision as of 12:07, 9 January 2019

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. As ICE is the supported mechanism to use STUN/TURN, neither would be used properly if ICE is not implemented. As a result, 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)
TSIP
(also known as SIP over TCP). TCP based SIP (optionally encrypted with TLS) is required to route SIP requests through our reverse proxy. Therefore, devices supporting SIP/UDP only will not work in such scenarios
SIP Offer/Answer Model
with Reverse-Media-Negotiation. This is required for all devices which are registered to the PBX directly. So this is a requirement for all 3rd party phones at least
DTMF
various features in the PBX are controlled via DTMF tones. Endpoints are required to send DTMF either using RFC 2976 (SIP INFO) or RFC 2833 (RTP DTMF). The PBX will not recognize in-band DTMF audio tones
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 inconsistent user experience
CTI
can be test using a myApps, myPBX or TAPI
  • Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list)
  • Answer incoming incoming call
  • Hold/Retrieve
  • Transfer

For more information regarding implemented RFCs, see Reference:Supported SIP Features and List of RFC's