System message

Brekeke SIP Sever Mirroring

Setting Up Mirroring on both Primary and Secondary server

1. At [SIP Server]>[Configuration]>[Mirroring], set
   ---------------------------------------------------
   On/Off: on
   Role: "primary" or "secondary" according to the machine role
   Virtual IP Address: VIRTUAL_IP_ADDRESS
   Pair IP Address: the other sever IP in the same IP range
   on primary server set SECONDARY_ IP_ADDRESS;
   on secondary server, set PRIMARY_IP_ADDRESS
   Mirroring Request Pattern: leave it blank
   ---------------------------------------------------
   If [Mirroring Request Pattern] is blank, all of SIP requests will be mirrored on the secondary Brekeke SIP Server.
   About more details on [Mirroring Request Pattern], please check Brekeke SIP Server document Section 3.8.8
   
   Example:
   PRIMARY_IP_ADDRESS: 192.168.200.10 /255.255.255.0 and 172.16.0.10 / 255.255.0.0
   SECONDARY_IP_ADDRESS: 192.168.200.20 / 255.255.255.0
   VIRTRUAL_IP_ADDRESS: primary IP, 172.16.0.10 / 255.255.0.0
   Gateway IP address: 172.16.0.1
   
   At pirmary server [SIP Server]>[Configuration]>[Mirroring], set
   ---------------------------------------------------
   On/Off: on
   Role: primary
   Virtual IP Address: 172.16.0.10 (VIRTRUAL_IP_ADDRESS)
   Pair IP Address: 192.168.200.20 (SECONDARY_IP_ADDRESS)
   Mirroring Request Pattern: leave it blank
   ---------------------------------------------------
   
   At secondary server [SIP Server]>[Configuration]>[Mirroring], set
   ---------------------------------------------------
   On/Off: on
   Role: secondary
   Virtual IP Address: 172.16.0.10 (VIRTRUAL_IP_ADDRESS)
   Pair IP Address: 192.168.200.10 (PRIMARY_IP_ADDRESS)
   Mirroring Request Pattern: leave it blank
   ---------------------------------------------------
   
   
2. press [Save and Update] button
   
   
3. Add the following dial plan rules on secondary SIP Server
   
   Rule: reject non-mirroring REGISTER
   -------------------------
   [Matching Patterns]
   $mirroring = false
   $primary = false
   $request = ^REGISTER
   
   [Deploy Patterns]
   $action = 200
   -------------------------
   
   
4. If Authentication for REGISTER is used, set the same realm in both Brekeke SIP Servers
   [SIP Server]>[configuration]>[SIP]>[Authentication]>[Realm(ex. domain name)]
   
   
5. Restart primary server machine
   
   
6. Restart secondary server machine

Test BSS mirroring:

1. Register UAs to Virtual IP address, the registration record will show on both primary and secondary servers when [Mirroring Request Pattern] is blank
2. Delete any registered client record from primary, the update also happens on the secondary server
3. when there is call, the session will show on both primary on secondary when [Mirroring Request Pattern] is blank

• If there are interface addresses set on the primary server>[SIP Server]>[Configuration]>[System]>[Network]>[Interface address], and these addresses will still need after failover, make sure the same interface addresses are also set on secondary server.
  
• At router used by both Brekeke SIP Servers, set port forwarding to the VITRUAL_IP_ADDRESS shared by both SIP Servers.
  
• The user authentication accounts set on primary will not be mirrored on secondary side.
  Please use shared third party database or other solutions for mirroring authentication settings on both primary and secondary servers.