web statisticsweb stats

Business Phone Systems

Previous Thread
Next Thread
Print Thread
Rate Thread
Page 3 of 10 1 2 3 4 5 9 10
Joined: Sep 2006
Posts: 149
Member
Offline
Member
Joined: Sep 2006
Posts: 149
Quote
It just isn't as easy as punching the cable down on one end and putting a jack at the other. :rolleyes:
There's no web interface for the equipment you need to make it work either. help

Atcom VoIP Phones
VoIP Demo

Best VoIP Phones Canada


Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.

Joined: Sep 2006
Posts: 149
Member
Offline
Member
Joined: Sep 2006
Posts: 149
Quote
Since lots of information is stored in the set itself what happens when you replace a phone, will the VOIP server back up the phones data?
You can set the phone to retrieve it's configuration from the server. Then you configure the phone settings on the server, which gives them to the phone when it boots up.

You could also configure the settings directly on the phone, but you will probably find this unmanageable for more than a few phones, and there will be no backup of the configuration settings.

Joined: Sep 2006
Posts: 149
Member
Offline
Member
Joined: Sep 2006
Posts: 149
Man, I've been here for over 3 years now and I've finally managed to ruffle enough feathers to get a 1-star rating from 2 people?

I'll summarize the problem with VOIP, and whether you like this or not, it's the truth:

The problem is not the technology, it is the implementation, and part of the implementation depends on the skills of the installer.

One poor implementation of VOIP I've seen has an expensive Cisco IP phone mounted on a wall, configured as a ringdown to the security office.

There should be an analog phone connected to an ATA there. Not a phone which is #1, expensive to replace and #2, subject to abuse.

Joined: May 2003
Posts: 2,924
Member
*****
Offline
Member
*****
Joined: May 2003
Posts: 2,924
web page

VoIP Phone Systems - When done wrong, hurts.
Christopher Reagoso, April 15, 2008 * DRAFT * Revisions to follow, stay tuned!

By revealing the dirty little secret of VoIP phone systems to you, a dirty little secret equipment vendors don't like to talk much about, I seriously risk being excluded from every good party thrown by my computer tech friends in Philadelphia, especially since many of them are trying to "get into the phone business" by selling VoIP systems to Small and Medium Business (SMB) customers with the promise of lower phone bills and a lower Total Cost of Ownership (TCO). To make matters worse, some of my tech friends enjoy confusing matters using abbreviations and acronyms in conversation like SMB, TCO, as well as SIP, QoS, MOS, TDM, as if use of those terms establishes some kind of an authority...

Even though I risk being shunned by my tech pals, I suspect I'll also make a lot of new SMB friends, be kept in better company with them, and be satisfied in knowing that I saved my new SMB friends from the hassle of poorly implemented VoIP systems by writing this article...

It sure is nice when you pick up the phone, and it just works. There's a dial tone, and you push buttons, and your call goes through.

That is changing with the introduction of cheap VoIP phone systems and VoIP phone service.

There's nothing wrong with VoIP itself - the problem is that vendors are trying to sell VoIP technology to consumers that will not benefit from it on promises of saving some money on long distance calls or adding some extra lines (SIP trunks) to phone systems for almost no money.

Adding to the problem, phone vendors love selling VoIP systems since they make more money when they sell VoIP systems, and some vendors will do anything to close the deal. It's easy to make more money selling VoIP phone systems to small businesses. In the mind of the small business owner, the hardware expense competes with the monthly recurring expense of the phone bill. If there's a way to get the monthly cost of the phone bill down, maybe they can afford the new phone system.

The small business owner sees the promise of a cheaper monthly phone bill and decides that they can afford the VoIP phone system. Even though a traditional phone system actually costs a little less than the VoIP system, the monthly bills for traditional phone service will cost a little more, so the traditional phone system is ruled out.

Hardware vendors selling VoIP systems make more because they use the phenomena of the smaller phone bill as a way to justify the expense of the system, so the vendor will sell a few extra phone systems that month.

When the small business owner connects their new phone system to their internet, they are suprised to discover that the VoIP calls are poorer in quality (fuzzy, sometimes voice cuts out, sometimes calls drop). This is because the VoIP traffic competes with all of the office's other internet traffic. The VoIP hardware vendor is quick and correct in pointing out that it's not a problem with the equipment they sold to the client, but it is a problem with the customer's local area network, internet connection, or VoIP telephone service provider.

Many disappointed small business owners now face the fact "when something sounds too good to be true, it usually is." When they try to leave their VoIP provider they find they have to pay fees to terminate and sometimes lose their phone numbers.

To resolve the problem, the business owner must switch to ordinary telephone lines, or add an additional internet connection to their office dedicated to their telephone system. While the extra internet connection may help, it cannot permanently resolve the problem.

