Implementing a VoIP network is often a relatively straightforward implementation, though it is vital to know which areas call for to be considered. We would suggest the subsequent key areas are looked into-
Network capacity
Network devices (routers, switches, etc) have the capacity and QoS features vital for accent traffic
LAN and WAN utilisation
Interaction with, and affect on, data applications
Effectiveness of network-optimisation tools to maximize utilization owing to compression and latency-reduction techniques
Disaster recovery
Duplication of major PBX nodes (dependin on your chosen VoIp key)
Fallback to POTS (Plain Ancient Telephone Logic) at all or strategic locations
Protection hostile to failure of power and power spikes
Emergency use mobile phones (which could be pay-as-you-go)
Emergency facilities with pre-provisioned network relations
Re-routing via the broadcast internet
Security (also outlined as a seperate link)
Disowning of Service (DOS). Attacks via a weakly confined VoIP element could flood the network disabling data applications, or conversely a DOS attack on a data application could inhibit accent traffic.
Hackers making free use of the telephone logic, for example by fooled billing (making the call appear to terminate internally when, in fact, it continues externally).
Inquiring on network traffic, soft phones and voicemail by innumerable devices, or by call hijacking (routing a call to a different destination).
Standards
H.323 (Packet-based multimedia communications systems) issued by the ITU
SIP (Conference Initiation Protocol) issued by the IETF
There are also other, proprietary protocols in use, for example Skype.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
