TNG not connecting to SMDRLink on TCP

[GreggB]

2012-08-30 10:15:03:272 [1.1.0.5] - ConnectToNetworkPABX: Host[172.18.6.6] Port[2600]Socket Error # 10038[13][10]Socket operation on non-socket.
2012-08-30 10:15:03:377 [1.1.0.5] - ConnectToNetworkPABX: Host[172.18.6.6] Port[2600]Already connected.
2012-08-30 10:15:04:373 [1.1.0.5] - ConnectToNetworkPABX: Host[172.18.6.6] Port[2600]Socket Error # 10038[13][10]Socket operation on non-socket.


Amethyst SMDRLink Version 1.6.3.7

C:\Users\Gregg>telnet 172.18.6.6 2600
Connecting To 172.18.6.6...Could not open connection to the host, on port 2600: Connect failed

[Belinda Frick]

With your setup SMDRLink receives call details from the PABX via serial cable. TNG connects to SMDRLink via TCP port.

The preferred setup is always that TNG connects direct to the PABX so that it is not dependant on other software. Since TNG is on a virtual machine, you cannot use the serial port option to connect TNG direct to the PABX.

Please do the following:

• TNG
  
  
  • Please upgrade you TNGLive to the latest version - see forum post:
    Where do I find the latest version of TNGLive(Windows)?
    
    The link also includes the release notes for TNG 1.1.1.8.
    
  • Note TNG has the feature to alert you if no call details has been received for a configured period within your office hours, please refer to forum post: TNG Alarm Configuration (TNG v1.0.6.5 or newer)
    
    TNG will then notify you if no call details was received from SMDRLink. You need to then investigate:
    
    • why the connection to SMDRLink is not working or
      How do I check if the SMDRLink TCP port is sending off data?
    • if SMDRLink stopped receiving call details.
  
  
• SMDRLink
  
  There is a known issue where SMDRLink can 'loose' the TCP connect settings. If SMDRLink is receiving call details, but TNG cannot connect to it or does not receive call details please do the following:
  
  
  • Stop the TNG service (so that it does not try to connect to SMDRLink)(.
  • Log into AMETHYST webadmin and stop/start SMDRLink.
  • Log into SMDRLink:
    
    • confirm that you are receiving call details from the PABX (set to log rawdata).
    • confirm that you settings did not change to default values (for example TCP port, etc.). If so, please correct settings and click on APPLY. After the settings was saved double-check that it did not change again. If so, please correct it again and save and check that it saved.
  • If SMDRLink is receiving call details and the TCP settings is displayed, you can start the TNG service.
  • Log into TNG and confirm the network settings to connect to the SMDRLink TCP port.
    To configure network connection see forum post: TNG and a network PABX
  • Go to the TNG Call List page and see if you now are receiving call details. If not, check the log files for clues to proceed. You might have to repeat the process.
  
  NOTE: I would always suggest that SMDRLink is configured to log rawdata. If any connection problems, etc. you then have the option to imported the rawdata into TNG. - see forum post How do I import rawdata into TNG?. The import option is only available for TNGLive Premium.

[Belinda Frick]

Did the steps resolve you TCP connect issue? Do you need any further assistance?