Skip to main content
Skip table of contents

CX Voice Upgrade to 4.5.1

Voice Connector

  1. SSH onto the Debian server on which the Voice connector is installed.

    1. Use command

      CODE
      ssh <username>@<server-ip>
    2. Enter user password and press ENTER.

    3. Use command

      CODE
      su
    4. Enter root password and press ENTER.

  2. Run the command to see the list of running containers

    CODE
    docker ps
  3. Note the container ID of the current deployed 4.5 Voice connector.

  4. Note the port of that container i.e. for 0.0.0.0:8116->8080/tcp, :::8116->8080/tcp, the port of the container is 8116.

  5. Run the command to stop the container

    CODE
    docker stop <container-ID>
  6. Run the command to remove the container

    CODE
    docker rm <container-ID>
  7. Navigate to the folder where the docker-compose.yml and env.txt files are located for the voice connector.

  8. Open the docker-compose.yml file and replace the text inside with text below:

    CODE
    version: "3.8"
    services:
      voice-connector:
        image: gitimages.expertflow.com/freeswitch/ecx_generic_connector:4.5.1
        container_name: unified-voice-connector
        ports:
          - PORT:8080
        env_file:
          - ./env.txt
        restart: always
  9. Replace the PORT keyword with the port noted above in step 4.

  10. Run the command

    CODE
    docker compose up -d
  11. Confirm that the docker container is running by using the command

    CODE
    docker ps
    Untitled-20240207-065334.png
  12. Confirm that the container is running correctly by opening the logs with command

    CODE
    docker logs -f containerID
    Untitled-20240207-065355.png

Media Server configuration

Scripts
  1. SSH onto the Debian server on which the Voice connector is installed.

    1. Use command

      CODE
      ssh <username>@<server-ip>
    2. Enter user password and press ENTER.

    3. Use command

      CODE
      su
    4. Enter root password and press ENTER.

  2. Confirm git is installed, and install it if is not.

  3. Clone the Media Server scripts repository:

    CODE
    git clone -b 4.5.1 https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/rtc/freeswitch-scripts.git
  4. Navigate to the cloned repository to access the files:

    CODE
    cd freeswitch-scripts
  5. Move hangup_event.lua to the Media Server scripts folder:

    CODE
    mv hangup_event.lua /usr/share/freeswitch/scripts/
    chmod -R 777 /usr/share/freeswitch/scripts/
  6. Move no-agent-available.wav to the Media Server prompts folder:

    CODE
    mv ivr_prompts/no_agent_available.wav /usr/share/freeswitch/sounds/ivr_prompts/
Changes in SIP Profile
  • Login to Media Server web interface. 

    • Open in browser: https://IP-addr, where IP-addr is the IP address of the Media Server.

  • Add the username and password that was shown upon installation of Media Server and press LOGIN.

  • Press the IP address in the top right and select the Domain created in the Domain creation section above:

  • Open SIP Profiles under the Advanced tab.

image-20240424-103707.png
  • Open the internal profile, scroll down to the ws-binding and wss-binding fields, and set their Enabled column values to True.

image-20240503-121016.png
  • Find the disable-transcoding field and its Value and Enabled columns to true.

  • Fine the nat-options-ping fields and its Value and Enabled columns to true.

  • Press the SAVE button on the top right.

  • Open SIP Status under the Status tab.

  • Locate the line sofia status profile internal and to its right press the RESCAN button, followed by the RESTART button after the page reloads.

image-20240503-121411.png
Changes in Media Server Config
  • Open /etc/freeswitch/autoload_configs/lua.conf.xml

  • Find the line near the end containing <!-- Subscribe to events -->  

  • Insert the following under it:

    CODE
    <hook event="CHANNEL_HANGUP_COMPLETE" subclass="" script="hangup_event.lua"/>
  • Run the command:

CODE
systemctl restart freeswitch
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.