> 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/sip-and-voip/sip/nap.md).
# NAP
A network access point (NAP) is the entry point to another network or peer - effectively a trunk group. How NAPs bind SIP, ISDN and SS7 access points on TelcoBridges systems.
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)](/telecom-references/ss7-and-signalling/ss7/sap.md), [ISDN](/telecom-references/ss7-and-signalling/isdn.md) stacks, and [SS7](/telecom-references/ss7-and-signalling/ss7.md) [ISUP](/telecom-references/ss7-and-signalling/isup.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](/telecom-references/ss7-and-signalling/ss7/circuit-identification-code.md), ISDN controlled timeslots, [SIP](/telecom-references/sip-and-voip/sip.md) 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://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-previous/web-portal-3-2/protocol-stack/protocol-stack-settings)
* [Toolpack v3.0: Network Access Points](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/protocol-stacks-general/tmedia-tdev-and-tsig-web-portal-3-0-protocol-stacks)
* [ProSBC: Network Access Points](https://prosbcdocs.telcobridges.com/configuration-details/configuration-by-web-portal-category/network-access-points-nap)
Click here for other versions
* [Toolpack v2.9: Network Access Points](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-previous/web-portal-2-9/web-portal-2-9-protocol-stacks)
* Toolpack v2.8 and earlier: documentation is no longer published. Contact [technical support](https://prosbcdocs.telcobridges.com/tmedia-documentation/operations-and-support/support/contacting-telcobridges-technical-support) if you need it.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://prosbcdocs.telcobridges.com/telecom-references/sip-and-voip/sip/nap.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.