BCM50 - I can hear them but they can't hear me

[unclerico]

Using BCM50 (ver 1.00.2.04g) and an I2004 handset

I am wondering what the typical causes are for one way communication. In this particular case I can hear them but they can't hear me both for interal and external calls. There is no firewall involved as our BCM50 connects directly to our provider via a PRI circuit. Currently the default codec and the default jitter buffer are set to default. I have tried setting the codec to G.711-uLaw with a payload size of 20ms. This is my first experience with VoIP so I'm not sure what to look for and my VAR is stumped also. Thanks for your help.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[norstarboy125]

you have to open the proper rtp ports that will happen every time...

 

[unclerico]

thank you for your reply. This is going to sound like a really stupid question, but on which device do I need to open the ports? I'm assuming the firewall, but I wouldn't think that is the case because 1) I have monitored my firewall as I was making calls and nothing was being denied outbound, and 2) I am under the assumption that the voice traffic will still go out via the PRI circuit as opposed to our Internet T1.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[tnphoneman]

Have the network routing checked. Sounds line you can go one direction but not the other. In other words the subnet for the phones knows how to reach the BCM but the BCM subnet does not know how to route to the phones.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[unclerico]

I used the ping utility from the BCM Manager and was able to successfully ping the phone as well as a pc that I placed on the VLAN to verify that routing is working as expected. Is there anything else that I can check for?

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[Skyfall]

It is a typically network issue. Something related to your layer 3 switches in your LAN. Ask your IT guy, check it out. We had customer same issue and after they changed something in the switch, IP set has two way talking now. But I don't know what exactly they changed.

Always learn from someone, something and somewhere......

MC

http://www.tomkin.ca

 

[Phonedaddy]

I'm assuming this IP phone is on your local LAN and not across a WAN? Try plugging the phone into the ethernet port right on the KSU. Also use your BCM monitor and watch when you place a call. You will see which ports are being used and you can go from there. I think they are in the 50000 to 61000 range.

 

[unclerico]

That is correct, the IP Phone is on my LAN. Here is the information that I can get from the BCM Monitor

IP Devices tab:
DN: 353
Type: I2004
IPort: 172.22.122.1:5000
RTP Session: 51000 <-> 192.168.10.114:28008
Info: G711_ULAW 3fpp, Small jb

Everything that I can find points to a layer 3 issue, but I cannot find anything that is blocking the traffic. My current configuration is like this: 2 x Cisco 3750's in a stack config performing IP routing(all devices on all VLAN's point to these as the Default Gateway of their respective VLAN), 4 x 48 port Linksys SRW2048's each cascaded off the 3750's using a 2 port EtherChannel in Trunk mode. The BCM is in VLAN 10 (192.168.10.x/24) and the IP Phone is in VLAN 122 (172.22.122.x/24). The BCM is plugged into one of the Linksys' and the IP Phone is plugged into a different Linksys. All routing has been verified between VLAN 10 and VLAN 122 by placing a PC on VLAN 122 and accessing resources in VLAN 10 and vice versa. No ACL's have been configured on the 3750's or the Linksys' and no firewall is between the BCM and the PRI.

I do know that sometimes the I2004 will take 20 minutes or more to actually connect to the BCM and download its config (it cycles through S1 and S2 multiple times). Other times it connects right away.

Like I said in my first post, I know very little about VoIP so I just don't know what else to look for. I have received support from Nortel themselves (if you call it that) and it has gone nowhere. Thanks for the help thus far.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[telcodog]

I had a similar problem once with a system that was connected to two others via voip trunks. One way transmission every time. I passed the issue off to their IT guys and they worked on it for almost the whole day.

I was getting frustrated in what was taking so long so I had a closer look myself and discovered that when they set up the dhcp scope for the ip sets, they were one digit off on the default gateway. Changed it manually and voila!

Phones would register ok and even place calls but we couldn't hear the far end no matter what.

This kind of thing is always a "network issue" but sometimes we forget to look at the simplest solution.

Just a thought.

 

[unclerico]

I hear what you're saying and I'm sure that it is a "network issue", but as I said I am able to get end-to-end connectivity with a PC for testing on the same VLAN that is set for DHCP. Thanks for the idea though.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[unclerico]

Actually, on the DHCP front is there anything that I need to define in Scope Options besides the Default Gateway?

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[unclerico]

Update...it looks like I have a faulty unit. I downloaded and installed the 2050 softphone on one of my laptops. At first I connected it to my main production LAN (VLAN 10) and was able to have two way communication. I then moved the laptop to VLAN 122 and again I had two way communication. After spending some more time on the phone with Nortel support it was suggested that I plug directly into the BCM with the i2004. Even doing this I was still only able to only get 1 way speech path. We then tried to place a call using speaker phone and what do you know, it worked. After that I brought the phone back to my workstation and plugged it back into VLAN 122. I placed a call using my headset and it worked just fine. So it turns out it is a hardware issue with the i2004. Thanks to those who helped me out I really appreciate it.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[kwtaylor]

You need a patch. I noticed you have Version 1.002.

I had the same problem, If you reboot your system the problem will go away temporarily and then reappear in about a week.