# Deploying an Issabel Server to AWS and using it with the Agent Assist Demo

# 

Now that you have deployed our Amazon  Chime Transcription and Agent Assist solutions, you will proceed to deploy a Unified Communications System to the cloud to test your solution.

Keep in mind that the following guide’s intention is to provide a testing environment and this isn’t by any means a recommended production environment as the resources are estimated for low load, and, the architecture is not designed to accommodate production workloads. Always when designing your architecture refer to the [_Well Architected Framework_](https://aws.amazon.com/architecture/well-architected/).

Issabel is an open source Unified Communications system based on Asterisk. You can find more information on [_https://issabel.org_](https://issabel.org/)

For this portion of the process you are going to deploy an EC2 instance with a Centos 7 AMI, execute the Issabel netinstall script, provision an Amazon Chime phone number and create a SIP trunk between Amazon Chime and your Issabel System.

### Deploying the EC2 Instance

You are going to deploy an EC2 instance with a Centos 7 AMI.

1. Click on “Launch Instance”:
![](images/daa_image_1.png)

2. Search for the Official Centos 7 AMI on the AWS Marketplace, which is [_Free Tier_](https://aws.amazon.com/free/) eligible:

![](images/daa_image_2.png)

3. In this case I will run a t2.micro instance, which for testing on 2 SIP channels (the incoming call and a SIP extension that will simulate the agent) should be enough.

![](images/daa_image_3.png)

3. Follow the standard procedure to launch the instance.

5. Keep in mind that for the CentOS ami the default username is “centos”.

6. Once your instance is ready we will need to configure your security group to open Port 22 and 443 for Issabel setup and the required ports for the Amazon Chime SIP Trunk.

You can find Amazon Chime’s full list of ports requirements [_here_](https://docs.aws.amazon.com/chime/latest/ag/network-config.html).

Since I’m running on the us-east-1 region, I will be using the following settings:

|A	|Source	|Port	|
|---	|---	|---	|
|SSH	|Your IP	|TCP/22	|
|---	|---	|---	|
|HTTPS	|Your IP	|TCP/443	|
|Test Softphone	|Your IP	|ALL UDP	|
|	|	|	|
|Amazon Chime / Signaling	|3.80.16.0/23	|UDP/5060	|
|	|	|TCP/5060	|
|	|	|TCP/5061	|
|Amazon Chime / Media	|3.80.16.0/23	|UDP/5000:65000	|
|	|52.55.62.128/25	|UDP/1024:65535	|
|	|52.55.63.0/25	|UDP/1024:65535	|
|	|34.212.95.128/25	|UDP/1024:65535	|
|	|34.223.21.0/25	|UDP/1024:65535	|

It is strongly discouraged to open your security group to any IP address, keep in mind to keep open only the necessary ports.

This is what your inbound rules for your Issabel instance should look like:

![](images/daa_image_4.png)

### Installing Issabel

Now that you have our instance ready and that you have configured our security group, you will ssh into, remember the default username for the Official Centos 7 is “centos” .

1. After you logged into your instance, you will update the OS and execute the [_Issabel_](https://sourceforge.net/projects/issabelpbx/) netinstall script.

`sudo yum update -y`
`sudo yum install wget -y`

2. After you have your tools ready, elevate your user to root and execute the netinstall script:

`sudo su`
`wget -O - [**_http://repo.issabel.org/issabel4-netinstall.sh_**](http://repo.issabel.org/issabel4-netinstall.sh) | bash`
![](images/daa_image_5.png)

3. Follow the installation steps.

![](images/daa_image_6.png)![](images/daa_image_ .png)Once the installation process finishes you will be able to login into your Issabel, the default username is “admin” and you have already set up the password during the installation:
![](images/daa_image_7.png)We will now go back to AWS console to setup the Amazon Chime Voice connector and the details for the SIP Trunk.

### Ordering a Phone Number for the Chime Voice Connector

1 On the left menu, click on Phone Number Management, then on Orders, and finally, on the Provision Phone Numbers button:

![](images/daa_image_8.png)

2. Choose “Voice Connector”.

![](images/daa_image_9.png)

3. Now its time to choose which phone number we would like to provision, you can either select by State and Location or you can enter a prefix, in my case I’d like a number on the Dallas Region. Select the number you’d like to provision and click provision.

![](images/daa_image_10.png)

4. You order will get into the processing stage.

![](images/daa_image_11.png)

5. After a couple minutes, the order status will change from Processing to Successful

![](images/daa_image_12.png)

### Creating a Chime Voice Connector

1. On AWS’ console we will search and click on Chime. Once on the Amazon Chime interface click on Voice Connectors and then on the Create Voice Connector button

![](images/daa_image_13.png)

2. For our next step we need to define a name for the Voice Connecotr, the AWS Region and if it will be encrypted. For our test we are going to Disable encryption, but it is highly encouraged that you enable encryption for production workloads.

![](images/daa_image_14.png)

3. After you enter the required information click on the “Create” button.

4. You will be taken back to the Voice Connectors list, we will click on the voice connector we recently created.

![](images/daa_image_15.png)

5. Click on Phone Numbers

![](images/daa_image_16.png)

6. Click on Assign from Inventory

![](images/daa_image_17.png)

7. Select the On the inventory list, select the number we just ordered and click on Assign from inventory.

![](images/daa_image_18.png)

### Setting up the Amazon Chime Connector for call Termination

Now that you have our Amazon Chime Connector configured, and a phone number assigned to it, you can setup the call termination and origination.

1. For the origination piece click on the Termination Tab, and click enable:

![](images/daa_image_19.png)

2. Take notes of the Outbound host name, we will need it for setting up our SIP trunk.

4. Under the Allowed hosts list, add your Issabel server's public IP addres and click “Add”.

![](images/daa_image_20.png)

5. For the calling plan we are going to select United States of America:

![](images/daa_image_21.png)

6. Next, you are going to create a set of credentials, under the Credentials section, click on New:

![](images/daa_image_22_.png)

7. Enter the username and password you will use to set up your trunk, and click Save:

![](images/daa_image_23.png)

8.Take note of the following fields:

* Outbound hostname
* Username and Password

9. Finally at the end of the form, click on Save.

### Setting up the Amazon Chime Connector for call Origination

1. Click on Origination at the upper tab of our Amazon Chime Voice Connector configuration screen.

![](images/daa_image_24.png)

2. Under Inbound routes click on “New”:

3. For host enter your Issabel’s server public IP, for protocol choose UDP on Port 5060, finally for weight and priority enter 1. After the information is entered, click on “Add”.

![](images/daa_image_25.png)

4. Click on Save.

### Enabling sending Kinesis Video Streams

The Amazon Chime Connector has the ability to send Kinesis Video Streams with the call audio, this will be the source of the audio used for our demo.

1. In order to enable Kinesis Video Streams, select Streaming on the top tab, and select Start under Details:

![](images/daa_image_26.png)

2. Also under Streaming notification, select EventBridge:

![](images/daa_image_27.png)

3. Click on the Save Button.

### Setting up the Amazon Chime Voice Connector SIP Trunk on Issabel

1. Login to your Issabel server,  by entering on using https:// followed by your Issabel server’s public IP on your web browser. 

You may get an alert that the certificate is not valid, this is normal as the certificate on the server is self signed. For a production workload your are highly encouraged to use valid certificates, for this task you may want to check [_AWS Certificate Manager._](https://aws.amazon.com/certificate-manager/)

2. After you have logged into your Issabel server, on the left menu, click on PBX, PBX Configuration:

![](images/daa_image_28.png)

3. On the new menu that will be displayed inside the frame, click on Trunks

![](images/daa_image_29.png)
4. Click on Add Sip Trunk

![](images/daa_image_30.png)

5. The trunk name can be anything, in our case AmazonChimeVoiceConnector.

6. For the Outbound CallerID we can use the format “Name”<+10000000000>, where 0000000000 is the number you just provisioned on the Amazon Chime side.

![](images/daa_image_31.png)

7. Under trunk name for outgoing settings I called it “ChimeOut”, also, here is where we are going to use the fields took notes from the termination portion of the Amazon Chime Voice Connector setup. This is what it looks like:

Trunk Name: ChimeOut

```
host=CHIME-OUTBOUND-HOSTNAME
username=USERNAME
secret=PASSWORD
type=peer
qualify=yes
```

![](images/daa_image_32.png)

7. For the Incoming settings, I used ChimeIn as the name for the trunk, and these are the contents:

User Context: ChimeIn

```
context=from-trunk
type=friend
insecure=invite
```

![](images/daa_image_34.png)

8. Click on Submit Changes on the bottom.

9. After the form is reloaded, you will see a pink ribbon with the message “Apply changes”, click on it.
![](images/daa_image_35.png)

10. You can check the current status of our newly created trunk by clicking under PBX, Tools, Asterisk-Cli and executing the following command:

`sip show peers`

![](images/daa_image_36.png)![](images/daa_image_ .png)

### Creating SIP extension for testing

1. You are going to click on PBX, PBX configuration, Extensions. On the Add an Extension screen, click on the Generic SIP device and click on the “Submit” button.

![](images/daa_image_37.png)

2. For user extension I’m using the number 100, for Display Name I’m entering Test Extension

![](images/daa_image_38.png)

3. Make user that under device options you set the nat option to Yes:
![](images/daa_image_39.png)

4. Click on Submit and then on Apply changes.

### Setting up an inbound route

Final step on the setup flow is to setup an inbound route that will route our incoming calls to the extension you just had setup.

1. In order to create an Inbound route, click on PBX, PBX Configuration, and in the internal menu click on Inbound routes:

![](images/daa_image_40.png)

2. Because we will only be getting calls for this demo, I will only fill the Description and will set up the destination as Extensions -> <100> Test

![](images/daa_image_41.png)

![](images/daa_image_42.png)

3. Click on Submit and apply changes.

### Creating an outbound route

You may also want to test our demo by dialing out, so we are going to create an outbound route.

1. Click on PBX, PBX Configuration and click on Outbound Routes:

![](images/daa_image_43.png)

2. Use the name ChimeVoiceConnector for the route:

![](images/daa_image_44.png)

3. For the Dial pattern, add + as the prepend prefix and 1XXXXXXXXXXas pattern for calls in the US. 4. This way you can dial the numbers without needing to add the +1 expected by Amazon Chime.

![](images/daa_image_45.png)

4. On the Trunk Sequence for Matched Routes, select the AmazonChimeVoiceConnector trunk.

![](images/daa_image_46.png)

5. Click on Submit changes and Apply changes.

### Setting up the external IP of our Issabel Server

1. Click on PBX, Asterisk Sip Settings:

![](images/daa_image_47.png)

2. Under NAT settings click on the “Auto Configure” button.

![](images/daa_image_48.png)

3. Click on submit and then on Apply Changes.

### Setting up a Softphone

For this stage you can use any IP Phone or softphone. In my case I will use Linphone an open source VOIP project.

1. After downloading and installing it you will set it up using my Issabel server’s IP as SIP domain, the extension number (100) as the username, and, the password you created for the extension.

2. In my case the configuration screen will look similar to this:
![](images/daa_image_49.png)