Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Subnets or masks issue?

Dear Network Gurus

What looked like a simple setup is giving us a headache

RouterA rv016 on 192.168.0.1/255.255.255.0 VPN gate to gate to RouterB rv082 with 192.168.1.1/255.255.255.0 , NAT transversal is enabled.

IPPBX on 192.168.0.10, Tel on 192.168.1.100, won't reach the PBX, we can ping from/to without problems.

We can ping the PBX with 192.168.0.10 from the lan with 192.168.1.1

We can ping the phone with 192.168.1.100 from the lan with 192.168.0.1

Ideas, tests, pointers, all appreciated.

thanks

Everyone's tags (5)
4 REPLIES

Subnets or masks issue?

What's your WAN connection type on RV016 and RV082?

Do you use protocol binding at all?

You might want to give SBSC a call to deal with issues like this.

Bronze

Subnets or masks issue?

Alejandro,

If the tunnel is up and the ping is going through it could be a phone configuration issue or a SIP issue.  What is the problem with the phones? do they not register? or is it communication between two PBX's?

Cisco Small Business Support Center

Randy Manthey

CCNA, CCNA - Security

New Member

Subnets or masks issue?

Randy, tekliu

The phones have DHCP, when there are placed on the 192.168.0.1, they get their IP, register and work without a problem.

When they are transported to the branch with the 192.168.1.1 network, they get their IP, but wont reach the PBX.

I can ping the PBX from that network , and can ping the phone from the other one.

We have found that enalbing Multiple Subnet on the RV016, and adding 192.168.1.0/255.255.255.0 hampers the funcionality of the VPN. We can ping the branch RouterB, but the branch cant ping the RouterA.

thanks

Bronze

Subnets or masks issue?

Alejandro,

I think it is a routing issue from what I can see so far, but we would need to see a network diagram to confirm this. It might also speed up the process if you called in and created a case and worked with an engineer on this issue. 1866-606-1866.

Cisco Small Business Support Center

Randy Manthey

CCNA, CCNA - Security

623
Views
0
Helpful
4
Replies