When you deploy an Avaya application at main location or at a branch location on Infrastructure as a Service, ensure that you follow the networking requirements, such as, the WAN network topology, bandwidth and latency of the Avaya applications. You must adhere to the Avaya network recommendations and Infrastructure as a Service networking rules.
Infrastructure as a Service has some limitations for establishing public internet VPNs and direct connections.
For more information about Amazon VPC Limits, see the Amazon Web Services documentation at https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Appendix_Limits.html.
For more information about Microsoft Azure VPN connection limits and VPN Gateway, see the Microsoft Azure documentation at https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways.
Important:
Avaya recommends the use of direct connection in combination of a private WAN connection with Service Level Agreement that measures to ensure that the network quality is appropriate for signaling and voice traffic.
Avaya is not responsible for network connections between Infrastructure as a Service and customer premises.
