Objective
Integrating Algo and 8x8. This can be done through two methods:
- SIP Integration
- Multicast Integration
Applies To
- Algo IP Speakers
- Algo IP Paging Adapters
- Algo IP Visual Alterers
- 8x8 Service
Procedure
- Algo 8180 with firmware 2.6.4 against a Poly VVX500 running 4.1.6.5216.
- Algo 8180G2 with firmware 1.6.4 and a Poly VVX350 and 5.9.7 firmware.
- Retested with Algo 8180G2 with firmware 5.2 and a Poly VVX350 and 5.9.7 firmware.
- Verified with Algo 8188, 8373, 8301, 8039, and 8186.
The screens may be slightly different but the values are all the same.The Algo 8180 functions differently from the Algo 8180G2. For new purchases, 8x8 recommends the 8180G2.
Prior to Setup
The Algo can be either a Sender or a Receiver but not both at the same time.
Functionality as Tested
The following functionality was verified when set up per this document.
- Press the page button on the Poly and select the proper group ID (Group 2 in this example).
- All Polys set up to listen went off-hook and the page was received
- The Algo Horn activated and the page was received/played
- Dialing the page extension assigned to the Algo.
- The Algo Horn activated and received/played the page
- Multicast phones DID not receive the page (no relay)
SIP Endpoint Integration
- Order a standard service plan for the Algo.
- Request 3rd party SIP Credentials for the extension you set up in 8x8 Admin Console.
X Series - Admin Console
Algo Setup in Admin Console with SIP Auth
- Log into the Algo and set the following for SIP registration (FOR SIP Integration only):
- Auth name = GUN/Username
- Page Extension = GUN/Username
- Auth Password = SIP Password
- URL = unsbc.8x8.com:5299
- Set as NON-SRTP
Setting up and Using 8x8 Group Paging in Admin Console
To enable group paging in Admin Console, see Create a Paging Group in Admin Console.
SIP Registration
This step is for SIP Integration only, not required for Multicast Integration. In this integration a user will dial an extension the Algo will answer and the page will be placed over the Algo. As an option, the page can be relayed to all Polys configured to listen to the Multicast page group ID.
- Navigate to the Control Panel.
- Click Basic Settings > SIP.
- Enter the GUN into the Auth name and Extension.
- Enter the SIP Password into the Auth Password.
- Enter unsbc.8x8.com:5299 into SIP Domain.
Optional SIP with Multicast Integration
With this option after the SIP Extension is dialed and the Algo answers the page will also be relayed out to any Poly devices configured to listen to the page group defined.
- Click Basic Settings > Multicast.
- Select the groups you wish the announcement to be sent to.
Multicast Setup
- Log into Algo to set up Multicast (For Multicast Integration only).
- Mode = Slave/Receiver (Typical Integration)
- Paging/PTT = Group Page
- Zone = 224.0.1.116:5001 (REQUIRED/Default)
- Default channel = whatever group you want
- Priority = 24 (Poly default)
- Emergency = 25 (Poly Default)
This step is not required for SIP Integration, but only for Multicast Integration. In this integration the Poly device will initiate the page, all Polys configured in the page group will receive as well as the Algo.
- Click Basic Settings > Multicast.
- Enter the following:
- Multicast Mode: Slave/Receiver (Typical Integration)
- Paging/PTT: Group Paging
- Zone: 224.0.1.116:5001 (REQUIRED IP:PORT)
- Default Channel: Of your choice
- Priority Channel: Group 24 (Poly Default)
- Emergency Channel: Group 25 (Poly Default)
Newer firmware may look like this:
Multicast Setup
- Click Basic Settings > Multicast.
- Enter the following:
- Multicast Mode: Slave/Receiver
- Paging/PTT: Group Paging
- Zone: 224.0.1.116:5001 (REQUIRED IP:PORT)
- Default Channel: Of your choice
- Priority Channel: Group 24 (Poly Default)
- Emergency Channel: Group 25 (Poly Default)
Troubleshooting
8301 LED Status
All four blue lights will be on during the power up and boot process.
- SIP: Steady light will appear when the SIP extension is registered. The light will blink when the device is engaged in a SIP page/ring.
- MCAST: Steady light will appear when 8301 receives multicast messages as a Slave. The light will blink when 8301 sends output to the Slaves as a Master.
- INPUT: The input light is ‘on’ when the device is actively using an analog input port, based on the configuration set in the web interface and the active state (it does not detect a physical connection to the audio jack).
- OUTPUT: Output light is on when analog output is enabled.
Use LED Status to verify the device is receiving traffic (SIP, Multicast and Network).
Verify Registered
To verify registration status, use Analytics for 8x8 Work and the Device Report to see the status if registered, it should be listed as such in the "Endpoints Status" field.
If the device is not registered verify the SIP credentials with 8x8 Support and/or verify the device settings listed above. You should also run the Network Utility to verify that the required ports and ALG is not Interfering with the registration.
Verify Connection to Paging Equipment
If the Algo is registered but there is no audio coming out of the paging device, verify the connection to the device. Algo provides wiring guides to several popular paging devices. Verify the device is powered on and the volume is set correctly.
Verify Multicast Traffic
If no audio is heard at the device, or it is in question if the audio is making it to the Algo, you can verify the Multicast traffic in Wireshark by taking a Wireshark at the Algo or Device port. In the PCAP results filter to ip.addr==224.0.1.116, which is the destination for all Poly Multicast traffic (it does not matter which zone). If you see traffic as seen below Multicast traffic is present.