This solution is an alternate solution to support the simultaneous downloads of configuration and firmware files from different endpoints through Avaya SBC. In this case, Avaya SBC does not rewrite the content of the configuration file. The file server must serve the configuration file with Avaya SBC content by using GROUPS in configuration file. Avaya SBC requires two IP addresses, one for downloading configuration/firmware files and another interface used for PPM and SIP signaling. Avaya SBC creates a relay between the endpoints and file server.
