Skip to end of metadata
Go to start of metadata


Table of Contents



Interoperable Vendors



© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved. The compilation (meaning the collection, arrangement and assembly) of all content on this site is protected by U.S. and international copyright laws and treaty provisions and may not be used, copied, reproduced, modified, published, uploaded, posted, transmitted or distributed in any way, without prior written consent of Ribbon Communications Inc.

The trademarks, logos, service marks, trade names, and trade dress (“look and feel”) on this website, including without limitation the RIBBON and RIBBON logo marks, are protected by applicable US and foreign trademark rights and other proprietary rights and are the property of Ribbon Communications Operating Company, Inc. or its affiliates. Any third-party trademarks, logos, service marks, trade names and trade dress may be the property of their respective owners.  Any uses of the trademarks, logos, service marks, trade names, and trade dress without the prior written consent of Ribbon Communications Operating Company, Inc., its affiliates, or the third parties that own the proprietary rights, are expressly prohibited.

Document Overview

This document outlines the configuration best practices for Vodafone involving EdgeMarc 2900 when deployed with SwyxPBX. This document provides the configuration snapshot of the interoperability performed between Ribbon's EdgeMarc 2900 and SwyxPBX, SwyxIt and Swyx Phone. SwyxPBX is a fully “Hosted PBX Service” with cloud telephony. In cases when you no longer have a PBX in your company, you obtain all features as a service from the cloud but you can keep your existing contract with your Service Provider who will provide you a local breakout.

Scope

This document provides configuration best practices for deploying Ribbon's EdgeMarc 2900 with SwyxPBX and associated users. Note that these are configuration best practices and each customer may have unique needs and networks. Ribbon recommends that customers work with network design and deployment engineers to establish the network design which best meets their requirements.

Non-Goals

It is not the goal of this document to provide detailed configurations that will meet the requirements of every customer. Use this document as a starting point and build the SBC configurations in consultation with network design and deployment engineers.

Audience

This is a technical document is intended for telecommunications engineers with the purpose of configuring both the Ribbon EdgeMarc 2900 and the SwyxPBX and associated users.

Steps will require navigating the third-party product as well as the Ribbon product using graphical user interface (GUI) or command line interface (CLI). An understanding of the basic concepts of TCP/UDP/TLS, IP/Routing, and SIP/RTP/SRTP is needed to complete the configuration and any necessary troubleshooting.

Pre-Requisites

The following aspects would be required before proceeding with Ribbon EM 2900 POE & SwyxWare 12.10.

  • SwyxWare 12.10 is installed in a Windows Server Platform and connected to the network.

  • A 190 trial license is available and obtained from Swyx.
  • Remote Desktop access to Windows host is available for remote access and configuration.

  • A valid 6 months trial License is running on the Server.

  • HFA firmware is loaded and installed on to Unify CP205 Phone Unit.

Product and Device Details


Equipment/ProductSoftware Version
Ribbon CommunicationsEdgeMarc 2900 POEVersion 15.8.3
Third-Party ProductsSwyxWareV12.10.16296.0
SwyxItV12.10.16296
Windows Server2019
Unify CP205V1 R3.9.0 HFA 190516

Network Topology Diagram

Use Case 2 Deployment Topology

The deployment topology diagram is depicted below.

Interoperability Test Lab Topology (or Call Flow Diagram)

IOT high-level architecture covering call flows & overall topology is depicted below.

Section-A: EdgeMarc Configuration

Connectivity

Configuring EdgeMarc A

In this use case, EdgeMarc A has a simple VPN configuration with no SIP configuration.

  1. Enable the VPN module then select Add a new VPN tunnel.

  2. Configure the following: 
    • The Protected Local Network - voice VLAN of EdgeMarc A.
    • The Remote VPN Gateway - WAN IP of EdgeMarc B.
    • The Protected Remote network - voice VLAN of EdgeMarc B. 

Configuring EdgeMarc B

EdgeMarc B is responsible for communicating with the SIP Service Provider as well as passing HFA phone traffic via IPSec tunnel to the head-end PBX. Configure IPSec:

  1. Enable the VPN module then select Add a new tunnel.

  2. Configure the following: 
    • The Protected Local Network - voice VLAN of EdgeMarc B.
    • The Remote VPN Gateway - WAN IP of EdgeMarc A
    • The Protected Remote network - voice VLAN of EdgeMarc A. 


      In addition, a static route is required on EdgeMarc B to allow the ALG to function correctly when communicating to a SIP PBX across a VPN tunnel. After logging into the EdgeMarc, execute the following commands:

      static router
      echo "router add -net 192.168.8.0/24 gw 172.16.1.1" >> /etc/config/user_defs.conf
      cfg_commit
      config_network
  3. Next, configure the ALG and SIP settings starting with the main VoIP page.


    The ALG VLAN selected should correspond to the voice VLAN of the EdgeMarc.
  4. Configure the SBC IP of the SIP Provider under list of SIP Servers. In this case the IP corresponds to the public IP of the Sonus 1000 used for testing.

  5. Next configure the LAN side SIP services.


    A trunking device is configured so that the EdgeMarc knows where to forward an inbound call from the SIP service provider. In this case, a non-standard port is used due to requirements of the Swyx PBX.
  6. Actions are configured in order to facilitate call routing in the Match section.




    The lab uses basic call routing that routes all inbound calls to the PBX and a specific client towards the provider.

