TAPI sample application not connecting to IP OFFICE 2

[arunknair82]

i was testing the TAPI SAMPLE (from devconnect )application to make calls and for an integration via url with customer CRM and it worked fine on my LAB IP office
When i tried the application in another site the application is not taking the agent extension as usual
IPO Rel 9.0.0.829
TAPI2 installed on the PC
User logged in Ip Phone
Advanced edition and CTI pro license installed on IPO and status is Valid,

user with password configured on IPO and Same user configured on the Avaya Tapi provider in phones and modem option as single user.
When i open the tapisample application it should show the agent extension number which is not happening, same application working fine in LAB ip office
I set a log for TAPI and i am getting the following

28/07 14:23:33 : TUISPI provider config - Makedlg...

28/07 14:42:54 : TUISPI_providerRemove
28/07 14:43:04 : TUISPI_providerInstall. Provider ID = 6
28/07 14:43:08 : TUISPI provider config - Makedlg...

28/07 14:58:01 : TUISPI provider config - Makedlg...

28/07 15:04:42 : TUISPI_providerRemove
28/07 15:04:48 : TUISPI_providerInstall. Provider ID = 8
28/07 15:04:49 : TUISPI provider config - Makedlg...

28/07 15:07:04 : TUISPI_providerRemove
28/07 15:07:08 : TUISPI_providerInstall. Provider ID = 9
28/07 15:08:25 : TUISPI provider config - Makedlg...

28/07 15:10:00 : TUISPI provider config - Makedlg...

28/07 15:12:56 : TUISPI provider config - Makedlg...

28/07 15:13:52 : TUISPI provider config - Makedlg...

28/07 15:19:16 : TUISPI provider config - Makedlg...

28/07 15:21:06 : TUISPI provider config - Makedlg...

What could be the issue ?
How can i figure out the TAPI is configured properly or is it an issues with the license or Release of IPO.
I checked all threads regrading such issues in the forum and tried lot of troubleshooting but couldn't fix the issue.

 

[janni78]

If TAPI is configured correctly you should be able to see the extensions in the Windows dialer.exe application

"Trying is the first step to failure..." - Homer

 

[arunknair82]

I opened the dialer application and i am not able to see the extension,
I can see the lines in the attached image.

 

[janni78]

In that case the TAPI driver isn't correctly configured/installed on the client.

Are you using TAPI in 1st or 3rd party mode?

In 1st you enter Name and Password of the user you wanna control and in 3rd you enter the System Password of the IP Office, not the same as logging into Manager.

"Trying is the first step to failure..." - Homer

 

[arunknair82]

I am using single user (1st) mode and using the name and password exactly same i configured in the Manger.
Its working fine in my LAB system.

 

[janni78]

Try it in 3rd party to see if that works, otherwise you have no need for the CTI license.

"Trying is the first step to failure..." - Homer

 

[amriddle01]

Avaya have started disabling TAPI on systems, make sure it's enabled in sec settings in the system

 

[arunknair82]

SPOT ON amriddle01 , TAPI was disabled, i enabled it and everything is working fine!
A star for that valuable piece of information.

 

[amriddle01]

No worries. Same goes for Xima Chronicall not populating reports, that's because they also disable TFTP directory read that Chronicall uses

 

[arunknair82]

That was strange but luckily you expertise helped me to solve the issue, i have the same release of ip office in my LAB and i never enabled TAPI as it worked out of the box.
Thank you everyone for the support.

 

[amriddle01]

An upgrade keeps the earlier settings, a new system takes on the tightened R9/9.1 settings, that's probably the difference

 

[arunknair82]

Just noticed that the TAPI works fine only when we are using a IP or Digital extension.
Its not working with Avaya Flare.
Do i need to do any other configuration to make it work.
Also i noticed that it works sometimes with Avaya communicator but works flawlessly when the user is on physical extension.

 

[derfloh]

Communicator is not really supported with TAPI different to Softphone. Reason is probably that Communicator runs parallel with the deskphone login while Softphone registration logged out the user from his deskphone.

 

[janni78]

Only thing that comes to mind with TAPI when you use Communicator is that you can't answer an incoming call if you have mobile twinning.
Also you since the Communicator logs in after the TAPI application is started you have to make sure that you're application handles that TAPI lines gets added and removed.

It probably works all the time if you log into the Communicator first and then start the application.

"Trying is the first step to failure..." - Homer

 

[arunknair82]

@derfloh You are right , i configured the old video soft phone for iP office and it works like a charm.
System was an upgrade from release 8 to 9 and there was no issues in configuring the soft phone.

To summarize TAPI works well wen you are logged from physical phone or Video Soft phone and at times it works with Communicator as janni78 explained but its erratic
TAPI doesn't work with FLARE

Also for new IPO installations we need to make sure TAPI is enabled in security settings as amriddle01 suggested, in my case it was disabled.

Thank you all for the support , i have finally finished the integration with CRM using the tapi application and configured video softphone for all the AGENTS.

 

[derfloh]

But don't forget that video softphone will not work anymore if you upgrade to R10