AADS 8.1.5 1

[fondog2]

Hello to all,
I have a couple of questions. The first is do any of you have a good document that explains how this application works? We have multiple sites with each having its own 46xxsettings file as each site has different items that are needed. We would like to be able to separate each out using the AADS. The second question is with our remote workers. Prior to coming onboard the administrator was manually configuring hard phones using the IP address instead of the FQDN. Can AADS push new settings to change from pointing to the IP to name? Asking as we are tabling changing SIP providers.

Thank you,

 

[kyle555]

SIP provider is irrelevant. Phones point to a call server.

9600 phones can only point to an IP
J100s and workplace can point to FQDNs.
READ THE BELOW VERY CAREFULLY!

As far as peeling out site specific settings, it has a basic httpd server in there like Utility Services had. You can have folder site1 and site2 and have DHCP say HTTPDIR=site1 to have phones pickup

http://aads/site1/46xxsettings.txt

Hardcoded settings override dynamic ones. If you hardcode a phone to point to server 1.2.3.4, nothing short of changing that or wiping the phone will make it honor a settings file that says to point somewhere else.

Unless you're talking about autoconfiguring workplace or having contact lookups and stuff, your question is more around a basic http server for provisioning phones - which AADS includes.

What I would do is have DNS entry aads.you.com internally point to AADS and externally point to the SBC.
Then all phones for external use get booted once on the corporate network to get DHCP string 242 of HTTPSRVR=aads.you.com. Skip this step if you have a DES account and J100 phones because DES on the internet can point J100 phones wherever you want for a settings file.

In any case, it'll get a settings file that says HTTPSRVR=aads.you.com and HTTPDIR=remote
Then you'd have the SBC with a HTTP relay pass that along to

http://aads.you.com/remote/46xxsettings.txt

Anyways, depending on what models you need to do this for, and whether you require them staged on site or not, and whether you need them to move in and out of the office afterwards will define the right recipe.

It's not a AADS question and more a settings file question.

## SIP_CONTROLLER_LIST specifies a list of IPv4 SIP controller designators,
##  separated by commas without any intervening spaces. 
##  The list is used on IPv4-only and dual mode phones (if�SIP_CONTROLLER_LIST_2 is not provided).
##  Each controller designator has the following format:
##  host[:port][;transport=xxx]
##  host is an IP address in dotted-decimal (DNS name format is not supported unless stated otherwise below).
##  [:port] is an optional port number.
##  [;transport=xxx] is an optional transport type where xxx can be tls, tcp, udp or auto.
##  "auto" means that the preferred transport is determined based on Name Authority Pointer (NAPTR) record retrieved for the SIP Controller FQDN configured. SRV records can be then used to retrieve port and the final FQDN for use.
##  If a port number is not specified a default value of 5060 for TCP and UDP or 5061 for TLS is used.
##  If a transport type is not specified, a default value of tls is used.
##  The value can contain 0 to 255 characters; the default value is null ("").
##  This parameter is supported by:
##       J129 SIP R1.0.0.0 (or R1.1.0.0); J100 SIP R2.0.0.0 and later; J139 SIP R3.0.0.0 and later, J159 SIP R4.0.3.0 and later, J189 SIP R4.0.6.1 and later
##	   For Aura environment, FQDN format is supported for J100 phones starting R4.0.11.0 
##		   For the FQDN, DNR SRV records are not used, only DNS A and AAAA records are used.
##         If the list contains a mix of FQDNs and IP addresses, only FQDNs will be used, IP addresses will be ignored.
##	   For OpenSIP environment, only one SIP controller is supported. 
##         "auto" is supported in OpenSIP environment only. "auto" is supported by J100 SIP R4.0.0.0 and later.
##       J100 SIP R4.0.0.0 and later; used on dual mode phones if�SIP_CONTROLLER_LIST_2 is not provided. 
##          When 3PCC_SERVER_MODE = 1 (a BroadSoft server), SIP_CONTROLLER_LIST should contain one sip controller entry and host should be an FQDN (DNS name format).
##          The FQDN would resolve to primary and alternate servers to support redundant configuration.
##          When 3PCC_SERVER_MODE = 0 (a generic SIP server), SIP_CONTROLLER_LIST may contain one or two sip controller entries (to support redundant configuration).
##          �host� of sip controller entry could be an FQDN(DNS name format) or an IP address. If FQDN is provided, it will resolve to one primary server. 
##          IPv6 is not supported for OpenSIP environment. In OpenSIP environment, there is no support for resolving an FQDN to an IPv6 address in the SIP_CONTROLLER_LIST or SIP_CONTROLLER_LIST_2. 
##          IPv6 is supported for Aura environment and in Aura there is no support for FQDN yet (only IP addresses can be configured).
## 	 J169/J179 SIP R1.5.0 
##	 Avaya IX Workplace 3.1.2 and later; DNS name format is supported.
##       Avaya Vantage Devices SIP R1.0.0.0 and later; DNS name format is supported; UDP is not supported; not applicable when Avaya Vantage Open application is used. 
##         IPv6 address is supported as well for Aura environment only. SIP_CONTROLLER_LIST_2 is not supported.
##       Avaya Vantage Connect Application SIP R1.0.0.0 and later; DNS name format is supported; TCP/TLS are supported in Avaya Aura, Avaya IP Office and OpenSIP environments. UDP is supported in OpenSIP environment only. 
##         OpenSIP environment is supported from R2.0.1.0 and later. The configuration file from the Avaya Vantage Device combines the configuration of this parameter from all sources (in the following order):
##         UI, LLDP, DHCP, this file, PPM and AADS. R2.2.0.0 and later - IPv6 address is supported as well for Aura environment only. Please note that for dual stack controllers (IPv4/IPv6), 
##         then FQDN shall be used to avoid multiple registration to the SAME controller over both IPv4 and IPv6 addresses. SIP_CONTROLLER_LIST_2 is not supported.
##       96x1 SIP R6.0 and later
##       96x0 SIP R2.4.1 and later
##       H1xx SIP R1.0 and later; udp is not supported.

In your site specific DHCP 242 strings, you'd have HTTPSRVR=aads.you.com and HTTPDIR=site1 or whatever.

 

[fondog2]

Kyle555,
Thank you for your response. I have a lot of respect for you out here. Avaya makes AADS sound like it is a do all. I will be honest I don't know poop about it. I will say though your first two statements are incorrect. The SIP provider does matter as we will have to change all the IP's that the remote worker phones are pointing to which is the external IP of the SBC that reverse proxy's to the utility server. They own the IP's from what they are stating. I may not have made that clear in my example. 9611 telephones can have the FQDN entered in them as I have tested this, which is why I wanted to see if we can push this out to the remote worker phones. Since Covid we have a crap load of remote workers and trying to walk one of them through how to change these settings is going to really suck. I will see if I can get our network team to work with us on DHCP and pointing to those groups are explained and see what I come up with. either way let you know. Thank you again. Gold star to you.

 

[kyle555]

OK, so you might be changing ISP. Any reason you'd change public IP the phones point to, then yes, that matters. I read "SIP provider" as PSTN provider.

SIP_CONTROLLER_LIST says "host" means IP address unless explicitly stated otherwise - like for J's at 4.0.11 upwards. And not DNS SRV, only DNS A records. I'm not so sure 96x1 can have a FQDN.

AADS is kinda sorta a do-all, but endpoint management with settings files is still cumbersome and it doesn't change that or make it any easier (yet)