A new networking trend that is approaching the small network user is VoIP (Voice Ovr IP). It will typically include IP-based videoconferencing and offer such benefits as free or very low-cost calls, “local number anywhere” and wideband (FM-grade) telephony. Businesses of all scales are moving away from the classic PABX or key system which has its own wiring infrastructure and moving towards an IP-based business telephony system which uses existing local-area-network infrastructure. For them it also reduces the need to rent extra telephone lines for such requirements as inter-location “tie lines”.
The main problem with current VoIP setups is that they are hard to configure. Typically, you have to determine the network configuration for your VoIP service provider and work out particular “dialling plans” such as whether to use VoIP or standard telephone to make a particular call. The other factor you have to work out is which number your VoIP handset rings to. Most of these setups involve awkward interfaces and terms, including remembering certain parameters to be set across multiple devices. In some situations, this kind of work still needs one who has technical knowledge of all things to do with business telephony.
A lot of VoIP service providers have responded to this issue by selling pre-configured VoIP hardware that is locked down to their services. This situation ends up with the hardware being useless if you decide to move to a better deal offered by a competing service provider or decide to expand and evolve the system.
One way of improving the setup is to provide service-plan data packages that can be uploaded to VoIP hardware. This can be useful when it comes to signing up to a new service provider or upscaling the existing VoIP service. Another improvement that can exist could be preset outbound dial plans such as “VoIP for calls other than local & emergency / service”, “VoIP for calls other than emergency / service” or pre-defined “VoIP tie-lines”. These can be selected through a wizard-style interface.
The inbound call plan would be set up through a service-extension map for “direct inward dial” or simple “one-click” options for basic “all-call” setups.
As far as the provisioning of new VoIP telephone extensions goes, VoIP systems should consider use of UPnP and similar IP-based technologies for this purpose. The other issue that also needs to be considered is a standard data package for supplying the extensions (VoIP handsets or analogue telephone adaptors) with the necessary data. This avoids the requiement to have a system that can only work with telephones from a few vendors and can allow innovation in this field. It is more of concern as far as WiFi-based VoIP handsets, including “fixed-mobile convergent” mobile phones, are concerned.
The data packages would be an XML-based configuration file that contains information about SIP / STUN provider details, handset identity details and outbound / inbound dial plans.
Once measures are taken to make VoIP telephony easier to deploy, this can lead to system owners being able to have home and business telephony their way.