> 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/telecom-references/developer-reference/routing-scripts/accessing-information-about-registered-users.md).

# Accessing Information about Registered Users

### Registered Users Information

Routing scripts can access information about registered users (when either the calling or called user is a known registered user). When these fields are empty, it means that the calling/called (SIP from/to) does not correspond to a known registered user (routing script may still decide to route the call based on static routes).

Information for the called user: params\[:registered\_user] Information for the calling user: params\[:calling\_registered\_user]

These parameters are a hash of key/values that provide information about the contact. {

> contact\_list=> \[ { contact=>"\<sip:user\_name\_or\_number\@hostname:7070;transport=UDP>", -> Full contact expires=>"60", -> Contact expiry time (seconds) host=>"hostname", -> host name from the contact header name=>"user\_name\_or\_number", -> user name from the contact header nap\_in=>"NAP\_NAME", -> NAP that the contact has registered from port=>"7070", -> Port from the contact header transport=>"UDP" -> Transport type from the contact header q\_value=>"0.00", -> Q-value for the contact (for contact ordering) src\_host=>"10.0.0.10", -> Actual source IP address that the contact has registered from src\_port=>"7070", -> Actual source port that the contact has registered from src\_transport=>"UDP", -> Actual protocol that the contact has been registering with } ] }

![BackToMain](https://docs.telcobridges.com/w/images/1/1e/BackToMain.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/telecom-references/developer-reference/routing-scripts/accessing-information-about-registered-users.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.