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

# SIP NAP Polling

### Polling

* In Tmedia, option ["Poll Remote Proxy?"](/telecom-references/parameter-reference/sip.md#p) is enabled by default
* Tmedia SIP polling is using SIP OPTIONS method to "poke" a SIP [Network Access Point (NAP)](/telecom-references/sip-and-voip/sip/nap.md) to see if it's alive or not, that is, [NAP](/telecom-references/sip-and-voip/sip/nap.md) availability
* Upon a response from the SIP [NAP](/telecom-references/sip-and-voip/sip/nap.md), Tmedia will determine whether to mark the [NAP](/telecom-references/sip-and-voip/sip/nap.md) as up
* If the option ["Map any response to available status"](/telecom-references/parameter-reference/sip.md#m) is unchecked, any 2xx/3xx/4xx class response to a SIP OPTIONS will bring the [NAP](/telecom-references/sip-and-voip/sip/nap.md) up
* The first time a SIP [NAP](/telecom-references/sip-and-voip/sip/nap.md) is added in configuration and configuration activated, Tmedia polls at 5 seconds, after that and general use is polling at 60 seconds
  * Since version 3.0.73 NAP SIP MAP polling is configurable with two parameters:
    * Proxy Polling Interval (Default 1 minute)
    * Proxy Polling Response Timeout (Default 30 seconds)

### [Network Access Point (NAP)](/telecom-references/sip-and-voip/sip/nap.md) Availability

If ["Poll Remote Proxy?"](/telecom-references/parameter-reference/sip.md#p) and ["Register to Proxy?"](/telecom-references/parameter-reference/sip.md#r) are both checked, only the SIP OPTIONS answers will affect the [NAP](/telecom-references/sip-and-voip/sip/nap.md) availability.

### Configuration

* [Allocating a SIP NAP Configuration v3.0](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/protocol-stacks-general/tmedia-tdev-and-tsig-web-portal-3-0-protocol-stacks#sip)

<details>

<summary>Click here for other versions</summary>

* [Allocating a SIP NAP Configuration v2.10](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-previous/web-portal-2-10/tmedia-tdev-and-tsig-web-portal-2-10-protocol-stacks#sip)
* [Allocating a SIP NAP Configuration v2.9](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-previous/web-portal-2-9/web-portal-2-9-protocol-stacks#sip)
* Allocating a SIP NAP Configuration 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.

</details>


---

# 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/sip-nap-polling.md?ask=<question>&goal=<user_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.