Section-B: SwyxWare, SwyxIt and HFA Phone Configuration

Configuring SwyxPBX

  1. Right Click on Location > Add Location.

  2. Add codes and prefixes then click Next. 

  3. Add access to Dial out and click Next. 

Adding a User 

  1. Click on Server > Right Click on User > click Add User. 

  2. Add Name and Description then Click Next.

  3. Select the Location and click Next.

  4. Select a new internal number and click verify to check if available. Click OK then click next.



  5. The Internal Number selected will be mapped to a public number, then click Next. 

  6. Select the Terminals by checking boxes and then click Next.

  7. Create a Password for the user login then click Next.

  8. Create SIP user and password and then click Next.

  9. Create a Swyx Phone Pin and then click Next.

  10. Select a Calling Right and then click Next.

  11. Select a Feature profile and click Next.

  12. Assign properties to the new user and click Finish.


Configuring a SIP Trunk

  1. Right Click on Trunk Group and select Add Trunk Group The Add Trunk Group Wizard pops up then click Next.



  2. Add the Trunk Group Name and Description and click Next.

  3. Select the Trunk Group Type and click Next. 

  4. Add SIP settings and click Next.

  5. Add the SIP Proxy and leave SIP port blank (auto-resolves) and click Next.

  6. If a STUN server is supported, click the check box and add the IP for the STUN server and click Next.

  7. Select Transport Protocol and click Next.

  8. Select the Routing Definition and click Next.

  9. Select Location Profile and click Next.

  10. Click Finish. 

  11. Right Click on the Newly created Trunk Group and click Add Trunk, The Add Trunk Wizard pops up, then click Next.



  12. Add a Trunk Name and Description. 

  13. Add the SIP trunk Provider and User Data then click Next.

  14. Select the Subscriber Number using the SIP Trunk and click Next.

  15. Add a SIP URI (wild card "*" for any) and then click Next.

  16. Select the Codecs supported by the SIP trunk and click Next.

  17. Select the Number of Simultaneous calls possible in the SIP Trunk and click Next.

  18. Choose PSX server or Computer Name and click Finish.


Configuring the SwyxIt Client 

  1. Click On Settings and select Local Settings

  2. Click the Connections Settings Tab and add the Server name or IP address and the User Name, then click OK.

  3. From the File menu select Logon.

  4. Once Logged in, More Choices are available in the Settings Menu. Some configuration capability is also available from the User Properties on the PBX server.


Configuring the HFA Phone

The Unify CP 205 comes out of the box as a SIP Phone. You must upgrade the firmware before configuring HFA Phone. Upgrade the firmware using FTP/HTTPS Access Data

By default, the phone has DHCP enabled. Look on the EdgeMarc 2900 for the IP leased to the CP205 unit. 

  1. Open your web browser and enter the appropriate URL. Example: https://192.168.1.15.


    Note: the default password is 123456.
  2. From the Administration via Web-Based Management (WBM), select File transfer > Phone application. 
    Click Browse to find the corresponding L62.iso file to upload to the Unify CP205 Phones. Then, click Submit. 

  3. Once the firmware has been upgraded Login to Web-Based Management to configure the network settings by selecting Network > General IP configuration, then click Submit.
    Choose between DHCP or Static IP assignment.
     
  4. Select Network > IPV4 configuration, then click Submit. Add IP address, Subnet Mask, and Default Route. 
    Note: If DHCP is enabled the values will be fetched automatically. 

  5. Add Gateway information by selecting System > Gateway, then click Submit. 

  6. Choose Codecs by selecting Speech > Codec preferences, then click Submit. 
  7. Go to Phone and login to SwyxPBX using the user created in section Adding a User.


Supplementary Services and Features Coverage

The following checklist identifies the set of supplementary services/features covered through the configuration defined in this Interop document. 

Sr. No.

Supplementary Services/Features

Coverage

1Registration over UDP/TCP/TLS

2Basic Call Setup & Termination

3Ringing & Local Ringback Tone

4Remote Ringback Tone Handling

5Cancel Call & Call Rejection

6Call Forwarding Busy

7Call Forward No Answer

8Call Transfer (Attended)

9Call Transfer (Blind/ Unattended)

10Conference Call

Legend

Supported

Not Supported

Caveats

The following items should be noted in relation to this Interop document. These are either limitations, untested elements, or useful information pertaining to the Interoperability.

  • Fax calls and other test were not performed due to unavailability of required devices at the Ribbon Lab.

Support

For any support related queries about this guide, please contact your local Ribbon representative, or use the details below:

References

For detailed information about Ribbon products & solutions, please visit:

https://ribboncommunications.com/products

Conclusion

This Interoperability document describes a successful configuration and interop involving EdgeMarc 2900 and SwyxWare PBX.

All features and capabilities tested are detailed within this document. Any limitations, notes or observations are also recorded to provide the reader with an accurate understanding of what has been covered, and what has not.

Configuration guidance is provided to enable the reader to replicate the same base setup - there maybe additional configuration changes required to suit the exact deployment environment.


© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved.