> 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/telecom-references/sip-and-voip/ip-network.md).

# IP network and security

Voice over Internet Protocol (VoIP) is a means of transmitting voice calls over a packet-based transmission network. It uses [SIP](/telecom-references/sip-and-voip/sip.md), H.323, or [BICC](/telecom-references/ss7-and-signalling/ss7/bicc.md) as a [signaling](/telecom-references/ss7-and-signalling/ss7/signaling-protocols.md)/control protocol.

### TelcoBridges and VoIP

TelcoBridges' [Tmedia](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/tmedia) and Tdev families of devices support VoIP via the SIP signaling protocol as well as via dedicated on-board hardware. This hardware is optional and can be configured at initial purchase or added later via mezzanine board upgrades.

At this time, TelcoBridges does not support VoIP signaling via the H.323 or BICC control protocols.

#### Supported SIP RFCs

TelcoBridges supports the following [RFCs](/telecom-references/sip-and-voip/ip-network/rfc.md) for VoIP:

**SIP**

* RFC 3261 Session Initiate Protocol
* RFC 2976 SIP INFO Method
* RFC 3398 ISUP-SIP Mapping (\*)
* RFC 3515 Refer Method (\*)
* RFC 3578 Overlap (\*)
* RFC 2327 Session Description Protocol
* RFC 3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
* RFC 3665 Session Initiation Protocol (SIP) Basic Call Flow Examples
* RFC 3666 Public Switched Telephone Network (PSTN) Call Flows (\*)
* RFC 3892 Referred-By Mechanism (\*)
* RFC 3891 "Replaces" Header (\*)

(\*) TelcoBridges' SIP stack supports the parsing and implementation of the RFC. Not all system-level call flows are necessarily implemented in the routing engine. Contact TelcoBridges' technical support to enquiry about the implementation level of a specific call flow or RFC subsection.

### References

* [Wikipedia article](http://en.wikipedia.org/wiki/VOIP)

## In this section

* [Call Leg](/telecom-references/sip-and-voip/ip-network/call-leg.md)
* [DNS](/telecom-references/sip-and-voip/ip-network/dns.md)
* [Gateway Port](/telecom-references/sip-and-voip/ip-network/gateway-port.md)
* [Leg](/telecom-references/sip-and-voip/ip-network/leg.md)
* [NSE](/telecom-references/sip-and-voip/ip-network/nse.md)
* [Product network interfaces cross-reference](/telecom-references/sip-and-voip/ip-network/product-network-interfaces-cross-reference.md)
* [RAW IP](/telecom-references/sip-and-voip/ip-network/raw-ip.md)
* [RFC](/telecom-references/sip-and-voip/ip-network/rfc.md)
* [TLS](/telecom-references/sip-and-voip/ip-network/tls.md)
* [TUCL](/telecom-references/sip-and-voip/ip-network/tucl.md)
* [UDP IP](/telecom-references/sip-and-voip/ip-network/udp-ip.md)


---

# 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/telecom-references/sip-and-voip/ip-network.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.