Hi,
Does anybody have any pointers on how to get this "odd" combination to work ?
I am not sure but think I need to use Network Connect for this ?
Regards
Scott
Hi,
We've been using IP Communicator with Network Connect for a few years without issue. In theory, WSAM would probably work but I haven't tested it.
-John
what did you do to make it work?
Yes, Network Connect is needed for this; WSAM cannot handle this due to the server-initiated nature of the call server.
I would recommend, as well, configuring the NC profile for ESP rather than NCP/oNCP.
Can you tell me where do you get this information from, I mean the thing about "the NC profile for ESP rather than NCP/oNCP"? We are implementing a Cisco Call manager and are deploying the Cisco IP Communicator to users and we have a lot of problems when using Juniper Network Connect.
The recommendation on using ESP rather than oNCP/NCP comes from working with multiple clients. It also uses UDP as the transport mechanism so has some additional speed there compared to the TCP-based oNCP/NCP. For call information the ESP mechanism also allows for QoS (if enabled on your network).