Question about IP phones on server edition with secondary server 1

[Qzwsa]

Hey all.

I've got a system going in that is going to be a server edition with primary and secondary servers and 200-ish J-series phones hanging off it - the phones scattered around the area and sites connected via MPLS.

My company mostly deals with smaller installs, 10-50 phones running on 500v2's, and have only done a couple of server editions - all as a central server running 500v2's as nodes in a star topology. This on is just a server edition with phones registered to it directly.

With a single server there's no problem - add the endpoint licenses to the WebLM, point the phones at the server (using DHCP option 242 for the http server), away we go.

My question is to how the secondary server provides backup/redundancy for the phones. They are pointed at the primary for their config. Does that config contain alternate SIP domain info to point them at the secondary in case of failure?

I'm hoping someone here can shed some light on how this works so I make sure things get done right and my customer is serviced properly by the solution we are selling them.

Thanks in advance.

- Qz

 

[IPOTS]

The secondary server is used as a backup server (Non SE)
You have to configure the primary SMTP in VMPro as the 1st line. Point that to the secondary server.
Do the same on the secondly server. (Point to the primary)
In the VMPro preferences tab configure the fallback options.
In Manager on the solution, configure the resiliency options.

The primary and secondary sync using SMTP configured in the VMPro client.

 

[derfloh]

In IPO config über the SCN trunk from primary to secondary check that "backups my IP phones" (and groups).

You also have to ensure that both servers have the same SIP domain configured.

The settings are reflected in the autogenerated 46xxsettings.txt

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Qzwsa]

@derfloh

Just to make sure I'm clear...

Obviously I'll want the check boxes on - that makes total sense.

The SIP domain - does that need to be a FQDN or just the IP of the primary programmed for SIP domain in both the primary and secondary under the LAN tab?

I figured the 46xx file would include both call server addresses somehow but I've not done this before and would hate to have the primary drop and none of the phones work.

Thanks guys.

- Qz

 

[derfloh]

I would use a word (local; sip) or FQDN (sip.example.com).

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN