Introduction
Interconnection Trunk is the trunk group used to connect one or mutiple carriers’ networks with B3networks's network for the purposes of exchanging Telecommunications traffic.
Edge Server is designed to be reliable and flexible. It allows system admin add/remove/update attributes of the interconnection on the fly, which means that the change will not impact service operation including call drop, audio. For example, you have calls which rely on the Interconnection Trunk named ANYNAME, and need to re-prioritize codec list or change signaling address, the change can be submitted immediately without worrying about affecting the current active calls.
Protocol
Edge Server represents a full user agent and controls the necessary signaling protocol and media streaming to process calls.
Edge Server uses Session Initiation Protocol (SIP) for signaling and Real Time Transport Protocol (RTP) for media streaming to other endpoints.
SIP is a text-based protocol, defining the specific format of messages exchanged and the sequence of communications for the cooperation of the participants. SIP carries SDP in payload to perform media negotiation and setup to employ RTP. SIP is independent with transport protocol, and can use UDP/TCP/TLS.
Functions
By using interconnection’s attributes, Edge Server is able to provide powerful functions with minimal and simple configuration:
- Health-check Voice Server by SIP OPTION with configurable ping interval
- Load balancing among interconnect signaling
- Outbound digest authentication
- Secure communication with TLS/SRTP
- Flexible update setting of codec, number translation, rate limit, or SIP header manipulation for interoperability
- Easy to scaling edge cluster with distributed node members.
- Firewall management automatically
- Re-routing indirected call
- Suspend interconnection trunk
Parameters
Below table shows parameters in a particular trunk:
Parameter | Sub-param | Value | Direction | Description |
|---|---|---|---|---|
| Name | Trunk Name E.g: NAME_IN NAME_OUT | IN - OUT | Trunk Name should be a unique capital name | |
| Capacity | Preset Capacity profile | IN - OUT | Security end force cps and concurrent call | |
| Codec | Preset Codec profile | IN - OUT | Codec profile | |
Direction |
| IN - OUT | Indicate the call direction with Edge is an origin
| |
Outparam | Username | Auth Username | OUT | Digest authentication for outbound gateways |
Password | Auth Password | OUT | ||
| Ping | 30s - 3600s | OUT | Interval in second for sending health check SIP OPTION | |
Signallings | ip | Ip address | IN - OUT | Set of signalings that will be used to process the SIP protocol: ip will be used to recognize inbound interconnect so it must be unique forinbound direction. |
port | Network port | OUT | ||
protocol | udp, tcp, tls | OUT | ||
Medias | Network address | IN - OUT
| Set of network addresses that will be used to process RTP streams. The media port allows 10000-65000 | |
| Toggle to turn off Trunk | on/off | IN - OUT | ||
| Nodes | Cluster members | IN - OUT | List of node members in cluster where the trunk engages to | |
| Interface | Interface name | IN - OUT | The network interface that the trunk engages to. | |
| Translation | Translation CLID (optional) | Preset Translation CLID | IN - OUT | List of translation profiles that apply for CLID |
Translation DNIS (optional) | Preset Translation DNIS | IN - OUT | List of translation profiles that apply for DNIS | |
| Manipulation Profile (optional) | Preset Manipulation Profile | IN - OUT | List of manipulation profiles. | |
How to create a new trunk
- Go to Trunks > Create trunk
.
. - Give your trunk a name > Choose a preset Capacity and Codec > Choose Direction for your new trunk > Configure Username, Password and Ping if the direction is outbound (optional) > Fill in Signaling, Port, Protocol, Media based on your vendors' interconnection form
.
- Drag the chosen Translation DNIS, CLID and Manipulation Profile to the right column (optional) > Create
.
. - Finish
.