Close
 Brekeke Website | Bekeke SIP Server | Brekeke PBX   
Notification:  
v3.0.2 Professional
Login
Loading

Set up Mirroring at bundled SIP Servers

Note:
If shared third party database set at both primary and secondary Brekeke PBX bundled SIP server > [Database], no mirroring settings are needed.

Mirroring settings at both primary and secondary Brekeke PBX bundled SIP Servers.
  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 address in the same IP segment
    on primary server set SECONDARY_ IP_ADDRESS;
    on secondary server, set PRIMARY_IP_ADDRESS
    Mirroring Request Pattern: ^REGISTER
    ---------------------------------------------------

    The setting of [Mirroring Request Pattern] cannot be changed. Only REGISTER SIP requests on primary server can be mirrored on the secondary Brekeke PBX bundled SIP Server. This will make both primary and secondary server have the same registered clients.

    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/255.255.0.0

    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: ^REGISTER
    ---------------------------------------------------


    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: ^REGISTER
    ---------------------------------------------------


  2. press [Save and Update] button

  3. Add the following dial plan rule on secondary SIP Server, and click [Apply Rules] button

    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 at both PBX bundled SIP Servers
    [SIP Server]>[configuration]>[SIP]>[Authentication]>[Realm(ex. domain name)]

  5. Restart primary server machine

  6. Restart secondary server machine
Now, you can see
Primary Brekeke PBX bundled SIP Sever > [Server Status] > [mirroring-role]: primary
Secondary Brekeke PBX bundled SIP Server > [Server Status] > [mirroring-role]: secondary
Access Brekeke PBX admintool from Virtual IP address, it will be primary server.

Test mirroring:

  1. Register UAs to Virtual IP address or router's global IP address, the registration record will show on both primary and secondary servers.
  2. Delete any registered client record from primary server, the update also shows on the secondary server
  3. when there is call, the session will only show on primary server because [Mirroring Request Pattern] is only for REGISTER. No session will keep on secondary server.