02-11-2009 05:45 PM - edited 03-15-2019 04:09 PM
This issue only happens to VPN users.
Version : Checkpoint SecureClient R56, IP Comm 2.1.2 , CCM 4.1(3)
When the VPN users run the CIPC, on CM it shows IP as the âinternet IPâ instead of the IP assigned by VPN
Test call, it rings, but after pick up, both end silent
Currently the work around is:
On IP Comm - Preference - Audio tab - Network button, change to âUse this adapter's addressâ, then change back to âAuto Detectâ,
Ok. Phone re-registered
My question is:
Is it a bug or sth?
Any solution?
thanks,
Ethan
02-12-2009 09:43 AM
Ethan,
I've been using CIPC and Checkpoint for years now, and just recently discovered that the newer versions of Checkpoint don't like the newer versions of CIPC.
I've used 2.1 through 7 with a Call Manager version 3 system. All work when on-net, but none of them work through Checkpoint.
I removed the CIPC and re-installed version 2.01 and the phone works again. (This with CP version HFA60)
Make sure that in CM under the device settings you have the IP Autoaddress Location populated with this address:
http://"CM PUB IP ADDRESS"/communicatorloads/communicator/getIP.asp.
This should point the audio stream to the correct location to allow two-way voice.
Lee
02-17-2009 08:44 AM
Hi Lee,
Thanks for your reply.
I already ran the administration tool to generate the getIP.asp. The VPN user still need to manually detect the IP.
I haven't tried to downgrade the CIPC to 2.0.1 yet.
This issue is weird. Not all the Checkpoint SecureClient R56 client users got the problem, just for 1 remote site users, other users are fine.
Anything else you want to add other than downgrading?
Thanks a lot,
Ethan
02-17-2009 09:52 AM
Hi all,
Is anyway we could trace? like run RTMT on the server? what monitoring tools we could run on PC?
thanks,
Ethan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide