> 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/routing-script-tests.md).

# Routing Script Tests

[Hide TOC](/telecom-references/developer-reference/routing-scripts/routing-script-tests.md)

### Introduction

The Web portal features a tool for testing scripts. You enter parameters to simulate the incoming call and after pressing the Test button, it will output selected routes and numbers. You do not need to activate the new routes, or the new scripts to use this test tool: It can be used to test the routing scripts and routing table before activating it. This is available in the Routing Scripts section of the Web portal.

### Test parameters

#### @call\_params

That variable should contain a hash of call parameters that will be passed to the routing script. This is equivalent to the incoming call parameters.

#### @nap\_list

A list of the hash containing the nap statuses. This is equivalent to the nap statuses at the time the call is to be routed.

**The nap list is hashed by the nap names in UPPERCASE.** It is important to consider this when creating new dynamic route or nap attributes that may nap names that will be used to fetch a status.

#### @params

A hash of hashes containing parameters. This hash contains bridge parameters and other kind of parameter groups may be added in the future.

```
@params = {
```

> bridge => {:announcement\_tone, "announcement.wav"}, contacts => { index=>"1", list=>\[ {:called\_number=>"6660", :priority=>"1000", :is\_number\_ported=>"0", :sip\_uri=>"", raw\_data=>"", :expiration=>"3600"}, {:called\_number=>"6661", :priority=>"1000", :is\_number\_ported=>"0", :sip\_uri=>"sip:6661\@192.168.215.127", raw\_data=>"\<sip:6661\@192.168.215.127>", :expiration=>"3600"} ], source\_indexes=>"nil,0" } }

![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/routing-script-tests.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.