Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM VoIP phones 1

Status
Not open for further replies.

bman123

IS-IT--Management
Feb 26, 2007
9
US
How come I can't talk to another IP set but I can ring there phone? My customer has a BCM 400 and I set up an IP phone here at my office and the other IP phone at an employee's house. I set up a VPN tunnel between me an and the BCM site, and another VPN tunnel from the BCM site and the employee. When I dial the other IP set from my IP set, the phone rings but no voice/sound. I,m so confused. Any ideas

 
This is a routing issue.
You need a route defined between the remote sites. Signaling is between the IP Phone and the BCM (hence the ringing) but once connected the data goes point to point.
 
Make sure your VPN router at the BCM site is set to allow branch to branch forwarding.
 
The voice uses 28000 thru 28500 ports for voice.

As far as the routing, you will probably need a route pointing to the WAN address of each Modem at the phone locations.
 
Thats not correct, you are connecting via VPN to the BCM and the other remote site is connected via VPN. You need a route to the INTERNAL address of the remote phone.

If you want our help then we need more info on the VPN you are using. If you are using split tunnelling, then add the subnet of the OTHER remote office to the list of addresses that go up the tunnel (and vice-versa)

If you are both connecting to a contivity, then check the forwarding settings on the contivity and ensure retmote to remote (branch to branch) is on (as biv343 said).

 
I'm using the Nortel Contivity 221 on all 3 sites. One at the IP phone end. Another Contivity 221bat the other IP phone end. And a Contivity 221 at the BCM end. What's messed up, is the IP phone works to the office directly fine or even dialing out of the BCM works fine. It's just from IP phone to IP phone. No talk path. I've racked my brain and can't figure it out.

 
I can't find the remote to remote (branch to branch) forwarding feature on the Nortel Contivity 221 either. Any suggestions.

 
Ok, so you have established Branch Office connections between the remote sites and the central (BCM) site.

Do you have a tunnel between the 2 remote sites as well (STAR Topology) or are you using a Hub+Spoke?

If Hub+Spoke, make sure you include the OTHER remote site's subnet in the opposite remote network list.

If you only have 3 site, then it would probably be easiest to setup a STAR (tunnel from remote to remote), assuming you have static IPs.

I don't know about the forwarding options on a 221, we use larger boxes and their firware is different on the 221 then the rest of the contivity lines. On a 1100 its under "System" -"Forwarding" <Tunnel to Tunnel Traffic>
 
No Static Ip on the remote ends.
How do I do the following which you suggested.
If Hub+Spoke, make sure you include the OTHER remote site's subnet in the opposite remote network list.
 
What are your 3 subnets?

Its been a while since I worked on a 221, Im not familiar enough to walk you through setting up multiple remote network lists (assuming it even supports it), in fact if memory serves me I think the 221 might only support 1 subnet per tunnel, in which case proper subnetting would be the solution.

ie if:
Site 1 (BCM) is 10.0.0.x/24
Site 2 is 10.0.1.x/24
Site 3 is 10.0.2.x/24
Then setup the subnet mask on the remote 221s to be 255.255.0.0, this will force all traffic for both the BCM and other remote site up the tunnel.

Someone else with more 221 experience feel free to chime in.
 
You can apply multiple policies per tunnel.

So....In remote site A's VPN IP Policy, you need to have two policies applied. Both will have A's local subnet as the local network and one will have Central site's subnet as remote network and the other will have Remote site B's subnet as the remote network.

Do the same at remote site B and you should be good.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top