Skip to content
plhale's profile

New Member

 • 

4 Messages

Friday, April 3rd, 2015 12:00 AM

VOIP "Consistency"

Hello,

I am a new business class customer. We lease the Cisco DPC3939 an have no static IPs. We have a 3rd-party MiTel VOIP system. The phones connect to the providers VOIP server/controller.

Since moving to Comcast service in Tuesday, the phones are not able to connect. Firewall is disabled during testing. The VOIP provider is blaming the issue on the "consistency" of the Cisco DPC3939. They are recommending we move to an ARRIS SB6141, or something similar.

Does this recommndation make sense? We are not dropping packets, but ping times to the VOIP controller sometimes do exceed 100ms.

If I put in a SB6141 tomorrow for testing, how troublesome is it to activate to test the provider's thoery and move back to the Comcast-provided GW if the provider's theory fails?

Advocate

 • 

1.4K Messages

10 years ago

 

Hello pthale and welcome,

 

So, you have no static IP for your VPN server, so how do you control its ability to have one standard IP address? The ONLY way you can do this is to make adjustments in your current internal DPC DHCP Server dynamic IP address range. For example, you should consider moving the start address from 10.1.10.2 to 10.1.10.10. This will give you 10.1.10.2 through 10.1.10.9 to work with and any of these will then be able to be used for your VPN Server force fed stable IP address. This way your VPN Server will have one stable IP address that will not be touched by any other devices obtaining 10.1.10.10 through 10.1.10.252 dynamic addresses.

 

Yes, it also quite common for Comcast to be blamed for everything as you mentioned your VPN Server manufacturer was. It is too bad that more are not aware that proper networking interconnect and configuration goes a long way to enabling data transaction processing to work correctly. I am familiar with MANY Comcast customers using the DPC successfully for the VPN, Security cameras, mail or web servers, ftp, proxy servers as long as they utilize the correct networking interconnect and configuration.

 

Hope this helps you out.

  

New Member

 • 

4 Messages

10 years ago

VBSSP-RICH,

Thanks for your reply. You are exactly right. I limit the DHCP range and give the server the static IP outside of the DHCP range.

I tested the IP phone on a different site that runs the setup, with Comcast, that the VOIP provider is recommending. It works, of course. So I guess I will go get a modem and try and remove the gateway for testing.

I am hoping I don't face a hassle or a long delay in getting the testing modem activated for use...

New Member

 • 

4 Messages

10 years ago

Update:  I removed the Cisco DPC3939 gateway and put in the SB6141.  To my astonishment, the VOIP phones worked instantly.  I was quite skeptical that the Comcast gateway would limit VOIP protocols.  Seems like too sinister an assessment to me, but I can't argue the result.

 

On the upside, activating the SB6141 was quick and painless.  The Comcasy Business support rep I worked with was fast, efficient, and very professional.  He had the gateway off the account and the SB6141 activated in less than 10 minutes.  I was impressed.

Advocate

 • 

1.4K Messages

10 years ago

What is your Internet speed?

New Member

 • 

4 Messages

10 years ago

It is the 100 Plus plan.  Averaging about 119mbps download and 23mbps upload.

New problem solver

 • 

8 Messages

10 years ago

Glad to hear we are not the only ones who found the DPC3939 to be unusable with VoIP (specifically SIP TCP/5060). Thanks for posting information about a suitable modem. We are currently still stuck with the DPC3939 and using some workarounds (alternate SIP ports) to get around the modem's issues.

 

Understand that bandwidth is not a concern. You can run ten calls through 1Mbit without any problem.