For the complete documentation index, see llms.txt. This page is also available as Markdown.

Web Portal 2.8: Protocol Stacks

ISDN FAS and NFAS

(Step 1) Allocate Physical Interfaces
(Step 2) Configure ISDN-PRI Signaling
(Step 3) Modify NAP profile
(Step 4) Configure Network Access Points (NAPs)

ISDN Advanced Features

ISDN Overlap Sending

CAS

(Step 1) Allocate Physical Interfaces
(Step 2) Configuring a CAS stack
(Step 3) Modify NAP profile
(Step 4) Configure Network Access Points (NAPs)

SIP

(Step 1) Configure IP port range
(Step 2) Configure SIP Signaling
(Step 3) Modify NAP profile
(Step 4) Configure Network Access Points (NAPs)

IP Advanced Features

SIP-I SIP-T
Remote NAT Traversal
Local NAT Traversal

SS7 ISUP

MTP2-MTP3-ISUP

M2PA-MTP3-ISUP

M3UA-ISUP

SS7 Advanced Features

SCCP-TCAP

MTP2-MTP3-SCCP-TCAP

M2PA-MTP3-SCCP-TCAP

M3UA-SCCP-TCAP

H.248 MEGACO

If the Tmedia is used to forward signalling messages to the SSW, you will require to configure M2UA, M3UA or IUA before configuring H.248.

If the Tmedia is used to connect media only, then you can go straight to [[#H.248|H.248 Configuration]]

Signaling

M2UA

M3UA

IUA

Media

TDM NAP (for ISUP/ISDN)

(Step 1) Allocate TDM Physical Interfaces
(Step 2) Modify NAP profile
(Step 3) Configure Network Access Points (NAPs)

VOIP NAP (for SIP)

(Step 1) Create IP Port Ranges
(Step 2) Modify NAP profile
(Step 3) Configure Network Access Points (NAPs)

CAS NAP

(Step 1) Allocate Physical Interfaces
(Step 2) Configuring a CAS stack
(Step 3) Modify NAP profile
(Step 4) Configure Network Access Points (NAPs)

Media Gateway

(Step 1) Configure Media Gateway for H.248 mode
(Step 2) Add a New Media Gateway Controller
(Step 3) Associate NAPs Resources to H.248 Configuration

Protocol Interoperability

Early Media

Q.1912.5 Profile A-B
Q.1912.5 Profile C (SIP-I)

*Configure NAP *Configure Profile

RFC3398

*Configure NAP *Configure Profile

Q.699

*Configure NAP *Configure Profile

Redirection Scenarios

Drop

*Edit termination cause codes *Uncheck Forward SS7 raw message bytes in the gateway configuration

''

Last updated

Was this helpful?