I’ve written my last couple of blogs on ISDN vs. SIP and Open Source vs. Proprietary PBX’s. Now I would like to conclude this subject with why Hospitals really should implement the SIP protocol on their PBX rather than remain with their legacy PBX, which could be TDM, or even the earlier signaling protocol H.323.

I would like to go over a couple of problems I have seen in the industry with utilizing these legacy PBX’s. The largest complaint on legacy PBX’s, especially the ones with TDM interfaces, is the lack of bearer channels. Every time you want to increase your capacity, you will need to add another T1 card, which of course only adds 23 more bearer channels, or 24 if you have the capability of running a shared d-channel as in a NFAS configuration. A second common problem is the display name being sent over the TDM trunk via the ISDN protocol. Some ISDN protocols use Information Elements (I.E) in the ISDN Setup Message while others may use Facility Messages to send the Calling Name. Sometimes, if supported at all, this configuration can be cumbersome. A third problem also seen, especially in a Tandem PBX, is the lack of the ability to sometimes send the actual calling number or perform any digit manipulation.

With a SIP PBX, especially Open Source, all of these problems can be easily resolved. There is no 23 bearer channel limitation. If you want the ability to place more calls, you just have to make sure you have the appropriate hardware such as memory and CPU power. As for the Calling Name, it can be taken from the Display Info in the SIP Header. This is pretty much automatic, really little to no configuration. Digit manipulation and the calling number are simple with SIP. The calling number is generally sent in the host part of the SIP from header. The calling number can also be obtained easily from what is referred to as a P-Assert or Remote Party-ID.

As for H.323, it really is an end of life protocol, still used somewhat in the public sector, but not much use in the private sector. Although closer than SIP in relation to ISDN signaling, there is little development being done with it today.

So in conclusion, choose SIP for your hospital.

I’ve often been asked if a proprietary SIP PBX or an open source PBX should be utilized in my environment. Well, the answer to this question can be rather complex, depending upon your needs. There are reasons one may be beneficial over the other, as I have explained below.

An open source SIP PBX will normally interoperate with any PBX, proprietary or open, as long as it supports the SIP RFC 3261, the IETF SIP standard. The great thing about an open PBX is you can customize the software to suit your needs. There is also plenty of online help to get you going and even to help you once you have started. The only negative thing about the open PBX is it may be more difficult to get paid support.

A proprietary SIP PBX may not interoperate with another proprietary SIP PBX. Many times companies add proprietary SIP extensions to their code, which prohibits some interoperability with other proprietary SIP PBX’s. Proprietary PBX’s may not completely follow the IETF standard either, which also adds to interoperability issues, especially with other proprietary PBX’s. A proprietary PBX will often limit you to purchase other peripheral hardware just from that one vendor. The nice thing about proprietary PBX’s though, is they normally have a paid support staff to aid you when you need assistance.

In conclusion, the open source SIP PBX will be much less in expense compared to the proprietary PBX. There are no licensing fees and you do not have to sign contracts for support. As long as you have a knowledgeable staff and want to save on costs, the open source SIP PBX is certainly the way to go. A proprietary PBX is just that, proprietary, and often keeps your selection down to just the one vendor.

All of us at Voalté are thrilled to announce the latest Voalté One for iPhone software release - the all-new 2.0 package. During the past few months our development team has been hard at work. The result? A new iPhone app, desktop web-client (now called Voalté Messenger), and server software powering it all from behind the scenes - giving you the best Voalté One experience EVER!

I know what you’re thinking … all this new software sounds great, but what does this mean for me, the end-user? For starters, a speedier experience. Login time, message delivery, and app responsiveness are all noticeably faster. And we’ve done it while dramatically reducing the amount of traffic sent over your network.

iPhone users will get more than just a sweet looking user interface, they’ll also get the following:

 

-An all-new navigation view that makes moving between your unit, your favorites, and the rest of the hospital a breeze

-An updated directory that organizes units by building/location, presenting your entire directory in a compact and organized fashion
-A search feature combined with presence, so your search results are ordered alphabetically by availability
-Read and delivery receipts so you'll not only know when a message was delivered, but also when it was read
-A new "Quick Response" feature, which allows you to respond to any question with a single tap to convey a "Yes", "No", or "OK"

 

I could go on and on about features (like Landscape view), so feel free to check out the online demo for all of the cool new features.

At this point, you're probably thinking, "How will the service team at Voalté take advantage of this occasion to make sure we're all up to date?"

At rollout, we'll provide a short instructional video, a PowerPoint presentation for training, updated manuals, and flyers perfect for mass distribution and posting on top of your local charging station. To top it off, your friendly Voalté Care Specialist and BFFs will be there to answer your questions. 

What's next? We're already working on the next release, and we're basing it on suggestions you've made -- so keep those great ideas coming!

As you know, we're all about feedback here, so I'd love to hear what you're most excited to see with the 2.0 release. Share away…