J100 wifi module 4

[Rhinorhino]

Before I set up this type of handset could you tell me your experience setting up a complete Wi-Fi network with the J series phones and the j100 add-on Wi-Fi module?

For example what type of a Wi-Fi transmitter network is required and how is the QOS and customer satisfaction using this setup as opposed to a traditional POE or DS network over a traditional wired network.

Thanks!

 

[nnaarrnn]

I only do this for home users, or those who want to use their own personal Bluetooth headset. I would never do a multi-endpoint rollout of WiFi phones.

 

[Desmisclvlv]

Nnaarrnn, what are the reasons you would not roll out a commercial network of these handsets using Wi-Fi?

 

[Shaun E]

I only do this for home users, or those who want to use their own personal Bluetooth headset. I would never do a multi-endpoint rollout of WiFi phones.

I concur.

I do this at home for some J179 sets I can't easily get cabling to but wouldn't roll them out in a commercial environment unless they were occasional phones (kitchen/lobby/etc). Even though I have a commercial grade Cisco WiFi network at home they're still lacking and will occasionally lose connectivity for a few seconds. I've just switched the one in my bedroom to wired because it lights up the display when it happens which will wake me up.

It's the same reason I ditched my WiFi cordless phones and moved over to the DECT R4.

 

[nnaarrnn]

Nnaarrnn, what are the reasons you would not roll out a commercial network of these handsets using Wi-Fi?

Because the unlicensed RF Spectrum that WiFi uses can be interrupted by anything. I have a location where the wireless (not WiFi!) handicapped-door open-button will cause the WiFi credit card machine closest to it to temporarily go offline for a few seconds. A door button.... Web browsing, streaming, etc... isn't affected too bad by a little hiccup in connectivity, but voice is one of those things where a connectivity hiccup is noticed immediately.

I rolled out the Avaya WiFi cordless phones at a location about 10 years ago. Nothing but problems (as reported by the users of the phones, we could not recreate the issues). We replaced them for the DECT equivalent and they hummed along fantastically until we changed directions completely.

 

[Shaun E]

I have a location where the wireless (not WiFi!) handicapped-door open-button will cause the WiFi credit card machine closest to it to temporarily go offline for a few seconds. A door button.... Web browsing, streaming, etc... isn't affected too bad by a little hiccup in connectivity, but voice is one of those things where a connectivity hiccup is noticed immediately.

Not to mention the microwaves.

If you have a customer site that has voice/wifi issues around lunchtime every day that's a likely culprit!

 

[Rhinorhino]

Thanks for all the information and heads up. I'm going to avoid putting in any of these handsets.

Qos and reliability still seems to order the day with telephones users expect to pick up those handsets and 100% of the time here a dial tone unlike computers where they'll put up with all sorts of problems rebooting etc.

This is the reason at all of my sites I refuse to install VOIP .

I've heard nothing but problems to me there's no cost savings but constant qos problems.

I stick only with analog and PRI perfectly reliable and cost the same sometimes even less expensive than VoIP always clear as a bell and no client complaints.

I'm still surprised at some very large organizations that have installed VoIP systems and when you call them it's the worst most horrible experience talking to them.

I had to call a government office the other day and it sounded like I was talking long distance back in the 1920s echoes delays noise awful.

When I hear those types of qos problems I most of the time ask the person I'm talking with are they're using a VoIP system and it's almost always yes.