Mitel MVO barring service

,

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.

TES Company Branch Settings

  • 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 ID value from the ircrecporter, from the INI file.
    Run this on the server where the barring will take place:
    grep "^ID=" /opt/datatex/ircexporter/ircexporter.ini

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

MVOBarring service

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

[OPTIONS]
BARRINGINSTRUCTIONPATH=/opt/datatex/irecexporter/instructions/

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

Add the following to the config file:
/opt/datatex/bin/check_running_apps.local

These are the commands to allow Check_running_apps.sh to check for 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.

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//