cancel
Showing results for 
Search instead for 
Did you mean: 

Cisco IP Communicator & Network Connect

SOLVED
emg1102_
Occasional Contributor

Cisco IP Communicator & Network Connect

Hoping that someone can assist with this issue.

 

We use Network Connect enabling users to connect into our LAN, however we are experiencing an issue with Cisco IP Communicator.

 

When two remote users are connected into Network Connect and attempt to call one another using Communicator, it does not work.


It seems that Network Connect is not allowing users to route to one another.

 

By comparison, when a user is connected into Network Connect and attempts to call someone on the LAN, it works fine.

 

How do we enable 2 Network Connect users to communicate with one another.

 

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
emg1102_
Occasional Contributor

Re: Cisco IP Communicator & Network Connect

Great question regarding the pings...

 

That was my first step in troubleshooting.

 

We were not able to ping, which caused us to dig a little deeper.

 

Ultimately, we discovered that the subnets of the unreachable devices were not built on the NC.

 

Once we added them, everything worked perfectly.

 

Thanks to all.

View solution in original post

5 REPLIES 5
felixkhang_
New Contributor

Re: Cisco IP Communicator & Network Connect

How did you configure your Network Connect Access Policies?  

Just to ensure that it's not the NC Access Policies configuration issues, allow all network (*:*) from the NC Access Policy then test the phones again.  

  • If the phones still do not work, there may be another issues (maybe firewall) other than your NC Access Policy configurations.  
  • If the phones are working, then it is your NC Access Policy issue.

The first issue may be more difficult to resolve.  But the second issue should be more straightforward.

In my NC Access Policy for Cisco IP Communicator, I had to allow the followings:

  • tcp://<IP of CUCMs>:80,2000
  • udp://<IP of CUCMs>:69
  • udp://<IP of VGs>:16384-32767
  • udp://<local subnets of each sites>:16384-32767

What I've configured maybe an overkill, but try this config.  If they work, you can either leave it or streamline it further to make it more secure.

jayLaiz_
Super Contributor

Re: Cisco IP Communicator & Network Connect

Hi,

 

Are you able to ping the NC assigned IP's from one machine to the other ?

 

Regards,

Jay

emg1102_
Occasional Contributor

Re: Cisco IP Communicator & Network Connect

Great question regarding the pings...

 

That was my first step in troubleshooting.

 

We were not able to ping, which caused us to dig a little deeper.

 

Ultimately, we discovered that the subnets of the unreachable devices were not built on the NC.

 

Once we added them, everything worked perfectly.

 

Thanks to all.

View solution in original post

zanyterp_
Respected Contributor

Re: Cisco IP Communicator & Network Connect

Thank you for sharing your solution & troubleshooting
emg1102_
Occasional Contributor

Re: Cisco IP Communicator & Network Connect

No problem.

 

This issue was an easy one to solve once we realized that devices were unreachable via ping.