In TNG Call barring all my ports shows not connected

[Belinda Frick]

TNG services

• TNG TMS program version: TNG.exe
  
  • TCP Port 20003 export port
  
  
• TNG Call Barring software: dtxCallBarring.exe
  
  • TCP Port 20009 barring port
• Barring software for your PABX:
  DTX Ericsson barring interface: dtxErcServMX.exe
  DTX Ericsson barring interface: dtxEricssonService.exe
  DTX Aristel barring interface: AristelBarring.exe
  
  • TCP Port 25010 port

To check:

• Check the firewall settings allows the TNG services(and BMS for BP barring).
  
  START -> CONTROL PANEL -> WINDOWS FIREWALL -> ALLOW PROGRAM THROUGH WINDOWS FIREWALL
  Tick program if listed, else click on ADD PROGRAM and browse to exe to select:
  
  
  WindowsFirewall.jpg
  
  
• Check the proxy settings allows the TNG services(and BMS for BP barring).
  
  
• If you have anti-virus software also allow the TNG services(and BMS for BP barring).
  
  Each anti-virus software settings will differ. Also include the services as per your barring solution (PABX specific).
  
  For example: Microsoft Security Essentials:
  
  
  • Settings -> Exclude Files and Locations:
    
    
    • browse to the TNG folder and select it - click on ADD
    • browse to the TNGCallbarring folder and select it - click on ADD
  • Settings -> Exclude: Processes:
    browse to the DATATEX folder and select it - click on ADD
    This is to exclude the recording software exe's (tng.exe/tngcallbarring.exe/dtxEricssonService).
  
  
• You can also run "netstat -nba" to see which process has a port open.
  
  

  Code: Select all

    Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:3050           0.0.0.0:0              LISTENING       3000
  [fbserver.exe]

  TCP    192.168.15.96:139      0.0.0.0:0              LISTENING       4
  [System]

  UDP    0.0.0.0:2529           *:*                                    200
  [Onyx_Sweeper.exe]

  UDP    0.0.0.0:27004          *:*                                    200
  [Onyx_Sweeper.exe]


  
  Ensure that the TNG ports are available and not in use by other software.

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. This will then cause the barring service to get
information again (simular to a restart).

The TNG Callbarring install, tng-callbarring-install-1_0_1_17.exe, did not
include some files, which caused the NOT CONNECTED display error. Note that if
used as an install you would have this issues, but with an update it would work.