How do I install TNG with Ericsson MD110/MX1 call barring?

Moderators: Leon van Heerden, Luanda_Junzi, Belinda Frick, Lee Hendricks

How do I install TNG with Ericsson MD110/MX1 call barring?

Postby Belinda Frick » Mon Nov 15, 2010 2:16 pm

What is required?

    Datatex Software
    • TNG TMS program version 1.0.7.0 or newer.
    • TNG budgeting software, tng-callbarring-install-1_0_1_18.exe or newer.
    • DTX Ericsson MX barring interface, tng-EricssonMX-install-1_0_1_10.exe or newer.
    PABX:

    MD110 with Software level 12.1 with Service Pack 7 or newer.
    MX1 Service Pack 3 or Release 13.

    Use standard output and certified plugin for MD110 BCM 12.

    NOTE: These settings are required to be able to use TNG in conjunction with the MD110.

    The MD110 by default doesn't report incoming and outgoing line numbers.
    With the following format all the line numbers and account codes are reported:


    Code: Select all
    CLTGE;
    CLOHE:FILE=CUSTOMER;
    CLODE:FILE=CUSTOMER;

    CLFOC:FORM=4,DATA=1-3M&2-4J&3-4P&4-1M&5-5K&6-1M&7-3X&8-2M&9-2I&10-1M&11-5A&12-3S&13-9T1&14-2M&15-9T2;
    CLFOC:FORM=4,DATA=16-2M&17-14G&18-2M&19-10E&20-7D&21-6F&22-9T&23-10E1&24-10G1&25-10G2,APPEND=YES;

    CLOHI:FILE=CUSTOMER,FORM=4,DMPSIZ=1,LOGABN=YES;
    CLODI:FILE=CUSTOMER;

    CLFOP;
    CLTGI;



    Ensure that the resolution is set to 1 second:

    Code: Select all
    ASPAC:PARNUM=122,PARVAL=1;


    This will ensure that the call duration is reported in Hour:Minute:Second notation.

    Barring must be configured on the PABX as per PABX requirements.

    NOTE: The barring works with the MD110 and the MX1, but has not been tested with the MX1 server.
    Barring commands cannot be sent via the buffer.

Data Flow:

  • TNG TMS program:

    TNG must have the TNG buffer connected,
    else it will not import any calls.
    The buffer is connected to the PABX for SMDR data.


    Pin codes and the user is configured in TNG and 'passed' to
    the TNG Call Barring software.

    TNG Call Barring software: dtxCallBarring.exe

    Configure to communicate with Ericsson barring interface via port 25010.

    This setting must match Ericsson barring ini extract:
    Code: Select all
    [BUDGETING]
    ADDRESS=127.0.0.1
    PORT=25010


    dtxCallBarring.ini
    Code: Select all
    [WEBSERVER]
    WEBPORT=7081

    [TNG]
    PORT=20003
    HOST=127.0.0.1

    [SETTINGS]
    EXTMODE=1
    DEFAULTBUDGET=0
    SEQ=0

    [SYNC]
    PORT=20009

    [BARRING]
    PORT=25010

    [GLOBALRESET]
    DAYOFMONTH=-1
    LASTRESET=


    The budget for each user must be configured in the TNG Call Barring software.

    Note: If the default budget for an account or extension is zero, then it
    will be ignored. If your global default budget or department budget is zero and the
    individual budget has an amount, it is enabled.

  • DTX Ericsson barring interface: dtxErcServMX.exe

    Installed by default in: C:\Program Files\Datatex\EricssonMX

    Configure the Ericsson barring interface to connect via comport or TCP to the
    PABX to send the bar/unbar commands.

    Ericssonbarring.ini:

    Code: Select all
    [BUDGETING]
    ADDRESS=127.0.0.1
    PORT=25010

    [COMMUNICATIONS]
    COMPORT=COM1
    BAUDRATE=9600
    PARITY=none
    LENGTH=8
    STOPBITS=0
    EOLCHAR=10
    hwUSEDTR=1
    hwUSERTS=1
    hwREQUIRECTS=0
    hwREQUIREDSR=0
    swNONE=0
    swTRANSMIT=0
    swRECEIVE=0
    swBOTH=0
    swXON=17
    swXOF=19
    ACK=0
    DisconnectWhenIdle=1
    MD110AlternativeBarring=0
    USETCP=0

    [LOGGING]
    VERBOSE=1

    [BARRING]
    BLOCKCOS=8
    UNBLOCKCOS=1

    [GENERAL]
    UPDATESPEED=2

    [PABX]
    ADDRESS=127.0.0.1
    PORT=23

    [Access]
    Login=MDUSER
    Password=HELP


    Please Note: The UPDATESPEED setting in the settings file is the number of seconds
    to wait between sending commands to the pabx. This is now enabled for TCP as well.
    It will default to 2 which we think should be ok, but you can make it longer.


    The Datatex Ericsson MX barring service will create the file AccountCode.dat.
    You need to manually edit it and add accounts in the following sequence
    Code: Select all
    CIL=PIN=COS

    3000=1234=1
    4000=1111=8


    Note: In the above example
    3000 is the value given off by the PABX as the Account in TNG and
    1234 is the index and
    1 is the class of service for this account.

    Log into TNGCallbarring with admin login.
    Go to General Setting page.
    Click on 'Configure' button next to 'Barring Service'.
    Under Configure Barring Settings in the AccountCode section
    enter all the account codes as per example (CIL=PIN=COS)
    Click on Apply.

    It will also write out an entry in the log file if the accounts were setup incorrectly.

    Format of [Accounts] is CIL=AUTHCODE=CAT

    The limits for the codes is as follows:
    CIL is 6 digits
    Auth code is 7 digits
    CAT is 0 to 63.


    Please Note: TNG, TNG CallBarring and the DTX Ericsson Interface runs as Services on the TNG PC. Please ensure that all the services are running. If they are running (TCP connect is up) then when you log into TNG CallBarring as admin you can see the status of the services.
