> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/protocol-stacks-sip/creating-a-sip-registrar.md).

# Creating a SIP Registrar

#### ***Applies to version(s): v3.0***

A SIP registrar represents a SIP endpoint that provide a location service. You must configure SIP Registrar for your system. The first step in doing so is to select your SIP Domain:

1- Click on your domain in the **SIP Domain List**

![Select SIP Domain](https://docs.telcobridges.com/w/images/4/42/Select_SIP_Domain.png)

2- Click **Create New SIP Registration Registrar**

![Create New SIP Registrar](https://docs.telcobridges.com/w/images/b/bf/Create_New_SIP_Registrar.png)

3- Create the new SIP Registration Registrar

* Enter a **Name** for the SIP Registration Registrar
* Enter an **Address** to reach the registrar
* Select the registrar destination **Port**
* Select which local interface will be use to send REGISTER message in **SIP Transport Server**
* **Poll Registrar** enabled by default. Sends an OPTIONS message to determine registrar availability.
* **Polling Interval** in seconds. Time between each OPTIONS sending message.
* **Response Timeout** in second. Maximum waiting time for a response to a registrar polling.
* Click **Create**

![Create New SIP Registrar3](https://docs.telcobridges.com/w/images/d/dd/Create_New_SIP_Registrar3.png)

4- Verify that the **Sip registration registrar was successfully created** message appears

![Create New SIP Registrar2](https://docs.telcobridges.com/w/images/7/75/Create_New_SIP_Registrar2.png)


---

# 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://tmediadocs.telcobridges.com/other-pages/protocol-stacks-sip/creating-a-sip-registrar.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.