The problem with VoIP isn't actually a VoIP problem at all - it's a hype problem - a problem with peoples' expectations of what VoIP can deliver versus what it was designed to deliver, and by new vendors and inexperienced users misapplying the technology to try to save two cents a minute on phone calls.

VoIP frequently doesn't work well on the internet - and it's not a problem with the speed of the internet, or the speed of your connection to the internet - it's a problem with the "Quality of Service" or QoS on the internet.

QoS is a feature that lets you (or more specifically, trusted network operators) control the priority of data traffic on a network.

On the open internet, it's like the wild west - this is by design and will never change. Nobody's network traffic has priority over anyone else's. On a good day, everything flows fine - probably even most of your VoIP traffic. On an average day there's regional outages, routine maintenance, and other problems that cause a delay of network traffic. The internet even has a few "rush-hours," usually when the kids get home and before everyone goes to work. These delays may last only a half-a-second, maybe a little more, and YouTube'ers, and music downloaders don't mind. If your email is delayed a few seconds, you probably don't mind that either. You probably also wouldn't notice, or wouldn't even care, if you were downloading web pages and there was a one or two second delay.

VoIP packets are the some of the most sensitive of all network traffic. Any disturbance, any delay, or even if too many of them arrive in the wrong order an your phone call goes fuzzy or drops.

Equipment vendors selling VoIP hardware will frequently dismiss the QoS issue and tell you that you only need to use a router with QoS on it. What they don't tell you is that the router can only control outbound network traffic, and it cannot control inbound traffic - or what "the internet is throwing at you."

Putting a QoS router on your internet connection is a band-aid - it does not permanently fix the the problem. If someone on your network is on YouTube, the internet is throwing video at you. If someone on your network is listening to streaming audio or internet radio, the internet is already throwing audio at you. Add that to inbound email, web sessions, virtual private network (VPN) traffic, intensive remote desktop sessions and other forms of remote office access, and your VoIP service gets very unreliable. You can't fix the problem by throwing more bandwidth (more speed) at it either. You have to control QoS to fix the problem, and you cannot control QoS on the internet.

Since you cannot control the inbound data QoS (what traffic the internet is "throwing at you"), you will experience fuzzy and dropped calls if you are using VoIP for your telephone service. Make sure you have some traditional phone lines to fall back on. Then again, this is not the kind of experience you want your customers to have when they're talking to you in the first place.

Big companies love VoIP technology. They can afford to deploy it properly. They can afford the dedicated network connections between their large offices that are required to deliver reliable, "fuzz free" calls. These dedicated connections save a lot of expense for inter-office calling versus having all of the inter-office calls go through the phone company (or Public Switched Telephone Network - PSTN).

If you are using VoIP for interoffice calls (e.g., you have more than one office location and are trying to save some money by linking phone systems with VoIP), you must have a "managed network connection" between your sites. When you have a managed network, you can control the priority of network traffic ensuring the voice packets get the highest priority from end-to-end. Generally, a managed network between offices means a dedicated data connection between offices. VoIP networked PBX'es are great for offices with a hundred employees at each site, and will save them some money. It doesn't make sense for the small business, though.

Simply put, unless you can afford a dedicated data circuits between your office sites, you will experience dropped calls, fuzzy calls, and have other problems.

Buying VoIP? Buy Local! If you are considering a VoIP phone system, you are always better choosing a local vendor. Do not choose an internet reseller. Your local vendor will know who all of the good local internet and SIP providers are - most importantly, they're "within reach" if your new phone system doesn't work as advertised. Most importantly - use an experienced local vendor and always, always check references first!

Do you need a phone system with 50 or fewer telephones? More than likely you'll benefit from a lower total cost of ownership, and greater reliability provided by a traditional telephone system. If you have a few remote workers - or even a dozen - a traditional phone system is likely still a better choice. The phone company solved this problem long ago with call forwarding, Centrex, and other services you can add to your account. Even when you add a few monthly services to your phone bill, a traditional phone system usually costs less in the long run than a VoIP phone system for small business.

Best of all - with a traditional phone system, when you pick up the phone, there's a dial tone. When you press buttons, the call goes through. Once your call is in progress it will stay on and give you no problems, unless of course the other guy has VoIP service or is on a cell phone.

Sorting through the hype, options, and service providers, and hardware vendors - and deciding how and when to go VoIP - is a minefield for any business (Forbes, 8/07).

The truth about internet phone system sales: As dealers, we all earn rebates or get lower pricing when we sell a lot online. The more we sell, the less we pay. Resellers that sell VoIP hardware online make more when they sell VoIP hardware than when they sell traditional hardware. VoIP phone systems are great for equipment resellers dumping equipment on internet consumers. Telephone system vendors make more money when you buy a VoIP phone system.

