Singlewire Software Integration with Wildix

Introduction

The Wildix and Singlewire InformaCast integration allows organizations to leverage Wildix’s VoIP and Unified Communications capabilities alongside InformaCast’s notification solutions. The integration is achieved through a secure SIP trunk using TLS/SRTP for encrypted communication. The Wildix InformaCast integration enhances enterprise communication by combining secure VoIP capabilities with mass notification features. By leveraging TLS-encrypted SIP trunks, multicast paging, and emergency alerting, organizations can deploy a scalable and secure communication platform for both routine and critical messaging needs. 

Use cases

• Emergency notifications: Send critical alerts (e.g., fire alarms, lockdown warnings) from InformaCast to Wildix phones and other connected devices using multicast paging (provided an InformaCast server is deployed on site)

• Trigger notifications: Trigger any InformaCast notifications from Wildix phones 

Requirements

• WMS latest version 

• An active InformaCast Fusion subscription with Singlewire Software

• A Fusion server (virtual or hardware appliance) registered to your InformaCast Fusion provider

• Multicast support on local network

Wildix PBX Setup

Step 1. Create a SIP trunk

• Go to WMS -> Trunks menu and click +Add option:

Open

• Fill up the following fields:

  • Title: user defined, informacast in this case

  • Trunk name: user defined, informacast in this case

  • Auth Login: user defined, informacast in this case (this user name will be used by InformaCast to connect to this trunk/ PBX)

  • Address or Host Name = dynamic (it means InformaCast server will register against Wildix server to create the SIP trunk)

  • Password: user defined password (this password can be anything and will be used by InformaCast server  to connect to this trunk/ PBX)

  • Also, make sure Enable registration option is disabled (InformaCast server will register against Wildix, not the other way around)

• Click Save. A configured trunk should look like this:

Open

Step 2. Obtain Certificate

Since a SIP trunk is required for the integration, it is recommended to enable encryption to ensure secure communication. While encryption is optional, both InformaCast and Wildix servers support it. This section outlines the steps needed to configure secure communications.

• Access Wildix server terminal and execute the following command as root: 

  cat /etc/kamailio/ssl/cert.crt  > /mnt/wildixcert.pem

• Then create a diagnostics hub report (see Diagnostics Hub: Features & Utilities) and download it, inside the report you will find a file called wildixcert.pem:

Open

• wildixcert.pem is the certificate you need in the following section. Once you have the certificate, execute the following command on the terminal (to ensure more reports created do not include the certificate): 

  rm /mnt/backups/wildixcert.pem 

InformaCast Server Setup

The following settings are to be performed on InformaCast web interface, all settings are to be performed under Admin -> SIP section:

Open

Step 1. Upload certificate

• Go to Admin -> SIP- > SIP Certificates section and click Upload option

• Navigate to the certificate obtained in the previous step. Once the certificate is uploaded, besides Singlewire server default certificate, you should see a certificate with your Wildix server name:

Open

Step 2. Ensure secure communications

• Go to Admin -> SIP -> Call Security section and make sure the following options are enabled and save:

  • Secure Signaling Required

  • Secure RTP Allowed

Open

Step 3. Create SIP Account

• Go to Admin -> SIP -> Accounts section and click Create Account

Open

• Assign a name to your account (WildixTrunk will be used in this example) and select Other option under telephony provider, another form will appear

• Fill up the fields as following:

  • Enable Registration: make sure this field is enabled

  • User: Auth Login value set in Create a SIP trunk step (informacast in this example)

  • Host: your Wildix domain name (in the form of NAME.wildixin.com)

  • Transport Protocol: TLS

  • Outbound Proxy Server(s): your Wildix domain name (in the form of NAME.wildixin.com)

  • Use DNS SRV: disable this option

  • Use Realm Authentication: disable this option

  • Authorization ID: Auth Login value set in Create a SIP trunk step (informacast in this example)

  • Password: Password value set in Create a SIP trunk step

Open

Once the previous settings are in place, you are ready to set up some Notifications from InformaCast to Wildix phones (see Delivering audio notifications to Wildix phones from InformaCast ) and to trigger some notifications from Wildix to InformaCast (see Triggering InformaCast notifications from Wildix).

Delivering audio notifications to Wildix phones from InformaCast 

One of the easiest ways to deliver an audio message to a big number of Wildix phones is using multicast paging, provided there is InformaCast server appliance on site, doing multicast paging is really easy.

By default, Wildix provisions its phones to use 239.1.1.10 address for multicast paging, and ports from 10000 and up. Considering that and the fact that InformaCast can perform multicast paging on site, the following setting need to be performed.

Wildix Paging Groups

• Go to WMS -> Dialplan-> Paging Groups and click +Add option

• On the form, assign a name to the paging group and add all the users (phones) that need to be paged in this group and click Save:

Open

• Once all the needed paging groups are created, make sure to sync all of the phones that need to be synced: go to WMS -> Devices -> select the devices and click Configure/ Sync device

• Keep in mind that paging groups are created using different ports on the address 239.1.1.10, starting from port 10000. The first paging group created in WMS uses port 10000, the second group uses port 10001, and so on:

Open

• Considering the previous picture, phones in the "Building_1" group will subscribe to 239.1.1.10:10000 (first port available), while phones in the "Main_Building" group will subscribe to 239.1.1.10:10004. The key point to remember is that the assigned port corresponds to the ID value minus one (because ports start in 10000, not it 10001), which will be relevant in the next section.

InformaCast