Micollab with two MBG

[sunspark]

Hi ,

I have :

-Micollab in LAN
-MBG1 in DMZ1
-MBG2 in DMZ2

i want to use two MBG for resilience

so from internal DNS : mbg.mycompagny.com resolve Both Mbg1 and Mbg2
From Extenal DNS : mbg.mycompagny.com resolve both Mbg1 and Mbg2

When MBg1 and MBG2 runs , evertyhing works.

But when i shutdown MBG1 i'm not able to switch to the second MBg2.

Maybe because External DNS (record type A) can't switch to the second Mbg ?


Any help will be appreciated.

[Navarre]

What clients are we talking about here? This is client behaviour, ultimately.

[sunspark]

Micollab client .

[acejavelin]

MiCollab Client doesn't support resiliency, only MiNet devices do.

[sunspark]

MiCollab Client doesn't support resiliency, only MiNet devices do.

Don't agree with u .

MiCollab Client for Mobile softphones support SIP resiliency with an MBG, such that if the call
signaling path is disrupted or the MBG is taken out of service, an already active softphone
re-registers with an alternate MBG to regain service


How it works
In an Enterprise or Cloud environment, the softphones are connected to the network through
an MBG cluster. You use DNS to map the Fully Qualified Domain Name (FQDN) of the MBG
cluster to the hostnames of the member MBGs. This mapping is contained in the configuration
file on the DNS server. If the MBG that supports the softphones goes out of service, the
softphones use the configuration data that they received from the DNS server to register with
an alternate MBG. This allows the softphone to obtain service.


Attached More informations

[acejavelin]

MiCollab Client doesn't support resiliency, only MiNet devices do.

Don't agree with u .

MiCollab Client for Mobile softphones support SIP resiliency with an MBG, such that if the call
signaling path is disrupted or the MBG is taken out of service, an already active softphone
re-registers with an alternate MBG to regain service


How it works
In an Enterprise or Cloud environment, the softphones are connected to the network through
an MBG cluster. You use DNS to map the Fully Qualified Domain Name (FQDN) of the MBG
cluster to the hostnames of the member MBGs. This mapping is contained in the configuration
file on the DNS server. If the MBG that supports the softphones goes out of service, the
softphones use the configuration data that they received from the DNS server to register with
an alternate MBG. This allows the softphone to obtain service.


Attached More informations

Actually didn't know that... Are your mbg's clustered?

Sent from my Moto G (5) Plus using Tapatalk

[sunspark]

MiCollab Client doesn't support resiliency, only MiNet devices do.

Don't agree with u .

MiCollab Client for Mobile softphones support SIP resiliency with an MBG, such that if the call
signaling path is disrupted or the MBG is taken out of service, an already active softphone
re-registers with an alternate MBG to regain service


How it works
In an Enterprise or Cloud environment, the softphones are connected to the network through
an MBG cluster. You use DNS to map the Fully Qualified Domain Name (FQDN) of the MBG
cluster to the hostnames of the member MBGs. This mapping is contained in the configuration
file on the DNS server. If the MBG that supports the softphones goes out of service, the
softphones use the configuration data that they received from the DNS server to register with
an alternate MBG. This allows the softphone to obtain service.


Attached More informations

Actually didn't know that... Are your mbg's clustered?

Sent from my Moto G (5) Plus using Tapatalk

It seems works now !

So

I put Micollab in ZONE "LAN"

MBG 1 in ZONE "DMZ1"
MBG 2 in ZONE "DMZ2"

In the default zone of DMZ1 i put DMZ2
and in the default zone of DMZ2 i put DMZ1
after that u have to create SRV and A records ( attached engeneering guideline)

Enjoy.