Hello,
is there a select to get the canonical username? or is 'canonical username' now a deprecated concept?
I know there is the uid, but the problem is, with 36 characters uid is too long for my purpose (user id for voicebox).
thanks Stefan
Hi Stefan,
Stefan Sayer schrieb:
Hello,
is there a select to get the canonical username? or is 'canonical username' now a deprecated concept?
the canonical username is still marked with a bit in the DB, but I fear there is no "select" statement which allows you easily to access this username from the config script (that's how I interpret your request).
Cheers Nils
I know there is the uid, but the problem is, with 36 characters uid is too long for my purpose (user id for voicebox).
thanks Stefan
Stefan Sayer wrote:
is there a select to get the canonical username? or is 'canonical username' now a deprecated concept?
I know there is the uid, but the problem is, with 36 characters uid is too long for my purpose (user id for voicebox).
Aren't you free to use whatever you like as a uid? Depending on context, I would probably use the customer ID or the canonical phone number for it.
If in doubt, you can always define an attribute that stores whatever ID you want for your voicebox.
Regards, Martin, who doesn't really like the idea that attributes need to be defined in some table somewhere for the serctl tools to add them. But one can, of course, always write directly to the database.
Hi Martin,
Martin Hoffmann wrote:
Stefan Sayer wrote:
is there a select to get the canonical username? or is 'canonical username' now a deprecated concept?
I know there is the uid, but the problem is, with 36 characters uid is too long for my purpose (user id for voicebox).
Aren't you free to use whatever you like as a uid? Depending on context,
yes, I am. only that the uid is 32 characters long, and I would have liked to keep it shorter to avoid fragmentation with udp as transport.
I would probably use the customer ID or the canonical phone number for it.
if the canonical username can change, the customer ID (uid) would be the natural thing to use, of course.
If in doubt, you can always define an attribute that stores whatever ID you want for your voicebox.
but that doesn't seem necessary.
Stefan
Regards, Martin, who doesn't really like the idea that attributes need to be defined in some table somewhere for the serctl tools to add them. But one can, of course, always write directly to the database.
-
Martin Hoffmann -
Nils Ohlmeier -
Stefan Sayer