AG4124 Resiliency with MiVB

[danramirez]

Hi,

AG4124 documentation says this unit is resilient when connected to MiVB:

"10.1.3 Resiliency
The resiliency scenarios supported by the AG4124 Analog Gateway when connected to MiVoice Business
is listed as follows:
Note:
The scenario names have been chosen for convenience for understanding the context related here.
• Scenario 1: Resiliency is achieved by utilizing the ability of DNS servers to provide multiple IP
addresses against a single FQDN. This is generally achieved by using DNS SRV or A records. This
scenario does not require anything from a SIP Endpoint except support for standard DNS behavior.
• Scenario 2: The device has inherent knowledge of the primary and secondary MiVoice Business and
will switch between them if a SIP request (REGISTER, INVITE, or SUBSCRIBE) times out. Behavior
will be characterized based on whether and when the device returns to primary MiVoice Business. This
scenario has some dependency on user action in detecting a failure, especially if configured with a long
registration expiry time, in which case there is chance of a user experiencing a long delay making a call
increases.
"

I Have followed all configuration step as per the manual but it does not work for me.

The manual doesn't say how to configure the MiVB side.

Scenario 2 says The device has inherent knowledge of the primary and secondary MiVoice Business. How does this happen? Is it because one needs to configure the secondary node when creating the user on MiVB? Is it during the registration process that the unit inherits the IP addresses of the primary and secondary controller?

Will this work with single line licenses?

Please let me know if you have managed resiliency with the AG4124.

Regards,

Daniel

http://www.hatkanatelecom.com

 

[Billz66]

i would imagine ( i dont have access to a AG4124) that you have to set the unit to use dns srv to determine the mivb addresses ( same as any other SIP device)

AG tries to register ext , does dns srv lookup gets primary and secondary returned
tries primary , if that fails tries secondary

it says that in section 10.1.3 Resiliency on PDF page 110

then use the srv address for the SIP server

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

 

[danramirez]

Hi Bill,

I think the AG4124 software is at very early stage.

First of all the SIP Server field only allows you to enter IP Addresses, it does not allow names for the SRV or NAPTR Records.

I had to modify the cfg file, replace the IP address with the FQDN, an then restore the backup.

I managed to make it resilient by entering NAPTR Query in the Domain Query type, It was impossible to make it to work by selecting SRV Query.

Also, I had to set everything to UDP 5060. It didn't work with TLS 5061 which is my next goal.

This is what I have in my DNS Server:

It seems the unit doesn't understand the SIPS+D2T, this is what I see in the syslog:

Any suggestions? I have raised a ticket with Mitel Support but it is still under Investigating.

Regards,

Daniel

http://www.hatkanatelecom.com