> 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/use-cases/interoperability-examples/vitalpbx.md).

# VitalPBX

Set up ProSBC between an ITSP SIP trunk and a VitalPBX server, covering trunk creation, extensions and remote worker access.

## Introduction

This Configuration Note describes how to set up Telcobridges ProSBC for interworking between ITSP’s SIP Trunk or remote client access for VitalPBX server.

NOTE: SIP Trunk use G.711 in this test. There is no transcoding available.

### Prerequisites

* ProSBC devices must be installed as described in their respective with release 3.0.x/3.1.x. Release 3.0.x is not supported for TCP connections installation guides.
* VitalPBX.For additional information on VitalPBX, visit [VitalPBX offical web site](https://www.vitalpbx.org/).

### Example Environments for SIP Trunking with VitalPBX

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f6/Vitalpbx_Trunking_1.png/800px-Vitalpbx_Trunking_1.png" alt="SIP trunking topology: an ITSP cloud connects through ProSBC to the VitalPBX server."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [VitalPBX Trunk Creation](/configuration-details/configuration-by-use-case/sip-trunking-configuration/vitalpbx-sip-trunk-creation.md)
* [SIP Trunking Example Configuration](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-vitalpbx.md)

### Example Environments for Remote Workers with VitalPBX

<figure><img src="https://docs.telcobridges.com/w/images/thumb/2/21/VitalPbx_Remote_Workers.png/800px-VitalPbx_Remote_Workers.png" alt="Remote workers topology: a remote office and two remote-worker phones reach the VitalPBX server across the internet through a single ProSBC."><figcaption></figcaption></figure>

### Example Configuration

Step by step example Remote workers configuration.

* [VitalPBX Extension Creation](/configuration-details/configuration-by-use-case/sip-trunking-configuration/vitalpbx-extension-creation.md)
* [Remote Workers Configuration Instruction with VitalPBX](/configuration-details/configuration-by-use-case/remote-workers/remote-workers-configuration-instruction-with-vitalpbx.md)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace.md">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace.md">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call.md">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport.md">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems.md">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


---

# 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/use-cases/interoperability-examples/vitalpbx.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.