Activating the Switchboard

This page reorganizes the operational steps for Activating the Switchboard.

The new switchboard is using the AMIRouter, so as first step, AMIRouter needs to be already configured. An additonal configuration in application.properties needs to be done

spring.datasource.database=asterisk

spring.datasource.url=jdbc:mysql://localhost:3306/asterisk?zeroDateTimeBehavior=convertToNull

spring.datasource.username=asterisk

spring.datasource.password=asterisk

spring.shell.command.quit.enabled=false

server.ssl.enabled=true

server.ssl.key-store=/usr/local/amirouter/certs/keystore.p12

server.ssl.key-store-password=tomcat

server.ssl.key-store-type=PKCS12

server.ssl.key-alias=tomcat

The keystore needs to be configured with a valid SSL certificate using the following command

cd /usr/local/amirouter

mkdir certs

cd certs

openssl pkcs12 -export -in fullchain.pem -inkey privkey.pem -out keystore.p12 -name tomcat

I suppose you noticed the keystore password is tomcat

You need to configure in Admin/Settings the URL the switchboard should connect to talk with the AMIRouter websocket part. You need to use something like pbx.yourdomain.com:8080 and activate the SSL

The switchboard is not yet ready for prime time, so it is not directly accessible from your web interface, but you need to manually enter the URL, like https://pbx.yourdomain.com/pbx/the related application page and authenticate using an user account (the one defined in the Configuration/Extension)

Current Verification

After applying the change, verify the related MiRTA PBX page, the Asterisk logs, and the relevant Status menu entry. Recheck tenant selection before testing tenant-specific behavior.