The
figure above illustrates an overall architecture for VoIP
and suggests that the challenges for the product developer
arise in five specific areas:
Voice quality should be
comparable to what is available using the PSTN, even over
networks having variable levels of QoS.
The underlying IP network
must meet strict performance criteria including
minimizing call refusals, network latency, packet loss, and
disconnects. This is required even during congestion conditions
or when multiple users must share network resources.
Call control (signaling)
must make the telephone calling process transparent so that
the callers need not know what technology is actually implementing
the service.
PSTN/VoIP service
interworking (and equipment interoperability) involves gateways
between the voice and data network environments.
System management, security,
addressing (directories, dial plans) and accounting
must be provided, preferably consolidated with the PSTN operation
support systems (OSSs).
The
race to create VoIP products that suit a wide range of user
configurations has now begun. Standards must be adopted and
implemented, gateways providing high-volume IP and PSTN interfaces
must be deployed, existing networks need to be QoS-enabled
and global public services need to be established. Adoption
of VoIP must also remain economically viable even if PSTN
prices decrease. Needless to say, developers often underestimate
both the difficulties of adding voice to packet networks and
the complexities involved in building products suitable for
public networks.
|