Scott wrote: > On Fri, 2009-09-11 at 16:46 -0400, Paul Mossman wrote: > > > Phase 1 is Polycom only. > > > > Though, it could easily be extended to any phone that can > report its > > MAC and specific model in the User-Agent: header of its > REGISTER messages. > > ... and which requests some default configuration that we can provide.
Pretty much yes. The phone needs to use HTTP to retrieve its registration/display configuration, which will trigger a script that generates the unique ID dynamically. (Scott pointed out this Apache trick to me. No plans to try this from the FTP server.) For Polycoms the default 000000000000.cfg file can forward the phone to an HTTP address for the rest of its configuration files. Nortel IP 1200 firmware packages have a file with a command that dictates the protocol the phone should use to retrieve its MAC configuration file. That should work too. (Not planned at this point.) Snoms I think request their configuration files via HTTP by default, which should also work. (Not planned.) This actually made me realize that the phone does not need to report its MAC in the User-Agent header. The script that is triggered should be able to determine the MAC of the phone from the HTTP URL. The script could then include the MAC in the generated registration configuration, such that the phone puts it into the user-part of the From: header in the REGISTER message. It means one more header to be examined by the auto-provisioning feature, but it eliminates the phone requirement that seems to be least commonly implemented. -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
