TAPI 64 bit software update for the Personal Call Manager application 2

[Firebird Scrambler]

I have a customer with a BCM 50 at release 6.0 that has all the latest Avaya patches installed who is currently using the Personal Call Manager tool on Windows 7 32 bit without any issues, but they are planning on using Windows 7 64 bit and this is where they are having problems.

Going on the Avaya website today, I found a reference to compatibility for Windows 8, that I have attached here but on page 3 it does say the following statement below.

"The BCM TAPI Service Provider (TSP) will only work on 32-bit versions of Windows 8.
Implementation specifics for Windows 8 prevent the BCM TSP working in WOW64 emulation. A
native 64-bit version of the TSP is required for support on 64-bit versions of Windows 8.

Note specifically that LAN CTE is supported through WOW64 on 64-bit versions of Windows 8, so
only applications that require TAPI support are impacted by the limitation just described. For
example, Personal Call Manager (PCM) is a TAPI-based application, so PCM cannot run on a 64-
bit version of Windows 8. Desktop Assistant Pro however is a LAN CTE application, so it will run
on 64-bit Windows 8. Please consult with developers of any third-party applications to determine
whether their applications are TAPI-based on LAN CTE-based.”

I’m not sure if the Desktop Assistant Pro tool is similar to the Personal Call Manager application as it would appear that there isn’t any problems with (DAP). I personally have never used Desktop Assistant.

Taking a look on the Avaya BCM FAQ section only states this from April 2016 below.

#################################################

BCM: How to obtain / download TAPI software

Rate this Page


Doc ID: SOLN286876
Version: 1.0
Status: Published
Published date: 05 Apr 2016
Author: Stephen Edge



Details
BCM
BCM50
BCM450
TAPI
LAN CTE
Problem Clarification
Where can the BCM TAPI software be obtained?
Cause
N/A
Solution
TAPI software is available to download from the BCM itself;
1. Point your browser to the IP address of the BCM
[the Home page uses Java, you may need to select “Click for Non-Java enabled browsers”]
2. Select User Applications
3. Select and download “LAN CTE Client”
This application has the option to install LAN CTE and/or TAPI driver

##################################################

The query I have if there was ever any 64 bit software developed but probably not supported that is available please. Has anyone ever come across this problem before?.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[koulioumbis]

Hello Firebird Scrambler
i face the same issue. I have a third party CTI application running fine on 32 bit windows but on 64 bit is is not possible. After installing the LANCTE interface on 64BIT it takes long time to apply it, it reboots and stops there.
Never found a solution on thanks.

Nikos

 

[Firebird Scrambler]

Thanks Nikos, I was about to email you about the problem.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[curlycord]

I found this link on Windows 8 Client Apps

On my R6 it states: Note: The TAPI option is not supported on 64-bit versions of Windows.
So I take that as any software that requires Tapi will not work on a 64bit machine.


________________________________________

Add me to LinkedIN

=----(((((((((()----=

http://www.curlycord.com

Toronto, CAN

 

[Firebird Scrambler]

Thanks Curly, it is the same PDF that I had attached on my original query that was dated in 2013.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[curlycord]

Oops , I did not notice you attached something.

I think the client needs to realize they are out of luck or maybe use Virtual Machine.

________________________________________

Add me to LinkedIN

=----(((((((((()----=

http://www.curlycord.com

Toronto, CAN

 

[Firebird Scrambler]

No worries Curly. Interesting, does the Virtual Machine LAN/CTE work OK with 64 bit Windows computers?.

If so, has anyone set it up and is it easy to do?.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[ucxguy]

This question (getting BCM TAPI working on 64-bit Windows) pops up from time to time. Maybe it's time to actually answer it. For inquiring minds, I'll provide some background info. Those looking just for the (unfortunately negative) answer can skip the next few paragraphs and go to the end.

BCM software provided two CTI interfaces - LAN CTE and TAPI.

The first CTI interface - CTE - is an API that was provided by Nortel to third party application developers who purchased the BCM CTI development toolkit. By using this toolkit, 3rd party developers had access to a large set of functions and events - due to that, they were able to develop a variety of applications with some very interesting features.
The second CTI interface - TAPI - provided only call related services due to a relatively basic implementation of a TAPI Service Provider (TSP). The BCM TSP is actually a LAN CTE application that uses just call related functions/events.

BCM TSP was based on a TSP originally developed for Norstar on Windows 95. At that time, TAPI 2.0 was the latest TAPI specification and there were no 64-bit Windows. During the years of active BCM development (2000 - 2009), the only updates of this BCM TSP were a few compatibility changes for TAPI 2.1 and some installer changes. Due to that, the BCM platform has provided only a TAPI 2.x TSP.

With Windows XP, Microsoft introduced a new specification - TAPI 3.0 - which was totally different from TAPI 2.x. From development perspective, there was no upgrade path - companies had to develop a completely new TAPI Service Provider for the TAPI 3 specification. To make the transition from TAPI 2.x to TAPI 3.x easier, Microsoft provided support for TAPI 2.x TSPs on all their 32-bit operating systems. Nevertheless, there was no support for TAPI 2.x TSPs on 64-bit operating systems.

Neither Nortel nor Avaya developed a TAPI 3.x TSP for BCM. The result is that the BCM TSP works only on 32-bit Windows and thus BCM TAPI services are not available on 64-bit Windows. To get TAPI working on 64-bit Windows, someone would have to develop a TAPI 3.x TSP for BCM (similarly to the TAPI 2.x BCM TSP, it could be a LAN CTE application).
Who knows, maybe some companies that used to develop CTI applications for BCM still have the BCM CTI development toolkit and could write such a TSP, but I suspect that their custom development charges for a project like that might not be acceptable for your customer.

 

[curlycord]

Thanks for the full details ucxguy.

As for Virtual Machine I cannot recall if Personal Call Manager or other, just tried the Win7 on VM and Win 10 blue screened me twice so need to fix VM I guess.


________________________________________

Add me to LinkedIN

=----(((((((((()----=

http://www.curlycord.com

Toronto, CAN

 

[koulioumbis]

Maybe anybody knows if IPO500 any version supports TAPI 64BIT? I know this is a post for another forum but it is related to this post as BCM can be migrated to IPO.
Thsnks
Nikos

 

[QueBall780]

I have a 3rd party LAN CTE attendant console working under 64bit. But it speaks to the BCM using that native LAN CTE protocol directly so no TAPI drivers needed. Product made by Advatel. I believe they will still sell it. Not exactly a great attendant console but the old one we used had been abandoned a long time ago. I know if I breathe on that virtual machine the wrong way the old one breaks but they still like to use it. The Advatel one is more of a backup for the critical task of showing the status of extensions on remote BCM units. (you cannot program a BLF button to show status of remote extensions on another BCM)

 

[janni78]

IPO has both TAPI2 and TAPI3 drivers working in 64-bit OS so guess they could do it if they want.

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