Back-end Servers Setup
- Dial plans used on front-end Brekeke SIP server
Priority Name Matching Patterns Deploy Patterns 1 REGISTER from NAT $request = ^REGISTER
P-Behind-NAT = Yes®ister.contact.nat = true
&net.registrar.adjust.expires = 90
$continue = true2 REGISTER $request = ^REGISTER
X-Remote = (.+)®ister.contact.addrport = %1
$action = registerex3 INVITE from NAT $request = ^INVITE
P-Behind-NAT = Yes$nat = true
$rtp = true
$continue = true4 INVITE to NAT $request = ^INVITE
$regdb.innat = true$nat = true
$rtp = true
$continue = true5 INVITE $request = ^INVITE
$regaddr = (.+)
$reguri = (.+)
$addr = (.+)X-Remote = %1
To = %2
$target = %3Note:
Click [Apply Rules] button to make dial plans take effect. - Share the databases used for all back-end Brekeke SIP servers
From each back-end Brekeke SIP Server admintool > [Configuration] > [Database/Radius],
set the same third-party database access information - From each back-end Brekeke SIP Server admintool > [Configuration] > [System] -> [Address Filtering], set
[IP Address filter]: allow
[Filter pattern]: ^172.16.0.1$ ( front-end server IP address )
This setting makes back-end servers only accept packets from front-end server - From each back-end Brekeke SIP Server admintool > [Configuration] > [SIP] -> [SIP exchanger],
set [B2B-UA mode] ON - Enable [Authentication] as your need
- Set correct system time at all Brekeke SIP Servers