Frequently asked questions about YateSTP

SIGRAN/M3UA

Supported

Support MAP V1,2,3

Supported

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

Partially supported

Notes: MTP routes by DPC only

Flexible routingby SCCP-level parameters

Supported

MTP L3 header manipulation OPC replacement,OPCtransparent translation, DPC replacement, Route selection by MTP parameters

Not supported

Flexible routes’ redundancy

Supported

E1/LSL

Partially supported

Notes: via Sangoma card or external M2UA gateway

MNP(mobile number portability)

Supported

Notes: via TS 23.066 or customer provided database or API

TCAP Routing based on MAP operation code and CAP operation Code

Not 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

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

Supported

E1/HSL

Partially supported

Notes: via external M2UA gateway

Routing by TCAP operation codes (for MAP & CAP)

Not supported

Special TT (-s) for outgoing traffic

Supported

SIGRAN/M2PA

Supported

SIGRAN/M2UA

Supported