|
|
|
|
Joined: Sep 2008
Posts: 142
Member
|
|
Member
Joined: Sep 2008
Posts: 142 |
Is it just me, or does the whole Desktop Suite seem a bit cumbersome. I've had nothing but issues...
Anyway the new one...On all the installs except my own, Outlook does not pop up on incoming calls. Mine works fine. Is there some sort of firewall issues I should be aware of? Is this a permissions issue with Windows? The users are local admins (Domain users), I can't figure it out. There is no Shared Services configured (see my other post) so this is just a direct connection over O&M I would assume.
any ideas?
Desktop Suite 3.6.2.0 / SV8100
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Apr 2005
Posts: 2,526 Likes: 4
Member
|
|
Member
Joined: Apr 2005
Posts: 2,526 Likes: 4 |
I'm sure you already have but I'm asking to confirm, have you enable pops in PC assistant?
We get old too soon, smart too late
|
|
|
|
|
Joined: Sep 2008
Posts: 142
Member
|
|
Member
Joined: Sep 2008
Posts: 142 |
If you mean have I enabled it in the Desktop Suite Preferences, then yes, I have, I got the same exact setup config wise on my machine. According to Docs, you have to set up the pops in Desktop Suite>Tools>Preferences and also to configure in Outlook Tools>>NEC Telephony setup.
Interestingly enough, the Telephony Driver installed on my machine is different than theirs I just noticed when I was looking through add/remove progs. I have one installer package from the CD and one from NTAC The telephony driver version is different between the two even though the revision number is the same...I wonder if thats what the issue is...
If you have another idea let me know, I'll post back if my above helps.
|
|
|
|
|
Joined: Sep 2008
Posts: 142
Member
|
|
Member
Joined: Sep 2008
Posts: 142 |
That installer that installs the TelephonyDriver(1st) is a much more in depth installer than the TelephonyDriver(3rd) Interesting. So upon reinstall of the 1st, I am prompted for the CTI port number (default was 8282 so I kept it) The installer was trying to connect to the PBX, and eventually timed out with an error stating there aren't enough licenses...putting the port to 8181 appears to work though (no error) - So Now I'm just more confused have a look at my licenses below and tell me if I'm OK.
Feature No Feature Name License Qty Expiry
0009 Basic Feature Remote Upgrade 1 Never
0014 256 Port 1 Never
0112 3rd Party CTI Client 1 Never
1001 VM Related VRS 4 Never
1012 VM Box users 512 Never
1404 UMS Client 11 Never
1425 UMS Lite ch 4 Never
2001 ACD Related ACD 1 Never
2002 ACD Client 512 Never
2101 ACD P-event 1 Never
2102 ACD-MIS Basic 1 Never
2103 ACD-MIS Add.Monitor 1 Never
2104 ACD-MIS Agent 8 Never
5012 Terminal Related K-CCIS over IP 128 Never
5304 Desktop Shared Services 128 Never
5305 Desktop Client 16 Never
|
|
|
|
Forums84
Topics94,513
Posts639,938
Members49,844
| |
Most Online5,661
May 23rd, 2018
|
|
|
1 members (BobRobert),
164
guests, and
48
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
