On Thu, 2009-10-29 at 10:28 -0400, Damian Krzeminski wrote: > 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?
We must use that approach, unless we know that the external system to which the phone is registering is sipXecs >= 4.2! Otherwise, the auth user name the phone sends to the external system won't have the value that the user entered into the UI. We might consider adding a checkbox to the advanced settings for an external line that would enable instrument-identification, but the default must be "no". > 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? In regard to softphones, if we don't generate the modified auth user name, the phone is not addressable via the special URIs. Although I don't know if we generate config files for softphones in practice. Dale _______________________________________________ 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/
