ποΈ Overview
trunkoverview1.png
ποΈ Trunk Types
SIP trunks can connect with the PBX in different ways. The PBX offers the following types.
ποΈ Creating a Trunk
Go to your selected tenant in the Vodia PBX interface. You will see the current list of SIP trunks.
ποΈ Trunk Settings
General Settings
ποΈ Inbound Routing of Trunks
After the system has detected an inbound call from a trunk it needs to make a decision where to send the call. The routing of the call is determined by the trunk settings, specifically in the "Destination for incoming calls" section.
ποΈ Trunk ANI
When the system sends a call to a trunk, it needs to determine what caller-ID to use for that call. The outbound caller-ID is called ANI (Automatic Number Identification).
ποΈ Trunk Custom Headers
The SIP standard leaves room for interpretation for many headers, especially when it comes to connecting to the public switched telephony network (PSTN). The PBX can send just about anything in the SIP headers when making outbound calls. This is particularly useful if the trunk provider needs special parameters/values in the SIP headers.
ποΈ SMS Management
Similar to SIP trunks, tenants can connect to the outside public network through SMS providers.
ποΈ WebRTC Trunks
When using WebRTC with the Vodia PBX, you can put a talk button on your web page that your web site users can use to call your company. Instead of publishing a phone number, you can use your web site address as a single point for communication with your company. With the growing support for WebRTC in the web browsers, you can have customers call you from desktop computers, laptops, tablets and smartphones from their offices or mobile.
ποΈ Dial Plans
Dial plans are used to route (and optionally modify) specific dialed numbers to specific trunks. Dial plans are used when an internal destination could not be found.
ποΈ Connecting Branch Offices
This section describes how to connect two Vodia PBX systems so that calls from the first location to the second location will be routed through VoIP rather than through the local PSTN. This can be useful for calls inside the company where someone from the branch office 1 wants to talk to someone on the branch office 2; but it can also be used to use the branch office 2 PSTN gateway to terminate calls made from branch office 1. This can significantly lower termination costs, for example when the first office in one country and the second one in another. Two different scenarios are presented:
ποΈ CO-Lines
CO-lines can serve multiple purposes on the system. They allow you to channelize a trunk and can be used in a way similar to the CO-lines of traditional TDM-based PBX systems. Although the Vodia PBX runs calls through SIP trunks over computer networks instead of connecting to public telephone lines (at least directly), CO-lines are still useful for determining which calls are active between the system and the outside world. To begin with, each trunk may have several CO-lines, and because users can subscribe to the state of CO-lines, each CO-line name must be unique within a domain. For example, four CO-lines might be set up on trunk 1 with the names co1 co2 co3 co4, while trunk 2 might contain co5 co6 co7 co8 (the list must be delimited by spaces). The system will reject names for COβlines that are already in use by accounts or other CO-lines in the same domain. With regard to monitoring, the CO-lines that you establish can be monitored from the domain's Account list. If a CO-line is in use, it will display the extension and the outside phone number to which it is connected.
ποΈ Inter Domain Dial Plan
Domains with Non-Overlapping Extensions
ποΈ Configuring peoplefone SIP Trunk
You will receive a letter from peoplefone containing the access credentials for your trunk account. Use these credentials to log in:
ποΈ Nexxtra Registration Guide
Nexxtra Registration Guide
ποΈ Configuring Telnyx SIP Trunk
Telnyx TLS SIP trunking
ποΈ External Presence Sharing
External Presence Sharing
ποΈ Dialplan & Trunk Regex
Dialplan Regex examples
ποΈ Area Codes
Area codes are another telecom relic that we are not getting rid of anytime soon.
ποΈ Anynode
Integrating Anynode with Vodia PBX