IP 2033: No speech path across SIP trunks

[cboelkow]

When making a call across the WAN using SIP trunks, I have no speech path in either direction. When I go off off hook and dial, you hear the ring back, see in the display that the far end answered, but neither end can hear anything. All other sets going across the SIP trunks work fine. The switch is a BCM400 rls4 with updated patches as of 3/25. The far end is a bcm50 rls3. The IP 2033 works fine when calling across the PRI or internally. Any ideas.

I see that there is a new firmware release for the 2033. How hard is it to upgrade? I have never done anything with a TFTP server before.

Thanks

 

[telcodog]

Sounds liks some port blocking going on. You obviously have port 7000 opened up but you also need 28000 to 28255 and 51000 to 51200 to be able to talk on the call. Don't forget to check the default gateways as well. On the calls where you can talk, you didn't specify if they were digital or ip sets but the 2033 is an ip set.

 

[allenmac]

The 2033 firmware is easy to upgrade.

You need to set-up a TFTP server on your network that the phone can ping, put the config files in it's default directory, and reboot the phone.

To configure the TFTP server IP in the phone, you will have to enter the configuration menu during the reboot process.

I use solar-winds TFTP server.

You can download it free here:

http://www.solarwinds.com/products/freetools/free_tftp_server.aspx

 

[cboelkow]

Sorry, it took me so long to respond, I was out of town. All of the sets on both systems are IP sets. There are no issues when calling across the LAN or WAN with other sets. The issue is only with the IP 2033. I will verify that those ports are open.

I will also be downloading the TFTP server and attempting to upgrade the firmware. I will keep you posted.

Thanks
Chuck

 

[SupportDude]

This is a good one!
The i2033 should be taking the same path as all the other IP sets. With that in mind, I would suggest taking a look at the codecs in use for the i2033. Make sure it is using the same codec as one of the other sets that can complete the call across the SIP trunks.

-SD-

http://www.mysupportguy.net

 

[bobby400]

*bobby400 is now working this issue as chuck is on vacation*

***This may or may not be part of the problem**************
While onsite I noticed that this IP 2030 set refuses to find the BCM to get an IP via DCHP. Chuck apparently had to hard programm the IP info. All other sets are set to DHCP.
************************************************************


Anyway...
I took this IP2033 set to another one of the customers locations. (same BCM network).This location has a WORKING IP2030. I configured it for DHCP. It connected to the BCM and subsequently downloaded a NEWER firmware (2310S678).
The phone makes call across the network just fine.

Maybe it's fixed...I will take it back to the original site and try it. It it works..great. If not then there is obviously a network issue, possibly related to my comments above.