Resiliency for Teleworker SIP Phones (MiCollab)

[Joe King]

Hello,
Currently have a MiCollab in LAN mode with a clustered MBG to a MBG in DMZ. Teleworker phones both MiNet and SIP work fine for MiCollab Client.

I need to add resiliency for Teleworker server so am deploying a second MBG in DMZ.

Been reading in docs (yeah I know) resiliency is achieved through DNS.

Anyone done this? Hows it done?

Thanks in advanced.

 

[Billz66]

for minet phones you can add mbg to the cluster and set weighting to handle what they connect to
existing phones would need a reset and should then get both public Ips .

for sip you would need the voice component to use DNS-SRV
set public primary to 1st Pub ip or mbg name
set public secondary to 2nd Pub ip or mbg name

set deployment to use dns-srv name




If I never did anything I'd never done before , I'd never do anything.....

 

[Joe King]

Thank you.

 

[jpruder]

You can set up zones and fail over to the backup

 

[Joe King]

Thanks for your replies. one more thing. Currently the MiCollab client registers to micollab.abc.com, if we create two SRV records for the two standalone MBGs

mbg1.abc.com and mbg1.abc.com does DNS_SRV need to map to these two new FQDN's.

What I dont want to happen is all the current clients have to re-register. could I create a new deployment profile which uses the new DNS_SRV

 

[Valamagules]

Sorry if I am late to the party

For MiNet Teleworker resiliency, you will need to add the MiNet failback addresses under the Networks Tab for both MBGs.
Also in Setting, ensure the Option "Relax set RTP checks" is enabled (if remote sites have a dual internet connection).

For MiCollab client, you will require 2 x MBG FQDN as SRV hostnames and targets to the MiCollab FQDN.

Host: sip._tcp
•Priority 1 for MBG1 FQDN
•Priority 2 for MBG2 FQDN
•Weight 10 for both MBG
•Port 5060

Host: sips._tcp
•Priority 1 for MBG1 FQDN
•Priority 2 for MBG2 FQDN
•Weight 10 for both MBG
•Port 5061

You can test here -

https://dns.pexip.com/

to see if you DNS SRV works ok.

Yes you can use a new deployment profile to test this before rolling it out to existing uses.

Clever men learns what Wise men shares!