Communication between services:

    TNG is sending the Call details to dtxCallBarring on TCP port 20003.
    To test if TNG is sending to TCP port 20003, request the TCPServer from
    support@datatex.co.za. Only TNG must be running, stop the dtxCallBarring service.

    TNG is sending the User/Extension details to dtxCallBarring on TCP port 20009.
    To test if TNG is sending to TCP port 20009, request the TCPServer from
    support@datatex.co.za. Only TNG must be running, stop the dtxCallBarring service.

    Note: If the service is restarted or apply then dtxCallBarring will sync with the barring service of the PABX (in this case the MX1 barring service). This will then cause the barring service to get information again (simular to a restart).

    dtxCallBarring is communicating with the MX1 Barring Service on port 25010.
    To check if dtxCallBarring is sending to the MX1 Barring Service:
    Close the MX barring service (only TNG and TNG barring must run)
    run a telnet 127.0.0.1 25010

    Note: The TNG Barring display will now show 'Connected'.


    If you get an error with the telnet,
    please run the following command in the command prompt,
    netstat -nba.
    Check for TCP and port 25010, it will list which application is using it.
    make a test call.
    TNG must update on the Call List page.
    TNG Call Barring must show the test call (update budget).
    The telnet session should receive an encrypted string.

    Global Reset:
    the dtxCallBarring sent the unbar command it is logged in the MX1 service as:
    Received command from TNG CallBarring.
    the MX1 service send of the unbar command to the PABX is logged as:
    SENT MSG TO PABX:

    Note: the barring service must be set to verbose logging to see the global reset entries.

    Communication between dtxEricssonService and the Ericsson MX1 PABX.

    Successfull connect

    Code: Select all
    Before Service Pack 6, on login the MX1 reply with

    (C)  COPYRIGHT ERICSSON
    [2009-02-27 07:57:16] SENT MSG TO PABX: HELP;
    [2009-02-27 07:57:16] Receive from PABX:      AUTHORITY CLASS   7
    [2009-02-27 07:57:16] Receive from PABX: (C)  COPYRIGHT ERICSSON 
    [2009-02-27 07:57:17] Receive from PABX:      LABOUR2         27FEB09    07:52:29       1-0-60-03 SYSTERMINAL
Belinda Frick
 
Posts: 3808
Joined: Fri Nov 12, 2010 4:25 pm

Return to Support Archive's (TNG)

Who is online

Users browsing this forum: No registered users and 1 guest