**How To:** Configure Metaswitch **Similar questions:** Configure Metaswitch, set up Metaswitch, configure Metaswitch with Xima CCaaS, set up Metaswitch with Xima CCaaS **Purpose:** Demonstrate how to configure Metaswitch # Getting Started Info Please be aware that you get the virtual handset extension information and password from your Metaswitch Provider. Also, note that this handset needs to have Voicemail Disabled. # Steps ## Platform Admin Portal Steps ### Create a UC Extension within the Admin Portal of your platform You will first need to create a UC Extension (subscriber) within the MetaView Web Portal. * **NOTE:** This is typically only accessible and available if you’re a reseller of Metaswitch. 1. Navigate to the MetaView Web Portal 2. Select the **Business Group > Lines > Add Line** {458}

Add Line button 3. Assign a license type to the new line * This can be from a predefined template (that may or may not exist within the portal), or created manually * For Xima CCaaS, the license type makes no difference as long as it allows for a SIP connection 4. Add a phone number and subscriber name * Example: “Xima Virtual Handset” 5. Add the extension under the Extensions tab as displayed in the image below. {1051}

Add Extension buttons ### Maximum Call Appearances 1. Open the new Subscriber you've just created 2. Under the **Connection** tab, adjust and verify the **Maximum call appearances** for your new extension that is acting as the Contact Center end-point 3. Please set the “Maximum Call Appearances” to an amount that the customer will not exceed, and notate for later steps * **NOTE:** This will be used within the Xima CCaaS Portal to dictate the "Total Channels Per Extension" setting {790}

Maximum call appearances setting location ### Configuration Menu Information 1. Navigate to the **Configuration** tab of your new Subscriber 2. Open the **Advanced** menu dropdown 3. Make sure that "User notification of call diversion" is selected {1700}

User notification of call diversion setting location 4. Notate the "Phone number" as this will be your "API Username" within Xima CCaaS 5. Notate the "EAS Password" as this will be your "API Password" within Xima CCaaS {1700}

Phone Number and EAS Password setting location ## Xima CCaaS Portal Steps ### Target Platform Configuration #### SIP Information 1. Once you are done with the creation of that subscriber, log in to the Xima CCaaS portal * To do this, navigate to Xima CCaaS with the URL that has been provided to you (E.g. **example.xima.cloud**) 2. At the login screen, enter your Username and Password and hit Login * **NOTE:** The first time you log in you may see an error message that appears at the bottom of the screen * This error simply means that Xima CCaaS is not connected to your platform yet. This is fine and is to be expected. 3. Once you are logged into the interface, select the **Settings** option (gear icon) on the left 4. Then select “Target Platform Configuration” 5. Fill out all of the SIP information * **SIP Server Host and SIP Proxy Server Host** * SBC Address, which is the address your phones connect to * **SIP Proxy Server Port** * Typically 5060, but does have some variance * **Total Channels Per Extension** * The default is whatever the re-seller sets it up as, but you’ll need to change the line appearances to account for more simultaneous calls * This information can be found under the [Maximum Call Appearances](https://guide.xima.cloud/docs/configuring-virtual-handset-on-metaswitch#maximum-call-appearances) {548}

SIP Platform Information #### API Information 1. Within this same menu, fill out the API information * **API URL** * This is the “CommPortal” Login * The URL will be unique to the Re-seller as this points to their EAS Server * **API Version** * This is found within the PuTTY Login or within the “Community Network Dashboard” (Portal used to log tickets) * It will need to match the version of Metaswitch to successfully complete the API request * **API Username** * This is the phone number of the Subscriber * It is found under the Configuration tab, as notated in the [Configuration Menu Information](https://guide.xima.cloud/docs/configuring-virtual-handset-on-metaswitch#configuration-menu-information) section above * **API Password** * This is the EAS Password * It is found under the Configuration tab, as notated in the [Configuration Menu Information](https://guide.xima.cloud/docs/configuring-virtual-handset-on-metaswitch#configuration-menu-information) section above * **NOTE:** This is not the "SIP Password" 2. Click **Save** {491}

API Information ### Manage SIP Extensions 1. Once done with that, click the gear icon again and select “Manage SIP Extensions” 2. Click the “+” button on the top right-hand side to add your extension * This is the [UC extension you set up previously](https://guide.xima.cloud/docs/configuring-virtual-handset-on-metaswitch#create-a-uc-extension-within-the-admin-portal-of-your-platform) to be used as the Xima CCaaS “Virtual Handset”, the same extension as the Subscriber 3. Within this new menu, fill out the SIP Extension information * **SIP Extension** * The extension of the user * **SIP User** * Subscriber phone number * **SIP Password** * The password used to register a third-party phone * **NOTE:** Not the EAS Password, but can be found under the **Connection** tab as seen below

SIP Password Location 4. Click **Save and Test** 5. Once properly filled out, wait a couple of minutes and the extension should show up as “Registered” within the "Manage SIP Extension" menu {584}

Edit Extension Menu > 📘 NOTE: > > If you have a single handset that is a part of 20 or more MLHG, your configuration will be slightly different and require that you create more handsets to handle Contact Center call traffic. This is an example of a site that requires routing of 40 differently MLHGs ![](https://files.readme.io/e8ac6b5-2023-01-10_14-02-04.png "2023-01-10_14-02-04.png") These extensions should be set up the same way as the article describes (unreachable number of line appearances, etc.) Once you have your extensions created, you are to point the MLHGs to the 2nd, 3rd, 4th, etc, extensions, NOT the top extension. With this configuration, the top extension is required to be there but doesn’t handle any traffic into the Contact Center. Each extension (2nd, 3rd, 4th, etc) can now handle the routing of up to 20 MLHGs. This setup and configuration will be unnecessary if you are routing through 20 MLHGs or below and should not be used otherwise.