Problem with getting a TAPI driver to work with ACT! on Windows XP pro

Hi,

I don't know if there is anyone out there with the relevant expertise.

We need a mix of Telecomms, Windows XP and Sage ACT! programming.

We have the following situation.

We have just installed a new PABX (LG IPLDK20).

We run ACT! 2009 v11 on a Windows XP Pro Service Pack 3

We have also purchased the DialIt for ACT! package

In simple terms we cannot get the system to work together. We have had it working perfectly for one full day, but then when we rebooted the next day it stopped working.

We have tried it on several PCs and have the same problem.

We also have the DialIt for Skype package and this works perfectly.

We need someone who has real expertise of:

Windows XP

TAPI and TPS drivers

Working with modern PABXs

ACT! administration

We've tried everything we can think of and basically run out of ideas, so any help would be much appreciated.

Many thanks
Chris
Chris_RyanAsked:
Who is Participating?
 
Mike LazarusConnect With a Mentor Act! Evangelist - CRM ConsultantCommented:
Have you installed the TAPI driver in your Windows locally (first-party control)? DialIT needs that

You should first try the Phone.exe test ... download Phone.zip from the bottom of:
http://www.glcomputing.com.au/main/56/1
Follow the instructions and see if it can make a call and identify the number on an incoming call

The great thing about Phone.exe is that you can give it to the phone guys to test what PABX config works, without them needing ACT! or Dial
0
 
Chris_RyanAuthor Commented:
Thanks so much

We have tried assigning both third party and first party control.

We have also tried Phone.exe.

We have also been doing some further research.  The main issue appears to be that the PC cannot see the PABX.

On the couple of occasions that the system has worked the Phone.exe works ok.  We think the DialIt is a red herring because we also tried a PC without ACT/DialIT, just using Outlook, with exactly the same results.

When we reboot the PC the next day we lose the connection and we just can't seem to be able to get it back no matter what we do.

Our current feeling is that it has something to do with the local PCs not holding either the TAPI or the TPS and our feeling is that it is TPS related, but we honestly have no real idea of where to take it from there!!

Any help or advice as to where to go would be much appreciated

KInd regards
Chris

0
 
Mike LazarusAct! Evangelist - CRM ConsultantCommented:
I would contact LG or your phone reseller....
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
Chris_RyanAuthor Commented:
Thanks

We have tried contacting both parties, but we are caught in the classic trap of everybody saying it is not their problem and pointing at everyone else :(

We need to get hold of a real expert
0
 
Mike LazarusAct! Evangelist - CRM ConsultantCommented:
Well, you've verified that it must be the phone system or driver already ... so how can either party say that?
0
 
Chris_RyanAuthor Commented:
Because I can't prove where the fault lies and they won't take responsibility for their drivers if they think it might be a Windows TAPI driver issue or other network related problem.
0
 
Mike LazarusAct! Evangelist - CRM ConsultantCommented:
Do they not have their own TAPI driver?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.