> 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/configuration-details/configuration-by-use-case/remote-workers/configuration-files-for-remote-office-workers.md).

# Configuration Files for Remote Office/Workers

Sample ProSBC configuration files for remote office and remote worker deployments, with and without NAT, plus the parameters to replace in each JSON file.

## Introduction

ProSBC Configuration Files for Remote Office/Workers Scenario Tutorial provides you with a scenario-based approach to configuring ProSBC systems, using sample configuration files. Complete general installation configuration steps, before you begin configuring your specific application.

### Prerequisites

ProSBC devices must be installed as described in their respective installation guides.

### Typical Remote Office/Workers Sample without NAT

<figure><img src="https://docs.telcobridges.com/w/images/thumb/9/99/ProSBC_Remote_Workers_sample_config.png/800px-ProSBC_Remote_Workers_sample_config.png" alt="Without NAT: remote workers and a remote office cross the internet straight to the ProSBC WAN_00 interface, with LAN_00 facing the enterprise IP-PBX and fax server."><figcaption></figcaption></figure>

### Typical Remote Office/Workers Sample with NAT

<figure><img src="https://docs.telcobridges.com/w/images/thumb/7/7c/ProSBC_Remote_workers_sample_config_NAT.png/800px-ProSBC_Remote_workers_sample_config_NAT.png" alt="With NAT: the same topology adds a NAT device between the internet and the ProSBC WAN_00 interface, ahead of the enterprise IP-PBX and fax server on LAN_00."><figcaption></figcaption></figure>

### Modifying configuration file

You can download sample configuration for Remote Office/Workers scenario from below;

[Remote Office/Workers Sample Configuration without NAT](https://docs.telcobridges.com/w/images/7/7f/Rmt_main_config.json)\
[Remote Office/Workers Sample Configuration with NAT](https://docs.telcobridges.com/w/images/e/e9/Rmt_main_config_nat.json)

* Open the json file with a text editor
* Replace following parameters in the file
  * \[tbsbc] with the hostname that you gave on installation stage
  * \[WAN\_00\_IP] and \[LAN\_00\_IP] with IP addresses for WAN and LAN
  * \[WAN\_00\_Subnet] and \[LAN\_00\_Subnet] with IP subnets for both networks (format: 255.x.x.x)
  * \[WAN\_00\_Gateway] and \[LAN\_00\_Gateway] with Gateway IP addresses
  * \[WAN\_00] and \[LAN\_00] with currently configured IP interfaces (for example voip0 and voip1)
  * \[Registrar\_Domain\_Name] with Registrar Domain (IPPBX Domain - must be IP address in version 3.0)
  * \[All Registrar\_IP] with Registrar IP Address (IPPBX IP Address)
* If you downloaded Remote Office/Workers Sample Configuration with NAT file please replace the following parameter too
  * \[NAT\_IP\_Address] with your External IP (Public IP of the NAT device)
* Save the file

### Uploading and activating the sample configuration

* You need to use an SFTP client to upload the configuration file to ProSBC
* After upload the file using the following commands from CLI
* For Remote Office/Workers Sample Configuration without NAT (Change user/password for web interface)

```
 tbconfig -u root -p root -C /configurations Rmt_main_config.json name="main_config"
 tbconfig -u root -p root -U /systems/system_1/target_configuration="main_config"
```

* For Remote Office/Workers Sample Configuration with NAT

```
 tbconfig -u root -p root -C /configurations Rmt_main_config_nat.json name="main_config"
 tbconfig -u root -p root -U /systems/system_1/target_configuration="main_config"
```


---

# 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/configuration-details/configuration-by-use-case/remote-workers/configuration-files-for-remote-office-workers.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.