07-15-2009 06:51 PM
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.
If this solves your problem, please mark this post as "Accepted Solution". Kudos are appreciated.
08-13-2010 06:21 AM
what did you do to make it work?
My customer is trying to get Cisco IP Communicator running with the
SA6500. We have the network connect allowing them to connect to the
Cisco Call Manager, but then outgoing calls fail. They can connect to the call
manager and register their phone. They can also get dial tone, but after
dialing a number it goes dead. Incoming calls are displayed, but when they answer
the call it then goes dead.
08-19-2010 11:12 PM
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.
11-16-2010 07:55 AM
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.
11-16-2010 09:19 AM
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).
03-14-2011 11:30 PM