Configuring xMatters to use SIP

While configuring SIP in xMatters requires a number of steps unique to the protocol, the overall process is the same. This article can also serve as an outline to adding any protocol to xMatters.

Step One: Download the manual for your version of xMatters

Before beginning to configure any protocol, ensure that your documentation is correct for the version of xMatters in your deployment. You can download the latest version of the admin guide at the following link: xMatters documentation.

Step Two: Verify the compatibility of your SIP gateway

The SIP gateways supported by xMatters are listed in the "Installation" chapter of the admin guide.  Please refer to the manual for your specific deployment, as the supported SIP gateways may change between versions.

For ease of reference, xMatters 5.x supports the following SIP gateways:

Asterisk:

xMatters has been validated against Asterisk 1.8.

Avaya:

The following versions of Avaya have been validated and are supported with xMatters:

  • Avaya Aura Communication Manager 6.3.4 (Service Pack 4) running on Avaya S8800 Server with Avaya G650 Media Gateway (R016x.03.0.124.0 with Patch 21291)
  • Avaya Aura Session Manager 6.3 (6.3.5.0.635005)
  • Avaya Aura System Manager 6.3.5 (6.3.0.8.5682-6.3.8.2826)
  • Avaya 9600 Series IP Telephones 3.21 (H.323) and 2.6.10.1 (SIP)

Note that previous limitations with Avaya compliance identified in xMatters version 5.0 have been resolved as of version 5.1 patch 001.

Cisco:

xMatters has been validated against and supports Cisco Unified Communications Manager (formerly CallManager) version 7.0.1 and version 9.

Note: There are otehr considerations detailed in the admin guide. It is recommended that you familiarize yourself with the SIP Gateway section in the installation chapter.

Step Three: Configure a SIP Device Engine in xMatters

Using the information in the "System Configuration" chapter of the xMatters installation and administration guide, add a SIP Device Engine to your deployment. The documentation lists all of the parameters required to define the Device Engine; you will need to gather the information required from your VOIP phone technicians or gateway provider prior to configuring the Device Engine.

xMatters deployments that will experience high volumes of SIP traffic must have SIP Device Engines configured on dedicated xMatters Notification Server Node computers (i.e., the Notification Server Node must reside on a computer that is separate from other xMatters components such as web servers, application servers, and the database).

Step Four: Configure a SIP Protocol Provider

Using the information in the "System Configuration" chapter of the admin guide, add a SIP Protocol Provider to your deployment. The documentation lists all of the parameters required to define the Protocol Provider; you will need to gather the information required from your VOIP phone technicians or gateway provider prior to configuring xMatters.

Step Five: Configure a SIP User Service Provider

The "System Configuration" chapter also explains how to add a new User Service Provider for your SIP Devices.

Step Six: Add User Devices

You can now specify the User Service Provider you created in Step Five as a provider when adding Devices for Users. (For information on how to add a Device, see the xMatters user guide.)

xMatters Reference

JDN-1222 Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk