sundance-communications.com Forums Telephony Discussion Phone & VoIP Systems Samsung Telephones & Systems Samsung Communicator s/w with V3

Dear all,

Installing Samsung Communicators/w Ver V3.4.0.03 (Got service License from Samsung)on HP Note Book ---Core i5----Operating system is Windows 7 professional 64 bit.(For Cliant Side only)with OS7400 Ver 4.75.
------------------------------------------------------------------
Inhouse Testing with trial license:
PABX ---- Samsung OS7200 Ver 4.92
Installed Samsung link3 v (Connected with OS7200)
installed Communicator ver V3.4.0.3
Added IP address of PABX & Pc in white list
enabled run compatibility mode in icon properties.

Result: not connected (Shows connecting and then fail to login)


Same setup only change the Samsung Communicator s/w ver V1.1003 and its working ok.

Please advise

Tariq

What mode are you using?

Deskphone, UC or Softphone?

UC mode doesn't need OS Link, but does require some settings turn on in COS.

The pc running OS link needs to be in the IP PHONE whitelist.

What ip address did you put in the SCTSP32 popup box during install?

We need to use Deskphone.
At this moment Samsung Communicator is working with Link server activated on Trial version,we will get the Link server license probably today after noon but the issue is that when we try to open license tool in link server its giving some error (does not open)link server is V3, is there any new version of Link server.

i entered pabx ip address at the place of Server address.
thats 192.168.1.90 (i already add in IP white list)made compatility mode enabled in desktop icon.

You need to run both OS link and the license application as administrator on windows vista and above systems.

You can set this to always happen via the compatibility tab in windows.

V3 is the current version of OS Link.

I wish they would update the service side so it works like it did with windows XP and earlier when running as a service so you don't have to enable the "interactive service display" service in windows to see whether it's connected or not.

I've seen this error.
It's to-do with missing dll files or dll's not registering correctly during install.
I'll dig up the fix I got from samsung for this.
Pm me your email and ill send it