-
-
Notifications
You must be signed in to change notification settings - Fork 88
Outbound
Minh edited this page Dec 17, 2023
·
6 revisions
- What is interconnection: Interconnection
Outbound Interconnection indicate the policies in caller, media, interoperability, rate limiting, load balancing algorithm, etc for outbound direction
Consider any setting that you want to add, following is the configuration parameters:
Parameter | Category | Description |
---|---|---|
name |
string required
|
The name of gateway (unique) |
desc | string |
Description |
sipprofile |
string required
|
a sip profile nameid that interconnection engage to |
distribution |
enum required
|
The dispatcher algorithm to selects a destination from addresses set.weight_based : distributes calls to gateways in a weighted round-robin fashion round_robin : like weight_based with fixed value of weight to all gateways as 1 hash_callid : reserved for future use hash_src_ip : reserved for future use hash_destination_number : reserved for future use
|
gateways |
list required
|
gateway list used for this interconnection |
rtpaddrs | string |
a set of IPv4 Network that use for RTP |
media_class |
string required
|
nameid of media class |
capacity_class |
list required
|
list nameid of capacity class |
translation_classes |
list required
|
list nameid of translation class |
manipulation_classes |
list required
|
list nameid of manipulation class |
privacy |
list required
|
Privacy Header auto : pass the privacy header from inbound leg to outbound leg none : remove the privacy header screen : add screen tag to privacy header name : request to hide name number request to hide number more detail can refer rfc3325 |
cid_type | enum |
caller-id in header: rpid : Remote-Party-ID, pid : P-Asserted-Identity , none : From Header |
nodes | list |
a set of node member that interconnection engage to |
enable | bool |
enable/disable this interconnection |
Gateway Map
Parameter | Category | Description |
---|---|---|
name |
string required
|
gateway name |
weight |
int required
|
weight value (1-100) use for distribution |
distribution
example
{
"distribution": "weight_based",
"gateways": [
{
"name": "gw1",
"weight": 8
},
{
"name": "gw2",
"weight": 1
},
{
"name": "gw3",
"weight": 1
}
]
}
For every 10 calls, 8 calls will be send to gw1, 1 call send to gw2, 1 call send to gw3