If you decide to purchase a VoIP phone system from an internet vendor, get a guarantee it will work so you can return it, or be prepared for a fight if it doesn't.

Another reason internet VoIP hardware vendors love selling VoIP hardware - it is easy to blame someone else (even you) when it doesn't work. Let's say your calls are dropping, or fuzz-out, or you're not even getting calls. Your vendor can blame it on your local area network, your internet connection (the "last mile" - your DSL, cable, or fiber connection), or the internet upstream (the internet beyond your walls - the internet you have no control of - the internet that connects the big providers to each other), or your dial tone provider (sometimes called SIP trunk provider).

If you have a traditional phone system, your hardware reseller cannot pass the buck as easily - you simply disconnect your phone system from the phone company's telephone line, and attach an ordinary telephone (or test set), and if you have dial tone, you know the problem is in the phone system. There's no guessing. It's just more reliable.

We sell traditional phone systems to do-it-yourselfers and other professionals through our web store. We do not sell VoIP phone systems over the internet. This was a decision we made since the small VoIP systems and service providers can be quite unreliable. When our customers have problems with their equipment, we do not send them off to the manufacturer for support, we work with our customers every inch of the way. Since VoIP systems tend to be a lot more trouble if not properly installed, we choose not to sell them over the internet.

As soon as we feel VoIP has matured, and QoS issues have been solved, we will carry it in our web store. Right now we agree with Forbes Magazine and feel that it is more hype than value.
Food for thought...


Someone commented to me after reading the draft that I sure included a lot of links about the problems with VoIP in small business. To be even handed, I tried googling things like "phone system problems" and "phone system drawbacks" and "traditional phone system problems" and nearly every article that returned was about problems with VoIP phone systems. Don't believe me, for a laugh, just try it yourself.


Reference Library

Video: Vonage Voice Over IP Review
Are VoIP carriers unreliable?
Fee to cancel unreliable VoIP service is unfair
Video: Number portability problem
VoIP Security Challenges
Is VoIP Reliable?
Hacking VoIP
VoIP Problems
IP Telephony Problems and Challenges
VoIP Cons, Problems and Pitfalls
VoIP System Security: Time to Worry, or Maybe Not
The Top 5 VoIP Security Threats of 2008
Brace Yourself: VoIP Spam Is Coming
Wireless Broadband + VoIP = Problems
Why there's no Internet QoS and likely never will be
QoS Fact or Fiction
Why QOS is Important and QOS Action List
Twitter Updates

* Did you know the makers of the Vertical SBX are closing their warehouse for an Entire Week? Reminder: Reliability is AVAILABILITY. 24 days ago
* Microsoft pulls the plug on Response Point. Expect a lot of new and no-name VoIP companies to fail as well. https://blogs.technet.com/rp/ 45 days ago
* Want new features for free? Upgrade your firmware. https://bit.ly/i2K3Y 91 days ago
* Are you using Direct Inward Dial, or are you forcing customers to dial extensions? Get out of the dark ages. https://tinyurl.com/nec-dsx-did 98 days ago
* VoIP for the NEC DSX is almost upon us! https://tinyurl.com/necdsxvoip 100 days ago

follow me on Twitter
Start Live Chat

* Buy Local!
* NEC DSX VoIP
* DSX Telephones
* NEC DSX-40
* NEC DSX-80
* NEC DSX-160
* DSX Voicemail
* DSX Expansion
* DESI Labels
* Headsets
* DSX Installation
* Warranty
* Programming
* Voice Over IP
* Tech Support
* Features
* NEC DS2000, NEC DS1000
* NEC DSX Demo

home | terms | site map | SHOPPING CART

Joined: Sep 2006
Posts: 149
Member
Offline
Member
Joined: Sep 2006
Posts: 149
To summarize that: Don't use VOIP because if you use SIP trunks, internet congestion may cause them to not work well.

On that note, was my KXT-308 VOIP enabled when I had one of the trunk ports connected to an ATA?

Joined: May 2003
Posts: 582
Member
Offline
Member
Joined: May 2003
Posts: 582
Brianl703
Quote
The problem is not the technology, it is the implementation, and part of the implementation depends on the skills of the installer.
This is absolutely true - you will find many people on this board that only believe in TIP and RING and would rather bash VoIP than admit the technology will run them over in the near future when there will be no TDM systems to sell as new implementations.

Sure maybe for the office with 2 or 5 people but you sure cant make any money on that sale and I am pretty sure 1/2 of those sales will then be carrier based SIP offerings.

Some of them bash VoIP because they are afraid to learn VoIP or don't have the skills to learn, some say its crap and not worth their time to learn and some just bash it in hopes it will never run them over.

The come back for the basher is TDM will be here for ever - sure as it will as grey market used stuff.

The question is can your business survive if you dont adopt new technologies - I believe that answer is NO!

