Product suggested to: DEVELOPERS.
Redundancy from 2x up to 4x.
 |
The Mobile Application Part (MAP) is a SS7 protocol
which provides an application layer for the various nodes
in GSM and UMTS mobile core networks and GPRS core networks
to communicate with each other in order to provide services
to mobile phone users. The Mobile Application Part is the
application-layer protocol used to access the Home Location
Register, Visitor Location Register, Mobile Switching Center,
Equipment Identity Register, Authentication Centre, Short
message service center and Serving GPRS Support Node.
Quick Specs:
- Standalone Linux/Solaris process
- SMS
- USSD
- ATI
- 4 TCAP Modules connected for load sharing/fault tolerancy
- 4 MAP Users connections |
| |
|
 |
The CAMEL Application Part (CAP) is a signalling protocol
used in the Intelligent Network (IN) architecture. CAP is
a Remote Operations Service Element (ROSE) user protocol,
and as such is layered on top of the Transaction Capabilities
Application Part (TCAP) of the SS#7 protocol suite. CAP
is based on a subset of the ETSI Core INAP CS-2 protocol.
Quick Specs:
- Standalone Linux/Solaris process
- CallControl
- GPRS
- SMS
- 4 TCAP Modules connected for load sharing/fault tolerancy
- 4 CAP Users connections |
| |
|
 |
The ISDN User Part or ISUP is part of the Signaling System
#7 which is used to set up telephone calls in Public Switched
Telephone Networks. It is specified by the ITU-T as part
of the Q.76x series, and Telcordia former Bellcore GR-246
series.
Quick Specs:
- Standalone Linux/Solaris process
- 4096CC
- Configurable protocol optional parameters
- Automatic Call Gaping
- 4 MTP3/M3UA Modules connected for load sharing/fault tolerancy
- 4 ISUP Users connections |
| |
|
 |
Transaction Capabilities Application Part, from ITU-T
recommendations Q.771-Q.775 is a protocol for Signalling
System 7 networks. Its primary purpose is to facilitate
multiple concurrent dialogs between the same sub-systems
on the same machines, using Transaction IDs to differentiate
these, similar to the way TCP ports facilitate multiplexing
connections between the same IP addresses on the Internet.
Quick Specs:
- Standalone Linux/Solaris process
- 128k simulaneusly open transactions
- Automatic Dialog recovery
- Automatic Transaction Gaping
- 4 SCCP Modules connected for load sharing/fault tolerancy
- 4 TCAP Users connections |
| |
|
 |
The Signaling Connection and Control Part (SCCP) is a
transport layer protocol which provides extended routing,
flow control, segmentation, connection-orientation, and
error correction facilities in Signaling System 7 telecommunications
networks. SCCP relies on the services of MTP for basic routing
and error detection.
Quick Specs:
- Standalone Linux/Solaris process
- 16 SCCP Bounded Entities
- 16k SCCP Translators
- 16k SCCP Destinations
- 4 MTP3/M3UA Modules connected for load sharing/fault tolerancy
- 4 SCCP Users connections |
| |
|
 |
The Message Transfer Part Level 3 (MTP3) is part of the
Signaling System 7 (SS7) used for communication in Public
Switched Telephone Networks. MTP is responsible for reliable,
unduplicated and in-sequence transport of SS7 messages between
communication partners.
Quick Specs:
- Standalone Linux/Solaris process
- 16 MTP Bounded Entities
- 1024 MTP3 Destinations
- 1024 MTP3 Routes
- 128 LinkSets
- 2048 Links
- 4 MTP2 Modules connected for load sharing/fault tolerancy
- 4 MTP3 Users connected |
| |
|
 |
The MTP Level 3 User Adaptation Layer (M3UA) as defined
by the IETF SIGTRAN enables the SS7 protocol's User Parts
to run over IP instead of telephony equipment.
Quick Specs:
- Standalone Linux/Solaris process
- 16 MTP Bounded Entities
- 1024 MTP3 Destinations
- 1024 MTP3 Routes
- 16 Associations
- 64 EndPoints
- 4 SCTP Modules connected for load sharing/fault tolerancy
- 4 M3UA Users connected |
All Gateways bring you the same LeibICT SS7XML interface that
enables your application to have an effortless roadmap from a
developing system to a critical mission application.
Our Developing and Testing Gateways come with a specific Traffic
Simulator that gives you the opportunity to test your application
with heavy traffic prior to entering the production stage.
