Blink integration

AG Projects RTC Platforms (Integration Guides)

This document describes the requirements for integrating Blink with a SIP platform.

A reference implementation is available with http://sip2sip.info SIP service.

To enable Blink functions into another platform deployed by AG Projects, several components are required to be installed and configured together with a contract from AG Projects. To enable this functionality you must obtain a contract from AG Projects and open a ticket in AG Projects support system.

Domain name

A domaine name is required. The customer needs to allocate a domain name to contain all the hostnames required for operating the services:

• msrprelay.example.com
• conference.example.com
• cdrtool.example.com
• xcap.example.com

TLS certificates

This component is mandatory.

To avoid the need of multiple TLS certificate, a wildcard certificate can be applied for at a registry like RapidSSL. This allows one certificate for *.example.com to be reused for all server components that require a TLS certificate.

ICE media

This component is optional.

To avoid relaying RTP video calls through the platform, ICE NAT traversal can be used to allow for discovering the shortest media path between end-points. This can be done by configuring OpenSIPS and MediaProxy to enable ICE transport.

Provisioning

This component is optional.

This allows for:

• Blink accounts to be automatically configured from within the SIP account settings web portal part of CDRTool or the custom web site developed by the customer using NGNPro API. When using CDRTool, a new tab is enabled in the SIP settings page and from it Blink can be automatically configured with the account stored on the SIP server.
• SIP account page to be opened from within Blink. This can be used to change the account settings on the server or order more services like paying for PSTN credit

This requires a X.509 TLS certificate to match the hostname where the web service runs (e.g. cdrtool.example.com)

Presence

This component is mandatory.

Presence allows end-to-end signalling of end-point status and a note using Subscribe/Notify mechanism and Publishing of changes related to user icon. The complete functionality is described at Presence.

Presence requires OpenSIPS to be configured as a SIP Presence Agent and OpenXCAP to be installed and configured for storing of buddy lists and presence policy.

• OpenXCAP server must be installed and configured with an X.509 TLS certificate to match the hostname where the XCAP service runs (e.g. xcap.example.com)
• OpenSIPS must be configured for using TLS for signalling and requires as well a X.509 certificate to operate
• OpenSIPS must be configured as presence agent
• Provisioning portal must be configured to provide the XCAP settings for the user
• DNS records must be added to advertise the location of the XCAP server

Chat, File Transfer and Screen Sharing

This component is mandatory.

This allows the session features beyond VoIP to work behind NAT.

• MSRPRelay server is required
• MSRP runs over TLS and it requires a X.509 TLS certificate to match the hostname where the relay service runs (e.g. msrp.example.com).
• DNS record must be added to advertise the location of the MSRP relay

Multiparty conferencing

This component is mandatory.

• SylkServer is required
• An X.509 TLS certificate to match the hostname where the web service runs (e.g. conference.example.com)
• DNS must be set to advertise the location of the MSRP relay.
• OpenSIPS must be setup to route conference calls to SylkServer
• An ENUM entry corresponding to one telephone number must be setup to route phone calls to the conference bridge
• CDRTool rates must be setup in case rating is required for accessing the conference service

Next Steps

Continue by:

• learning the steps to Obtaining/Requesting support.