Frequently asked questions about YateSTP

Flexible routingby SCCP-level parameters

Supported


Special TT (-s) for outgoing traffic

Supported


Flexible routes’ redundancy

Supported


E1/LSL

Partially supported

Notes: via Sangoma card or external M2UA gateway


E1/HSL

Partially supported

Notes: via external M2UA gateway


SIGRAN/M2UA

Supported


SIGRAN/M2PA

Supported


SIGRAN/M3UA

Supported


MTP L3 Routing based on OPC, DPC,NI and service indicator

Partially supported

Notes: MTP routes by DPC only


SCCP Routing based on Calling part, Called party, TT and NAI

Supported


SCCP maniputing Calling party replacemet, Called party Replacement, TT replacement in calling pary and called party address, NAI replacement, MTP header manipulating depend on SCCP address,routing selection by SCCP parameters, redundancy route selection in case of main route unavailability

Supported

Notes: no direct manipulation of MTP header is supported, can SCCP route between MTP domains, can SCCP route between ITU and ANSI networks


MNP(mobile number portability)

Supported

Notes: via TS 23.066 or customer provided database or API


Support MAP V1,2,3

Supported