atcomsystems.ca/forum Forums VOIP Phones & IP PBX VoIP & Cloud Phones, Hosted PBX, General IP Phones ISPs and VoIP

Hey all,

I just posted a blog article about whether Your Internet is Suitable for VoIP. Check it out and let me know what you think

For a beginner or novice its a good beginning.

A good internet connection is an absolute necessity, obviously.

Not enough attention gets paid to network infrastructure INSIDE the building, though. It's really a must to have managed switches, not the $49 box from the big box stores to manage and properly route network traffic, with special attention given to voice traffic with VLANs created when necessary. Our salespeople learned this lesson the hard way after selling hosted VoIP to Mom and Pops with simple 4 port dumb switches. Unhappy customers always crow louder and longer than happy ones do.

Thanks for looking guys

JBean - you are correct about cheap consumer grade switches and routers, they can definitely burn you sometimes. However, some of the "big guys" like Ring Central like to blame call quality issues on the LAN. They say you NEED to have QOS implemented which is something beyond the average IT guys, let alone the average small business person. In practice, call quality issues 9 times out of 10 are completely ISP related.

That being said, call completion problems or 1 way audio most often have to do with mis-configured local equipment.

I'm in a unique spot. My company is the local CO, a hosted provider, an IT management company AND the ISP. Most of the time, call quality issues are my fault one way or the other, unless I can prove the problem lies outside my network.

The biggest problem we see with other people's networks is LAN settings that don't disable SIP ALG or allowing the port re-mapping tendencies of some firewalls.

Very true, mis-behaving routers can result in hair loss! I've personally observed Sonicwall routers randomly change NAT port numbers part way into a call - this obviously broke audio. Mind you, that was 10 years ago.

Which routers have you seen mess around with port re-mapping?

I prefer to keep the firewall name under my hat ( its initials are 'Sonicwall'). It still happens, but mostly because the customer's IT person isn't aware of the settings to stop it.

I dumped using Sonicwalls years ago. Man they gave me head aches.

Former employer used to sell Soincwall...until we stopped selling on premise phone systems and went to hosted systems. They were a nightmare for VoIP. Even when everything was configured the way it was supposed to be, even with SIP ALG turned off, things tended to break. Sonicwall would suggest a firmware update, requiring after hours work to bring down the customer's network, meanwhile they think we've sold them a dud of a phone system. Support was horrible, and it was clear the sale to Dell and back again was rough on them. We dropped Sonicwall and went with Fortinet. Didn't have a single firewall related voice issue between when we switched to selling Fortinet and when I left the company.

My challenge recently has been a side customer I have (my current position is entirely internal working on Avaya Aura and managing an IT service group) that isn't large enough to justify a more expensive firewall, so they rely on their AT&T provided "residential" gateway. It has been nothing but problems. Currently working through an issue with it causing their SIP trunks to drop registration a couple times a month.

I've been pleased with mikrotik routers on a 4 location vpn project I recently completed. Mikrotik are very feature rich and reasonably priced. There is a learning curve and I am still learning.