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

IP calling into BCM 450 one way talk path

Status
Not open for further replies.

Sekin

Programmer
Dec 28, 2010
6
US
Any help would be appreciated.

The deal here is this:

from 1.1.1.1 making inbound call to the BCM ( lets call it 2.2.2.2) we get the voicemail after 4 rings but if someone answers the call is dropped. If you try to leave a message at the extension you have called there is no talk path to the BCM but you can hear the VM message.

Here is what we are trying to do

Make a call without a tunnel across the internet to the BCM. We have succeeded in what is stated up above but can't get 2 way talk path to work. We have the NAT license installed but I am not sure which way to go from here to get the voice path up to the BCM. I realize that for external ip phone to external ip phone you need a tunnel but we are asking if anyone has made a pure ip phone call to a BCM and succeeded with using the ip address and no tunnel in place?

Thanks for any input!
Take Care!
 
I've been doing the same thing today on my BCM 50 release 2 system. My colleagues can connect OK, even log onto Element Manager.

They can call me, I can call them but there isn't any speech.
I don't know if the problem is with my broadband router?. I have enabled all the known BCM ports to the BCM 50 System.

Here are my current router port forwarding settings. My BCM is on my own home network of 86.130.12.5

BCM Signalling ALL TCP/UDP 5000 86.130.12.5 5000
I20xx to BCM Media ALL TCP/UDP 51000 - 51200 86.130.12.5 51000 - 51200
Succession 1000 IP Phn ALL TCP/UDP 4100 86.130.12.5 4100
Access Unified Mngr ALL TCP/UDP 6800 86.130.12.5 6800
BCM Signalling ALL TCP/UDP 2216 - 2219 86.130.12.5 2216 - 2219
BCM Signalling ALL TCP/UDP 16500 - 16501 86.130.12.5 16500 - 16501
BCM Signalling ALL TCP/UDP 15000 - 15100 86.130.12.5 15000 - 15100
BCM Signalling ALL UDP 1718 - 1719 86.130.12.5 1718 - 1719
BCM Signalling ALL TCP 1720 - 1721 86.130.12.5 1720 - 1721
BCM Call Pilot ALL TCP 443 86.130.12.5 443
BCM Call Pilot ALL TCP 5989 86.130.12.5 5989
BCM 50 Signalling ALL UDP 30000 - 30999 86.130.12.5 30000 - 30999
BCM IP Signalling ALL UDP 7000 - 7002 86.130.12.5 7000 - 7002
I20xx to BCM Media ALL UDP 28000 - 28255 86.130.12.5 28000 - 28255
BCM Signalling T.38 Fax ALL UDP 20000 - 20255 86.130.12.5 20000 - 20255
BCM NAT traversal ALL UDP 9950 - 10050 86.130.12.5 9950 - 10050
SIP Port ALL UDP 5060 86.130.12.5 5060
BCM 50 Signalling ALL UDP 59000 - 60999 86.130.12.5 59000 - 60999

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
I forgot to add that when ever one of my colleagues tries to ring, this message appears in the alarm table.

TERM.(0007, :0001): No public media address available for IP set at 192.168.0.4:51014

I'm assuming that this is my actual problem?.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
Based on the symptom we can deduce the following.
Signaling path is good.
Outbound stream from the BCM to the IP Phone is successful.
Outbound stream from the IP Phone to the BCM fails to connect.

I would suggest using the BCM onboard capture utility to grab sniffs via the LAN port.
Save it as RAW with no filter applied.
After you do the capture, save it to your PC with a .pcap file extension.
Review the file using WireShark.
This should give you an indication of why the BCM cannot accept the inbound stream from the IP Phone.

You might also try configuring the IP address of the phone into a DMZ on your router.

HTH!

-SD-
 
Will see what I can come up with thanks much!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top