Target Platform

Connects CCaaS to a Metaswitch platform by creating a virtual handset subscriber and entering its SIP and CommPortal API details.

Target Platform configuration connects CCaaS to a Metaswitch deployment using SIP connection details and CommPortal API credentials taken from a virtual handset subscriber created in the MetaView Web Portal, typically by a Metaswitch reseller. This must be completed before any SIP extensions can be registered — see SIP Extensions.


Creating the Virtual Handset Subscriber

The virtual handset subscriber is created in the MetaView Web Portal, typically only accessible to a Metaswitch reseller.

  1. Navigate to the MetaView Web Portal and select Business Group > Lines > Add Line

    458
  2. Assign a license type that allows a SIP connection — the specific type otherwise makes no difference

  3. Add a phone number and subscriber name (for example, Xima Virtual Handset)

  4. Add the extension under the Extensions tab

    1051
📘

Voicemail Must Be Disabled

The virtual handset subscriber's voicemail must be disabled.


Setting Maximum Call Appearances

  1. Open the new subscriber and select the Connection tab
  2. Set Maximum Call Appearances to a value the deployment will not exceed
  3. Note this value — it is entered as Total Channels Per Extension in CCaaS
790

Retrieving API Credentials

  1. Select the subscriber's Configuration tab, then open the Advanced menu

  2. Confirm User notification of call diversion is selected

    1700
  3. Note the Phone number — this is entered as the API Username in CCaaS

  4. Note the EAS Password — this is entered as the API Password in CCaaS

1700
📘

EAS Password vs. SIP Password

The EAS Password is not the same as the SIP Password used later to register the extension in CCaaS — see SIP Extensions.


Accessing Target Platform

Target Platform is accessible to accounts with Admin permissions.

  1. Navigate to Admin (System) > Target Platform Configuration
  2. The Metaswitch Platform Settings window is displayed

Configuring SIP Information

  1. Complete the following fields:
FieldDescription
SIP Server HostThe SBC address phones connect to
SRV Record
SIP Proxy Server HostTypically the same address as SIP Server Host
SIP Proxy Server PortCommonly 5060, though this varies by deployment

Configuring API Information

  1. Complete the following fields:
FieldDescription
API URLThe CommPortal login URL, unique to the reseller's EAS server
API VersionThe Metaswitch version, found in the PuTTY login or the Community Network Dashboard
API UsernameThe subscriber's phone number, noted above
API PasswordThe subscriber's EAS Password, noted above
  1. Select Save