On Thu, 2009-10-29 at 12:54 -0400, Damian Krzeminski wrote: > Dale Worley wrote: > > On Thu, 2009-10-29 at 12:26 -0400, Damian Krzeminski wrote: > >> We do (Bria A.K.A. Counterpath). The only thing I am trying to say is that > >> serial number for Bria *is* your user ID. So it does not make any sense to > >> generate 'authentication user name' in the form of 'userid/userid'. > > > > Eh? If there isn't a slash in the auth user name, the Registrar code > > won't recognize it has *having* a serial number. > > > > Let me try to explain what I meant: Let's say we have a user "juser". Admin > adds a Bria phone for 'juser' soft phone. The soft phone serial number will > have to be 'juser'. > > Why should sipXconfig configure the line for 'juser/juser' instead of > configuring the line for 'juser'? > > sipXecs doesn't gain any additional way of identifying anything if we do > that. What am I missing here? > > BTW: I assume that registrations for 'normal' format usernames still work, > right? (They'll have to work for un-managed devices).
Let me answer the last question first, as that might clarify things: If the auth user name does not contain a slash, then it is (of course) the real auth user name, and the phone has an identity of (empty string), which is not considered an identity and cannot be addressed using a ~~in~ URI. This is the default condition for phones not using the mechanism. If the auth user name is "[real name]/", then the effect is the same. If the auth user name is "[real name]/[real name]", then the phone is addressable via "sip:~~in~[real na...@..." and "sip:~~in~[real name]/[real na...@...". This allows the softphone to be addressed separately from any phone that presents a different identity. (E.g., a hardphone that registers for the same user, whose identity is its MAC address.) 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/