We adopted it a few years back and have been very happy with the systems we sell and the revenue it generates.

Our IP system sales are at least twice to three times that of any hybrid sales and I am thinking with 2 years we will not be selling a hybrid system at all.

Yes we invested the time and money it takes to be successful and it has paid off big time.

Joined: Sep 2006
Posts: 149
Member
Offline
Member
Joined: Sep 2006
Posts: 149
I think TIP and RING still has it's place.

Because of that...

I like using the PAP2 ATA to marry TIP and RING with VOIP. The support the PAP2 has for analog telephones far exceeds that of most of the TDM stuff I've seen.

FSK message waiting? The PAP2 does that.
Caller-ID? The PAP2 does that.
CPC that works right? The PAP2 does that.
48V talk battery? The PAP2 does that.
Call-waiting Caller-ID? The PAP2 does that.

(These all tend to be "problem areas" for TDM systems, don't they?)

You can even use a PAP2 to add MOH input or paging outputs to a VOIP system.

Joined: Feb 2005
Posts: 12,344
Likes: 3
Member
***
Offline
Member
***
Joined: Feb 2005
Posts: 12,344
Likes: 3
All I want to do is hang a KSU on the wall, connect the POTS CO Lines and run one or two pairs to each phone. I want to be able to simply program from a predefined feature set using a phone or a GUI interface. That's all the majority of customers need to keep them happy.

I DON'T want to become a software programmer.
I DON'T want to contend with software licenses and upgrades.
I DON'T want to become a network administrator.
I DON'T want to become a computer jockey.
I DON'T want to contend with SIP or any of that BS.

NONE OF THIS CRAP IS NEEDED!! What the hell is so hard for you VoIP guys to understand?? This is all designed by the manufacturers to put more money into their shareholder's pockets by modeling the telecom business after the IT business. TDM systems lasted forever with little maintenance, THAT HAD TO BE CORRECTED with something that generated a constant revenue stream.

And the suckers are falling for it.

-Hal


CALIFORNIA PROPOSITION 65 WARNING: Some comments made by me are known to the State of California to cause irreversible brain damage and serious mental disorders leading to confinement.
Joined: Jan 2005
Posts: 15,379
Likes: 13
Moderator-Vertical, Vodavi, 1A2, Outside Wire
*****
Offline
Moderator-Vertical, Vodavi, 1A2, Outside Wire
*****
Joined: Jan 2005
Posts: 15,379
Likes: 13
Quote
"These all tend to be "problem areas" for TDM systems, don't they?"
Well, not exactly. These are basic standards as specified by the FCC and Telecordia (formerly Bellcore) for all telephone systems and hardware in the United States. The fact that local service providers are constantly trying to reinvent the wheel with gadgets to squeeze more life out of their cable plant is the problem. They install these contraptions, but don't know how to configure them.

IP, TDM or even Close-N-Play systems is irrelevant: All phone lines are supposed to be delivered to the customer premises within the limits of these standards. An improperly-configured Cisco IAD that is only putting out 34 VDC for dial tone or 50 VAC ringing voltage isn't going to work for many, if not most systems.

Oh and yes: Many of these contraptions are often made by manufacturers that are not experienced in the real ins and outs of these standards.


Ed Vaughn, MBSWWYPBX
Joined: Sep 2006
Posts: 149
Member
Offline
Member
Joined: Sep 2006
Posts: 149
Point is, the properly configured PAP2 will meet the standards.


It even has enough ring power to ring the bell on a 2500 set. 3 of 'em, in fact. (I didn't try 5 to see if it delivers a full 5 REN but I expect it does).


As far as TDM systems lasting forever, they do. It's just that technology marches on and something as trivial as caller-ID is "sorry, can't do that. Not with out a special board that's as rare as rocking horse turds and has a price tag to match".

Page 3 of 10 1 2 3 4 5 9 10

Moderated by  JWRacedog 

Link Copied to Clipboard
Forum Statistics
Forums84
Topics94,293
Posts638,829
Members49,768
Most Online5,661
May 23rd, 2018
Popular Topics(Views)
212,577 Shoretel
189,451 CTX100 install
187,612 1a2 system
Newest Members
Robbks, A2A Networks, James D., Nadisale, andreww
49,767 Registered Users
Top Posters(30 Days)
Toner 26
teleco 9
dexman 6
jsaad 3
Who's Online Now
1 members (justbill), 121 guests, and 241 robots.
Key: Admin, Global Mod, Mod
Contact Us | Sponsored by Atcom: One of the best VoIP Phone Canada Suppliers for your business telephone system!| Terms of Service

Sundance Communications is not affiliated with any of the above manufacturers. Sundance Phone System Forums - VOIP & Cloud Phone Help
©Copyright Sundance Communications 1998-2024
Powered by UBB.threads™ PHP Forum Software 7.7.5