> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/lnp-options-outgoing-calls-lnp-mode.md).

# LNP Options: Outgoing Calls LNP Mode

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 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/lnp-options-outgoing-calls-lnp-mode.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.