Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

On this page

📋 What’s about

To use XCALLY Mobile App, it is necessary to configure your own push gateway by following these guidelines and when you create Mobile Agents in Staff Section you will need to specify your Push Gateway Address (we'll see in this guide what settings to enter based on the scenario you choose)

The XCALLY Push Gateway, consists of 4 modules:

  • Stack SIP (Drachtio): the element that works as a “proxy” : Via SIP comes the registration from a mobile phone and the push gateway takes the register notification and sends it to XCALLY server, which responds to push gateway and push gateway responds to mobile

  • Push Notification system: when the app is in the background, the call comes to XCALLY and it's necessary to resume the app to manage the call. So there is a notification system that contacts Apple Push Notification which sends a notification to the agent's mobile. Device receives the Push Notification and agent accepts it

  • Redis Cache used to keep in memory foreground and background devices there is cache system

  • Redis Insight: cache dashboard to view what is in the cache. By default dashboards are installed, you can hook up your database, and if you have mobiles connected on db, you will see them on the dashboard

These 4 modules are run through the docker, so container where the application runs regardless of the operating system.
Since you need to run multiple containers, it’s possible to use docker compose: you define the containers to run (with their variables, ports...) and launching docker compose file (available below) the 4 modules will be executed automatically. So in next sections you can find instructions on how to install the docker-compose.yml file

🔧 Scenarios

Firstly you have to choose if you want to install the push gateway:

METTERE IMMAGINI

▶️ Common commands for the 2 scenarios

🛑 How to stop the containers

To stop and remove the containers (preserving the data), run the following command in the same directory as the docker-compose.yml file:

docker compose down

image-20240614-074359.png

This command will stop and remove all containers associated with the docker-compose.yml file.

These instructions should guide you through the process of running the provided docker-compose.yml file.

If you encounter any issues during the execution or have additional questions, please don't hesitate to ask for assistance.

Otherwise, to remove the whole stack (including data):

docker compose down -v

image-20240614-074248.png

Instead, to remove the single container:

docker compose down <service name>

image-20240614-074107.png


➡️ How to restart the container

docker compose restart <service name>

<service name> is the name assigned within the docker-compose.yml e.g. service drachtio

image-20240614-073824.png

To recreate the single container:

docker compose up <service name> -d

image-20240614-074154.png

👁️ How to view logs or status

To view container logs:

docker logs <container name>

image-20240614-073850.png

To view container status:

docker stats

image-20240614-073151.png

To access a container:

docker exec -ti <container name> /bin/bash

To exit the container, type exit.

image-20240614-073957.png

  • No labels