TDM over Ethernet or TDM over IP |
As carriers continue to see the advantages of an IP/Ethernet network, it compels them to consider their current infrastructure capabilities, while scrambling to manage today’s demand for cellular voice capacity, today’s augments have to be cost-effective. With timing and synchronization solved, operator trust in the solutions drives them to converge their fixed and mobile networks as one providing a superior experience to customers.
TDM over IP Will the link carry any traffic transparently, even signaling protocols like DPNSS and QSIG?
PacketBand TDM will handle all protocol types transparently, simply passing the data to the end devices unchanged. This will work the same way in both G.703 (unstructured) and G.704 (structured or framed) modes, except that timeslot 0 is not passed on G.704 connections, but reconstituted locally.
As TDM over IP packet networks have no concept of clocks or clocking, this raises the requirement for PacketBand to enable TDM over IP or TDM over Ethernet services. A PacketBand device can be given a reliable clock source (external or internal) which is then recovered by the PacketBand devices at the other side of the network. This means the attached TDM equipment receives the necessary steady clocks and all devices are synchronized together. The recovery and stability of these clocks, which is the whole basis and reason for using this technology, is a major strength of the PacketBand range. With PacketBand the TDM device sees what it believes to be a continuous steady clocked stream of traffic with no delays - just as if it was connected on a point-to-point wire or leased line.
Seamlessly enable voice and leased-line service traffic over Ethernet/IP/MPLS.
Eliminates the need to lease T1/T3 and T3/E3, reducing operating costs.
TDM over IP is transparent to protocols or signaling, supports proprietary features and signaling.
No forklift upgrades to your equipment.
Toll-quality voice across the network.
Standards-compliant with TDM over IP, SAToP and CESoPSN.
Reconstituting timeslot 0 has some significant advantages when inter-connecting E1 devices on a network with packet loss. If running G.703 and packets are lost, the E1 interface of the attached devices may shut down after a number of lost timeslot 0 packets. When running G.704 mode this will not happen as the timeslot information is generated locally
============================