Mitel MVO barring service

Telephone Management ( TNG and TES )
,
1

The Mitel MVO ( Old Aastra / MVO 400 range) supports integration via OpenApplication users.

We have created a barring service that allow the extensions or pin codes to be blocked from making calls when the budget for these users is exceeded.

This post will show how to setup

  1. The TCP Proxy to gather SMDR data from the PABX
  2. Process the SMDR data through TNGBuffer.
  3. Upload to TES iReCall
  4. Setup TES for barring
  5. Retrieve barring instructions from TES iReCall
  6. Process barring instructions via MVO Barring service.

MVO Barring Documentation file here

TES MVO400 Barring Service 1.pdf (1.1 MB)

This service will require:

  • A Datatex license based on the number of devices that needs to be barred.
  • Access to the MVO to setup the user account and SMDR upload to TCP Proxy service. The PABX provider will need to follow the steps in the attached document to complete this.
  • SMDR data to be captured via TCPProxy service and processed by TNGBuffer. The PABX vendor will have to setup the SMDR destination as the IP where the TCPProxy is running.
  • TES or TNG to process the SMDR and generate budget update info.

Barring via Remote TES

The following settings must be configured on the client’s TES Company Settings.

  • Enable the Budget feature
  • Set the Barring host to 127.0.0.1.
    This will not actually be used, but if the field is blank, then the barring will not execute.

TES Company Branch Settings
You will need to get the ircexporter ID from the INI file of the branch that is uploading the SMDR.
Run this on the server where the barring will take place:
grep "^ID=" /opt/datatex/ircexporter/ircexporter.ini

  • Create a branch for the site where the barring will take place. (if it doesn’t exist.)
  • Click on the Details link for the branch.
  • Set the Barring PATH to the ID from the ircexporter. (From the ircexpoter.ini file. )

The iReCall Exporter service will upload the SMDR to TES and download any barring commands to the folder /opt/datatex/ircexporter/instruction

If your instructions are not downloading, check that the ircexporter command to downloads the instruction files, is in the download script.
./ircexporter --download
must be at least the line above the upload command.

MVOBarring service

The barring service is configured to look for the files using this setting

[OPTIONS]
BARRINGINSTRUCTIONPATH=/opt/datatex/ircexporter/instruction/

Default INI

Default dtxmitelmvo.ini file:

[BUDGETING]
ADDRESS=127.0.0.1
PORT=25010
 
[LOGGING]
VERBOSE=0
 
[BARRINGMODE]
ACCOUNTS=0
EXTENSIONS=1
 
[MVO]
HOST=192.168.0.2
PORT=1131
USERNAME=datatex
PASSWORD=
USESSL=1
LICENSE=
BARSETTING=2
UNBARSETTING=1
SERIAL=
BARRINGRANGES=
 
[OPTIONS]
BARRINGINSTRUCTIONPATH=./instruction/
 
[TCP]
LISTENPORT=27985

This service will connect to the PABX and download all the extensions and show this info int he logs. There after there is a keep alive every 30 seconds to keep the connection up.

Service parameters:

  • –serial
    This will display the current system generated serial that will be used to match the license.

Startup

By adding the below section to the config file /opt/datatex/bin/check_running_apps.local it will be checked for auto starting.
This is the config to allow check_running_apps.sh to check and start the barring service.

#MVO Barring
APP=dtxmitelmvo
APPLOC=/opt/datatex/tesbarring/mvo400/
APPSTART=$APPLOC/startmvobarring
CheckAndStart $APP $APPLOC $APPSTART

iReCall exporter ( ircexporter)

This service uploads and downloads the files required for this facility to work.

Active upload of the data

  • Supply the ID from the ircexport to irecall@datatex.co.za with the client details that needs to be activated for uploads and prepare the instruction file creation for TES.

Upload TNGbuffer data

  • To gather the TNGBuffer logs, the script “/root/MyUpdates/irecall/move-tngbufferlogs.sh” needs to be copied to the folder “/opt/datatex/ircexporter/”
cp -i -v /root/MyUpdates/irecall/move-tngbufferlogs.sh /opt/datatex/ircexporter/
chmod +x /opt/datatex/ircexporter/move-tngbufferlogs.sh

This should not ask to overwrite a file. Say “N” and check the file that is already installed.

  • Set the CLIENTNAME at the top of the script.
  • Make sure the correct upload script is used for the ircexporter that checks if the move script is in place and runs it first.

Confirm with iReCall Admins if the upload folder was created on the iReCall Upload server: /opt/datatex/ircimporter/guid//

TES

Now that everything is setup, SMDR should be picked up from the PABX and uploaded to TES. The TES Barring facility will need to be enabled for the extensions that you need to bar and when they exceed their budget, the instruction file will be created to upload back to the client.

See this post for more details on the config:
TES User budget config - Telephone Management ( TNG and TES ) - Datatex Discourse