> 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/troubleshooting-and-support/troubleshooting-tips-and-actions/routing-scripts/update-your-routing-scripts.md).

# Update Your Routing Scripts

When you update your Tmedia Firmware, routing scripts are not automatically update in order to preserve any custom modifications a user may have made.

A customer may have multiple Script Lists that are different versions and saved in the same config. But only one Script List can be used at a time.

In order to check which Script List you are using go to the **Gateway** and check the **Use script** parameter.

<figure><img src="/files/W7NR9ambGIkJkceL7RxK" alt=""><figcaption><p>The Routing Script List used in this screenshot is named 3.3.6.68</p></figcaption></figure>

Clicking on **Gateway > Routes > Routing Script** will bring you inside your used Script List.

There you can check your current version or navigate back to your Script Lists to generate the current list.

<figure><img src="/files/tPgHcThJe76okWUb7pID" alt=""><figcaption><p>To check your version click on <code>base_routing.rb</code>and <code>simple_routing_sbc.rb</code> </p></figcaption></figure>

After you navigate to the lists you can click [Create New Script](#user-content-fn-1)[^1] to create the default scripts concurrent with your firmware version.

<figure><img src="/files/OnScfFcnExHw2IXiBRrj" alt=""><figcaption><p>Create default script files should be checked to generate the default scripts, name can be custom.</p></figcaption></figure>

After generation you can check `base_routing.rb`to confirm the proper version.

<figure><img src="/files/zdpuvcN3azGSMkkoFd82" alt=""><figcaption></figcaption></figure>

[^1]: Link in top left


---

# 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/troubleshooting-and-support/troubleshooting-tips-and-actions/routing-scripts/update-your-routing-scripts.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.