Avaya autoconfig - use ASBCE B1's FQDN

[M3A]

Hello,

I'm trying to use autoconfig to use email address from internal and external networks, I configured dynamic configuration file on AADS with SIP_Controller_list adding SBCE_B1.domain.com where it would be resolved to public SBCE B1 address (external) and to private SBCE address B1 (internal).. I use private and public IP addresses on SBCE B1 and it's being NATted on Customer's firewall.

I see traces where dynamic configuration file is being retrieved but SIP_Controller_list is not as configured on AADS, but it's showing SM100 private IP address, this cause phone service not available. I believe I'm missing something!!

 

[TelecomRob]

You need to configure split horizon. You should have one single domain name.
sip.companydomain.com

On your external DNS server configure the A record to go to your SBC B1 interface. On your internal DNS server configure the A record to go to the SM100 address.

For email configuration you will need to configure the PTR and TXT records. This can be found here:

https://documentation.avaya.com/bun...ices_R8.0/page/Setting_up_the_DNS_server.html

 

[M3A]

Thanks for your response and recommendations, I already did so but when I try to sign in externally client gets SM private IP address and then client prompts phone services are not available.

 

[TelecomRob]

Can you share the domain name so we can check the DNS records? Only way I think this could happen is if your client is getting the internal record externally.

 

[M3A]

I believe it's taking the IP address from user's SM profile that overrides the SIP Controller list configured on AADS, as I'm using one FQDN in AADS config file that resolves to Public SBCE B1 externally and Private SBCE B1 internally.. I'm not routing to SM100 internally.. So this should eliminate the possibility of resolving the incorrect FQDN..

In both test scenarios, client gets the SM private IP address.. what I know that SMGR user's SM profile overrides the 46xxsettingsfile on US/AADS. I configured MPP mapping on SBCE with no joy

 

[kyle555]

Trace it with PPM enabled. PPM will override whatever came in the settings file.

So, you've got the part in SM-->network config-->remote access where you map the interfaces. And you got the PPM mapping profile in the SBC. That's the part where SM sends PPM with the SM100 IP and the SBC matches on that and replaces with the B1 DMZ or public IP.

If you see a PPM trace returning PPM to the endpoint on the internet with a SIP proxy that's a private IP, then you need to look at the PPM mapping profile in the SBC.

 

[M3A]

Hello Kyle555,

Thanks for your response and sorry for late reply, I have configured remote access where mapped the interfaces on SM as following:
Reference A: <SBC B1 DMZ private ip>
Reference B: <SBC A1 ip>

And PPM mapping profile in the SBC as following:
Server Type: Session Manager
Server Address: <SM sm100 ip>
SBC device: Avaya-SBC
Signaling IP address: <SBC B1 DMZ private ip>

And Reverse Proxy:
Listen IP: <SBC B1 DMZ private ip>
Listen Port:443
Connect IP: <SBC A1 ip>
PPM Mapping Profile: PPM_Profile
Server Addresses: <SM sm100 ip>:443

and from AADS I set SIP_Controller_list to public IP FQDN <SBCE-RW.domain.com> that should be resolved to SBC B1 public IP externally and SBC B1 private IP internally.

 

[G van Hamburg]

I think you need to adjust the SM100 certificate to match your DNS.

Freelance Certified Avaya Aura Engineer

 

[kyle555]

But what do you get when you trace?

 

[M3A]

Issue has been resolved after enabling Split Horizon DNS Mapping in (AADS > Dynamic Configurations > DNS Mapping) where I added SM SM100 private IP and mapped it to FQDN "SBCE-RW.domain.com".