TNG: No smdr/call details received - serial connection

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

TNG: No smdr/call details received - serial connection

Postby Belinda Frick » Thu Mar 29, 2012 12:38 pm

TNG is configured to receive call details/smdr via a serial cable form the PABX unit. However, calls are not upating to the 'Call List' page in TNG.

How do I check if the PABX is sending the smdr/call details and if TNG is receiving it?

  • The PABX sends off the call details via serial cable:

    • TNG (with buffer):
      check that the serial cable is connected between the PABX and the PC (where the buffer is connected to.
      the buffer must be connected via USB cable to the TNG PC.
    • TNGLive:
      check that the serial cable is connected, directly to the TNG PC.
  • Enable permanent logging of rawdata. This will allow you to see if raw data is received from the PABX.

    If so, ensure the rawdata is in the standard output format and if you have the correct version of the plugin loaded. You can search the forum for your PABX brand and model.

  • If no rawdata is written out, stop the TNG service

    How do I stop/start the TNG service in Windows?

    and connect directly to the port (where the serial cable connects) using HyperTerminal or Putty (please disconnect the TNG buffer beforehand). See: How do I enable logging of data in Putty?

    If you are still not receiving call details, you need to log a call with your PABX support company/technician.

    These are some of the 'normal' problem areas and must be checked:
    - the cable,
    - pc/pabx comport
    - pabx has a problem sending off call details.

    If you receive call details while and you the buffer is disconnected, then it could be a buffer setting problem or the problem could be with the actual buffer. See My TNG buffer is not being detected
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

cron