How do I install TNG with Ericsson BP250 call barring?

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

How do I install TNG with Ericsson BP250 call barring?

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

Please note: The Ericsson BP PABX does not have the account code barring option. Virtual extensions are used. Please follow the setup instructions for the PABX configuration as required to do the barring via TNG.

What is required?

  • Datatex Software:

    • TNG TMS program version 1.0.7.0 or newer.

      For TNG 1.0.7.6 update see forum post - TNG: Why is my 8TA calls costing at zero?

    • Plugin required:
      Ericsson BP and virtual extensions/accounts for barring

    • TNG Call Barring software, tng-callbarring-install-1_0_1_18.exe or newer.

      Download, unrar - password is 'datatex':
      tng-callbarring-install-1_0_1_18.rar


      See install manual
      TNG CallBarring Installation Manual.rar
      Download and urar for PDF document.

    • DTX Ericsson BP barring interface,
      tng-EricssonBP-install-1_0_0_2.exe or newer.

      Download, unrar - password is 'datatex':
      tng-EricssonBP-install-1_0_0_2_callbarring_1_0_1_12.rar


      NOTE: If you use Ericsson BP 1.0.0.2, you must use TNGCallbarring version 1.0.1.12 or newer.
  • PABX:

    • Use standard output and certified plugin for BP.
      See forum post PABX3 Plugin: Ericsson BP settings to use Topaz

    • BP 50 or a BP 250 Release 15
    • Ericsson CLI format must be set to "CLI Hotel 3".
    • PC with BMS 3.3 installed as a service.

      Please note: The first time you connect to BMS, please do so manually. Take note of the connection time it uses to start up and connect. This will be dependant on the 'size' of the system (aswell as the processing speed of the PC it is running on).

      dtxEricssonService.ini:
      Code: Select all
      ConnectionIntervalMinutes=10
      SystemLoadTimeoutMinutes=5

      Please use the time of your system (as this may vary dependant on system size) and add about 2 min as the System load time, see explanation below:

      SystemLoadTimeoutMinutes=5
      Log into the BMS manually first and check the amount of time it takes for the full system load. The system must be started up and connected (System status = online ready) The SystemLoadTimeoutMinutes value needs to be more than the time it takes to load the data other wise it will always time out before the load is complete.

      ConnectionIntervalMinutes=10
      This is how often the Service will try and login to the BMS. Don't make this to little as it takes a long time to login and you don't want the service to be logged in most of the time, as it will lock the port for remote access.

    • The PC must have 2 COM ports to run both TNG and the BMS
      (if the BMS doesn't utilize a network connection)
      • 1 X TMS port setup for TNG
      • 1 X programming port


      Note: We suggest to use the TCP option, as the serial option can lock if the site is very busy. To use the TCP option you configure it in the BMS and you need an IPU card on the PABX.

      There will be a delay in updating the bar and unbar commands, because we must wait for 'Online Ready' which is after the system back, save and disconnect. This process must be followed because the session cannot stay open permanently (if open permanently no remote maintenance can be done on
      the PABX).


    • Extension barring:

      The bar and unbar level(COS) used in TNG must be setup on the PABX unit.
      The bar and unbar level(COS) used in TNG must work from the PABX unit.
      The Ericsson technician can test this with the interface connected to the Ericsson BP250 PABX unit.

    • Account Code barring (Virtual extensions):

      The PABX must be set to use a portable class of service, to change the facility cost on the extension.

      While the trail license is running, create 100 mobile extensions.
      Give them fictive numbers. Use these numbers to do portable COS.
      Setup the rest of the extensions to only dial speed-dial numbers. In other words create speed-dials to be used as account codes.
      Speed-dial overrides the barring, therefore need to change the facility COS to block it.
      Then program the string into a speed-dial number:
      *72*pin code*extension#.
      Set facility cost on trunks (this will allow dialing with speed-dial, without using an account code to dial).

      Note:Barring commands cannot be sent via the buffer.

      For detailed instructions download and unrar document:
      Ericsson_BP250_BP50_setup_account_codes.rar

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:
    [BUDGETING]
    Code: Select all
    ADDRESS=127.0.0.1
    PORT=25010


    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.

    For configuration of budget, etc. see TNG Callbarring install manual. Download and unrar the PDF document:
    TNG CallBarring Installation Manual.rar

  • DTX Ericsson barring interface: dtxEricssonService.exe

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

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

    dtxEricssonService.ini:
    Code: Select all
    [CONNECTION]
    SERVER=127.0.0.1   {do not use the URL from the BMS server, only the IP}
    USERNAME=admin
    PASSWORD=default
    SYSTEMNAME=ERICSSON
    ConnectionIntervalMinutes=10
    SystemLoadTimeoutMinutes=5

    [BARTYPE]
    TCD=1

    [BUDGETING]
    ADDRESS=127.0.0.1
    PORT=25010

    [SETTINGS]
    BLOCKCOS=8
    UNBLOCKCOS=1
    VERBOSE=1


    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 and connected.

    barring command added to queue of dtxEricsson service to send to PABX:
    Code: Select all
    [2009-09-07 06:41:16] AddCommandToQueue:C:EXT|8025|8


    Unsuccessfull attempt to send barring command from dtxEricsson service to PABX:
    Code: Select all
    [2009-09-07 06:41:16] AddCommandBackIntoQueue:C:EXT|8025|8


    Global Reset:

    the dtxCallBarring unbar command is logged in the dtxEricssonService as:
    Code: Select all
    AddCommandToQueue:C:EXT|208|3!


    the dtxEricssonService unbar to the PABX is logged as:
    Code: Select all
    [2007-12-17 18:27:09] Going to connect now
    [2007-12-17 18:27:09] Connected?
    [2007-12-17 18:27:09] Connected to Web server
    [2007-12-17 18:27:09] Going to talk now
    [2007-12-17 18:27:10] Going to select session now etc.
    [2007-12-17 18:27:17] Going to set EXT:208 to COS:3 now
    [2007-12-17 18:27:18] COS changes of ext : 208

Trouble shooting:

  • If your budget is updating in TNG Call Barring, but it does not bar or unbar the extension check the communication between TNGCallBarring and the BP barring service:

      dtxCallBarring is communicating with the BP Barring Service on port 25010.
      To check if dtxCallBarring is sending to the BP Barring Service:
      • Close the BP 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.
    • The logs for dtxCallBarring is in:
      C:\Program Files\Datatex\TNGCallBarring\Audit (audit trail of budgeting)
      C:\Program Files\Datatex\TNGCallBarring\Serverroot (dtxCallBarring service entries)

      Note: Verbose logging is enabled by default. If you stop and start the service, you must have entries in the serverroot logs. If not, it could be access issues. A service runs as System and should not have access issues unless site specifice policies are in place. IT department will need to assist you with this.


    • If the dtxCallBarring is sending the information to the Ericsson BP barring service, you need to check the updating between the Ericsson BP barring and the PABX (via BMS). See above log entry examples for global reset and unbar.

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

    • dtxEricssonService.log: going to refresh page now

    • Also note that once the budget is reached, each time a call is made it will attempt the barring. You can pick this up in the audit trail(dtxCallBarring) and then in BP Barrring service logs. If the BP barring service cannot connect to the PABX, then no bar/unbar will take place.
      • Make sure that a fire wall/proxy is not blocking communication (allow ports and services, etc.).
      • If anti-virus software is running allow all the services and the BMS.
      • See above for 'ConnectionIntervalMinutes' and 'SystemLoadTimeoutMinutes' settings.

NOTE: to have access to the attachment, you need to be registered and logged in.
You do not have the required permissions to view the files attached to this post.
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