Dale asked me to review sipXconfig changes related to that. I think I'll have a small patch related to those but I need a clarification first.
As a reminder: the proposed improvement asks for appending device ID to user authorization name. In this way various components in the system can easily tell apart which registration is associated with which device (and that it turns allows for fixing several issues related with identifying specific user agent). In addition to just assigning users to devices sipXconfig allows for configuring "external" lines. For most managed phones admin can add account on an "external" system. I am thinking that in those cases we want to stick to canonical username. Otherwise we would require that people configure accounts on external systems differently, and in any case external proxies would not benefit out of additional 'instrument' information. So I am thinking I'll add the code that would distinguish between "internal" (lines with non-null user) and "external" lines. Anybody sees problems with that approach? Another question: is there any reason I should not enable new username format for all the phones sipXconfig supports (well hardphones - since on softphones your phone if already *is* your username)? Or do we want to start small, test it and add new phones gradually? Damian _______________________________________________ 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/
