TAPI CALLER ID

Discussion in 'Windows' started by HannoBakkeren, Aug 4, 2008.

Thread Status:
Not open for further replies.
  1. HannoBakkeren

    Joined:
    Aug 4, 2008
    Messages:
    6
    Likes Received:
    0
    The "Notify tapi" option im my Voip client v6.0.727.0 does not pass caller id. I am using CallClerk, giving output below. Also tried Astice Tapi Monitor, no caller ID as well.

    Any suggestions?

    Thanks!

    (1) 4-8-2008 11:46:29
    TAPI reporting that a new call is arriving

    (2) 4-8-2008 11:46:29
    Connected

    (3) 4-8-2008 11:46:30
    The remote party has disconnected

    (4) 4-8-2008 11:46:30
    Disconnected

    (5) 4-8-2008 11:46:32
    Finalize Call
     
  2. HannoBakkeren

    Joined:
    Aug 4, 2008
    Messages:
    6
    Likes Received:
    0
    no, not working...

    the voip client popup works fine (even with call-groups etc) and does display the caller-id
     
  3. HannoBakkeren

    Joined:
    Aug 4, 2008
    Messages:
    6
    Likes Received:
    0
    i'm not sure what you mean by "tapi pop",

    situation is like this:

    The 3CX Softphone identifies the caller ID (external and internal calls), so I see the number in the client interface. I also see the number in the "Show Notification Popup"which I set under "Preferences" of the 3CX Softphone.

    A random TAPI monitor however doesn't get the caller ID, which the 3CX client should pass through to TAPI. The TAPI monitor does get the incoming call, but then almost immediate gets a disonnect. I read about PBX'es passing caller ID AFTER the first or second ring, so may be the 3CX client gives the "Disconnect" signal to fast to tapi?

    Is it working in your environment?

    Log from tapi monitor (CallClerk):

    (1) 4-8-2008 11:46:29
    TAPI reporting that a new call is arriving

    (2) 4-8-2008 11:46:29
    Connected

    (3) 4-8-2008 11:46:30
    The remote party has disconnected
     
  4. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,935
    Likes Received:
    250
    It has been tested with identapop and tapicall and it works. We have customer installs were it is working

    If you have a commercial package with tech support, please contact our support dept.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. HannoBakkeren

    Joined:
    Aug 4, 2008
    Messages:
    6
    Likes Received:
    0
    OK, will try those monitors. Not commercial yet, still testing.

    Thanks.
     
  6. HannoBakkeren

    Joined:
    Aug 4, 2008
    Messages:
    6
    Likes Received:
    0
    Tried TAPI call and it works, thanks! Will go on to buy the product now.
     
  7. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,935
    Likes Received:
    250
    good to hear that :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. HannoBakkeren

    Joined:
    Aug 4, 2008
    Messages:
    6
    Likes Received:
    0
    Hmm, still strange. Now using identapop (and just now Tapicall).

    Using the client in "Headset Mode" gives correct caller ID:

    10:55:06:400 CallState [105506] = CONNECTED
    10:55:06:416 TAPI OnCallerID (8)
    10:55:06:728 Examining: LINECALLINFO (8)
    10:55:06:743 Caller Name: Missing
    10:55:06:759 Caller Number: 003162442162x

    Changing the client to "Desk Phone Mode" gives "Dn1" as caller id..... (everything the same except for voip client mode):

    10:58:32:475 CallState [105832] = CONNECTED
    10:58:32:756 Examining: LINECALLINFO (8)
    10:58:32:756 Caller Name: Missing
    10:58:32:772 Caller Number: Dn1


    This has been tested as well?
     
Thread Status:
Not open for further replies.