Bind IP address for RTP relay
Bind IP address for RTP relay of a specific ARS route at Brekeke PBX (v3.7 or later)
In the case Brekeke PBX server has multiple IP addresses, generally, an appropriate IP addresses is automatically selected for relaying RTP packets. However, for controlling rtp route/traffic or other purposes, you can manually bind an IP address that is used for relaying RTP packets at each ARS route.
Example:
<Brekeke PBX>
The server has the following 4 IP addresses:
192.168.1.1
192.168.1.2
192.168.1.3
192.168.1.4
<UAC>
Ext:500, IP address:192.168.1.20
<UAS>
Ext:900, IP address:192.168.1.30
At “Pattern IN” section in ARS, you can bind an IP address for RTP relay between UAC and Brekeke PBX.
ARS Pattern IN:
[Matching Patterns:] [To:] sip:9(.*)@ [Deploy Patterns:] [Custom:] &net.rtp.bind=192.168.1.2
At “Pattern OUT” section in ARS, you can bind an IP address for RTP relay between Brekeke PBX and UAS.
Pattern OUT:
[Matching Patterns:] [To:] sip:(.+)@ [Deploy Patterns:] [Custom:] &net.rtp.bind=192.168.1.4
In this case, if the above ARS routes are set, RTP packets of a call from ext.500 to ext.900 are relayed with the following IP addresses;
UAC:ext.500 (192.168.1.20) <—–RTP packets—–>(192.168.1.2)Brekeke PBX(192.168.1.4) <—-RTP packets—–>UAS:ext.900(192.168.1.30)