As I have stated in previous blogs the use of a SIP client on a consumer based smart phone within the healthcare enterprise just will not work in a reliable fashion. First; smart phones were designed for the consumer “cool” experience and value advantage of connecting to the carrier for voice and data. With the premise…now data, and more data. How often do you actually see folks “talking anymore”? It was and is all about the smart phone user experience to drive the ARPU. (Average Revenue Per Unit) for the carrier. The carrier’s all currently control the “smart phone” and the connectivity to the tower. Dropping in a WLAN radio and BTLE (Bluetooth Low Energy) were important to include NFC (Near Field Communications) to increase valuation of the smart phone market and the user experience. The more stuff the better. In terms of the WLAN radio for the smart phone it has provided basic security and connectivity but in terms of enterprise roaming to ensure a persistent connection with enterprise grade security, this was not the goal. If it could connect to your home or a hotspot, that was good enough. From a business goal perspective, if this were to occur to work in a reliable fashion it would off load the ARPU of voice. Not a good business model perhaps for the carrier. Thus there is no incentive for smart phone manufacture’s to improve the embedded WLAN radio side of things. So at the end of the day, the enterprise WLAN infrastructure vendors either through design or software will not be able to enable the limited resource WLAN smart phone device to operate in a bullet proof WLAN roaming fashion with the enterprise voice SIP WLAN. So for reliable healthcare voice connectivity, you need an enterprise client device that was designed for this. Trying to stick a round peg in a square hole will not cut it. In this case, it all about RF performance, which a lot of folks simply gloss over.
714-264-7101
sales@integrasystems.org
