Actions

LNP Options: Outgoing Calls LNP Mode

Revision as of 17:06, 14 April 2022 by Luc Morissette (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

No LNP insertion

  • No LNP field is inserted in the outgoing leg. (Default).

Relay LNP information

  • LNP fields are inserted in the outgoing leg only when they are received in the incoming leg.

Always insert LNP information

  • LNP fields are inserted in the outgoing leg regardless of their presence in the incoming leg.


The following table contains the pseudo-code of the mapping to the outgoing call according to the configuration AND what was present in the routing script variables:
CPN = called party number or the TO sip header
called = called number variable accessible in routing script
GAP = generic address number SS7 information element type 0xc0
ported_number = extra number type accessible in the routing script
RN = rn field in SIP request URI
bitM = SS7 Forward call indicator information element: ported number translation indicator (bit M)
X = drop number

Outgoing NAP config. Outgoing SS7 Outgoing SIP
No insertion bitM = 0
if ported_number then
ported_number => CPN
called => X

else

called => CPN
RN and ndpi not present
if ported_number then
ported_number => CPN
called => X

else

called => CPN
Always bitM = 1
ported_number => GAP
called => CPN
ndpi=yes
if ported_number then
called => RN
ported_number => CPN

else

called => CPN
RN not present
Relay called=>CPN
if ported_number then
bitM = 1
if ported_number is empty then
ported_number => X
else
ported_number => GAP

else

bitM = 0
if ported_number then
ndpi=yes
if ported_number is empty then
called => CPN
RN not present
else
called => RN
ported_number => CPN

else

called => CPN