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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VOIP on a BCM

Status
Not open for further replies.

eartel

Vendor
Mar 10, 2003
214
US
I am trying to setup VOIP on my BCM and have run into some difficulties. I have read the manual and have programmed accordingly but continue to not connect to the network from my IP2004 set. Is there a check list of what to do somewhere or is the book the only reference? Any help would be appreciated.

EARTEL
888 416 4327
310 549 0387 Fax
rluna@eartel.net
 
My supplier guarantees we have ip licenses, but how do I verify.

EARTEL
888 416 4327
310 549 0387 Fax
rluna@eartel.net
 
I was able to make the IP 2004 work on the local network.

EARTEL
888 416 4327
310 549 0387 Fax
rluna@eartel.net
 
I have to struggling with this same issue. I now have my BCM connected to a Static IP Address. I can connect to the BCM on my local network but not from offsite. I have been asking for help on this from a number of sources without success. I can't even ping the static ip address from off site but it is no problem from onsite. There has to be some trick to this.
 
Yeah there is a trick for remote sets.
It's called partial DHCP or fixed IP assigned to i2004 in firewall DMZ with port forwarding.
I recommend the static method.
The S1 address on the phone must be pointed to the static ip address of the BCM.
The public interface of the BCM must also be the published IP address defined on the IP telephony tab in unified manager.
If NAT is used on the BCM enable the default rule for include IP phones for the public LAN interface.
The port used on the phone is 7000.
You must also port forward 2800-28511 on the residential router to the static ip address of the phone.
 
Are you saying the IP2004 must have a static IP address? Where do you assign the IP address to the phone in the BCM? I thought the BCM was the only device to have a static IP address.

I have a linksys router at the off site and a netopia dsl modem at the bcm site. I have 5 static IP addresses assigned through the netopia modem with 4 input ports. I have the BCM connected directly to the netopia and my computers going through a linsys router.

What settings do I change on the netopia router and what settings do I change on the linksys router at the off site?

EARTEL
888 416 4327
310 549 0387 Fax
rluna@eartel.net
 
The i2004 must have a static IP address on the remote private LAN.
The linksys router at the remote will only be able to accomodate 1 remote phone through port forwarding.
Any more than one set would require a hardware VPN between the sites.
 
Aragon:

I appreciate all your help with trying to get this working. I have been assuming that you don't need a static IP address for the remote site is that true? The IP phone itself has a static IP on the remote local lan but the lan itself does not have a static IP address. The BCM side does have a static IP address. Since the remote Lan doesn't have an static address I don't understand how the BCM would go to the IP Phone.
 
According to the book the only static IP address should be assigned to the BCM. Why do you need a static IP for the remote site? I checked with other techs and they say the static IP should be only at the BCM. What is the real story?

EARTEL
888 416 4327
310 549 0387 Fax
rluna@eartel.net
 
I never said the remote site needed a static IP I said the phone did.
The IP address for the BCM must be entered into the static configuration of the set or through partial DHCP.
For some reason the phones do not like to use DHCP off site.
TecTel you are correct the phone needs a static ip address on the lan. The remote router can use DHCP.
 
But can the remote site work with a dynamic IP Address. The reason I ask is because you are suggesting that the IP phone be included in the DMZ. It was my understanding that this (DMZ) was so you could go to the IP address of a network and then get to a specific device (without that device having a static IP).
 
Aragon,

Thanks for all your support on the VOIP IP2004 setup. I got it to work today and it works great. I also got the desk top messaging working to.

I was trying to get into the programming of the BCM from my remote computer and was able to get to the home page of the BCM and was able to go into voice mail and the other applications. But I was unable to get into the system programming of the BCM. Is there a setting that allows for TCP entrance or a different user name and password. Again thanks for your help.

EARTEL
888 416 4327
310 549 0387 Fax
rluna@eartel.net
 
I'm jealous. I still can't get mine to work. Could you let me know what you did.
 
TecTel,

There are many areas to turn on and off. You would have to call me and be in your system and you would have to check each item one by one to truly verify if your system will work. Call me and I will assist you.

EARTEL
888 416 4327
310 549 0387 Fax
rluna@eartel.net
 
For remote management BCM is a pain.
Many ports required for BCM management are now blocked by most ISP's
DCOM is blocked
RPC is blocked
You can however use the v.90 modem in a pinch.
 
Aragon,
Your last post mentions the v.90 modem. I just posted a new thread about my modem not answering at all. Ring , no answer. New 3.6 hard drive in an older (colored connector) BCM 1000. I think it may be a driver issue. You seem very knowledgable of the BCM. Would you mind checking out my thread about this modem problem and see what your take is. Thanks HelplessBCM
 
I know little about the BCM but I bet the phones connect to a control port probably SIP TCP/UDP 5060/5061 @ the IP address of the BCM?

If you are trying to connect to your BCM over the internet without first VPNing in, you will want to port forward on your firewall, so you will 'point' your outside phone to the outside address on the firewall and it will forward the traffic to the BCM.

Of course that is a sloppy way of doing this and branch office VPN is probably the best...

 
Setting up VoIP to you branch offices is not difficult.

But first you have to get your VPN solution up and running.
You'll want to use a site-to-site VPN. This can be done with inexpensive routers (like linksys, D-Link, etc.).

Once you have your site-to-site VPN going, you can have as many phones at the remote site as you want.


MCSE CCNA CCDA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top