> 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/protocols/nap.md).

# NAP

A Network Access Point or NAP represents the entry point to another network or destination peer (e.g. SIP proxy, ISUP interface peer, etc). A NAP can also be thought of as a trunk group.

### TelcoBridges and Network Access Points

The Network Access Point (NAP) allows for [service access points (SAPs)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/sap/README.md), [ISDN](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/isdn/README.md) stacks, and [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) [ISUP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/isup/README.md) interfaces to be associated as a combined resource for one type of access. A NAP is used to represent a collection of voice endpoints, for example: a group of SS7 [CICs](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/circuit-identification-code/README.md), ISDN controlled timeslots, [SIP](https://telcobridges.com/learning/sip-trunking/what-is-sip/) outgoing proxy to a specific provider, and more. NAPs are, later in the configuration process, used to define how calls are routed out of the Tmedia system.

### NAP Types

* SS7 (Signaling System 7)
* ISDN (Integrated Systems Digital Network)
* CAS (Channel associated signaling)
* SIP (Session Initiation Protocol)
* VOIP (Voice Over IP)
* TDM (Time-Division Multiplexing)
* Media-only (VoIP or TDM) for H248 controlled resources

### Related actions

**Refer to the appropriate Toolpack release:**

* [Toolpack v3.2: Network Access Points](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-protocol-stacks/README.md)
* [Toolpack v3.1: Network Access Points (ProSBC)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/allocating-a-sip-network-access-point-nap/README.md)

\- \[Toolpack v3.0: Network Access Points]\(/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-3-0-protocol-stacks) - \[Toolpack v2.9: Network Access Points]\(/tmedia/configuration/web-portal-2-9-protocol-stacks) - \[Toolpack v2.8: Network Access Points]\(/tmedia/configuration/web-portal-2-8-protocol-stacks) - \[Toolpack v2.7: Network Access Points]\(/tmedia/configuration/tmedia-tsig-and-tdev-web-portal-2-7-tutorial-guide)


---

# 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/protocols/nap.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.