outlook 365/2019 call contact with 3cx greyedout

Status
Not open for further replies.

duduhandros

Free User
Joined
Feb 23, 2021
Messages
1
Reaction score
0
Hi friends
new installation the option greyed out. 3cx cloud last version 16.0.8.9
tried to run the windows 3cx client and the outlook as admin not helped.
any suggestions?
 
The Outlook plugin is supported until Office 2016 and older. Newer versions are not supported because Microsoft discontinued the APIs.
 
The Outlook plugin is supported until Office 2016 and older. Newer versions are not supported because Microsoft discontinued the APIs.
@Frederick Marcoux, actually newer versions are not officially supported because they weren't tested, but I have seen them working in some installations, so it should be possible to get this working. The API available for Outlook add-ins remains unchanged.

Hi friends
new installation the option greyed out. 3cx cloud last version 16.0.8.9
tried to run the windows 3cx client and the outlook as admin not helped.
any suggestions?
Having the click to call with 3CX menu options greyed out, means that the 3CX add-in (running inside Outlook) can't connect to the Outlook plugin (running inside 3CXPhone for Windows). You're seeing the options, and that means that the Outlook add-in have been loaded by Outlook, and it's working. So, this is what you need to check:
1) Both Outlook and 3CXPhone must be running with the same user account. This is because the named pipe used for this communication contains the User ID as part of the name. If you're running Outlook as administrator, you will need to do the same with 3CXPhone. Ideally, run both programs as a normal user.

2) Check if 3CXPhone has loaded the Outlook plugin. You can check this from the "C:\Users\USER_NAME\AppData\Roaming\3CXPhone for Windows\Logs\3CXPhoneForWindows.log" file. If you're deploying the integration via provisioning (PRO/ENT licenses), then you need to look for something like this:
[23.02.2021 14:34:26.810][1] Pro only added DotNetScriptPlugin, Version=16.3.0.0, Culture=neutral, PublicKeyToken=bac47dd19dc4098a

Otherwise, if you're installing the integration with the 3CXPlugins installer (STD license), then you need to look for something like this:
[23.02.2021 14:34:26.939][1] Targets override Standard, Pro MicrosoftOutlookPlugin, Version=15.0.945.640, Culture=neutral, PublicKeyToken=bac47dd19dc4098a
[23.02.2021 14:34:26.939][1] Pro added MicrosoftOutlookPlugin, Version=15.0.945.640, Culture=neutral, PublicKeyToken=bac47dd19dc4098a
[23.02.2021 14:34:26.939][1] Standard added MicrosoftOutlookPlugin, Version=15.0.945.640, Culture=neutral, PublicKeyToken=bac47dd19dc4098a

3) If the plugin is loaded, you should check the "MicrosoftOutlookAddin.log" and "MicrosoftOutlookPlugin.log" files in the same Logs folder, which might give you additional hints.
 
@Frederick Marcoux, actually newer versions are not officially supported because they weren't tested, but I have seen them working in some installations, so it should be possible to get this working. The API available for Outlook add-ins remains unchanged.
That is different from what I heard but okay then! That's good to know!
 
  • Like
Reactions: edossantos
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,324
Messages
591,897
Members
165,475
Latest member
lastshadow