The Dialogic® TX 5000 Series SS7 Boards offer a range of throughput capacity and signaling protocol support with Dialogic® NaturalAccess™ Software. The TX 5000 Series architecture combines TDM connectivity and transport with the SS7 protocol layers required for higher level application interface.
PCI Express Hardware
The TX 5500E and the TX 5020E are full length, full height form factor boards, requiring a single x4 PCI Express slot. The design includes an H.100 interface for connecting H.100 bus timeslots to both the SS7 signaling resources and external interfaces to accommodate different configurations.
Onboard Protocol Execution
The TX 5000 Series boards are available with MTP or MTP, ISUP, TUP, and BICC layers of the SS7 stack running on the board processors. Each product requires an appropriate SS7 software runtime license and comes with drivers to support Windows, Solaris, or Linux.
Multiple Network Interfaces
The TX 5000 Series boards provide up to four digital trunk interfaces, which are software-configurable to support T1 or E1 connections. Also included is a 10/100Base-T Ethernet interface, which is used for redundancy.
For network interfaces, all channels from the primary rate digital trunk interfaces can either be terminated locally on the TX 5000 Series board or switched onto the H.100 bus for processing by other H.100-compliant products.
H.100 Provides Open Architecture and Vendor Independence
The H.100 bus and switching feature provides flexibility, openness, and vendor independence, with access to other resources, such as voice and call processing and speech recognizers.
When deploying two boards from the TX 5000 Series in a redundant configuration, one of the onboard Ethernet interfaces is required. The interface supports a dedicated point-to-point link to provide extremely fast data transfer between the two boards. This approach avoids the need to transfer lower-level data over the host computer's bus and significantly improves SS7 signaling performance.
Redundancy protects against signal¬ing link, board and node failure. A typical redundant configuration has two boards - one primary and one backup - under a single point code, with active links going to each board. Link-level redundancy is managed automatically at the MTP level. Higher level check-point¬ing is implemented by the application for total redundancy.