Hello Daniel,

my understanding is that l_uuid and l_domain are used to construct the Contact: 
header in outgoing REGISTER, and thus RURI and To: for incoming
INVITE.

Is my reading correct, that after an INVITE arrives for sip:l_uuid@l_domain, 
the UAC REG functions (which ones?) are used to substitute
l_uuid@l_domain to l_usernname?

Greetings
  Дилян

-----Original Message-----
From: Daniel-Constantin Mierla <[email protected]>
Reply-To: [email protected]
To: Kamailio (SER) - Users Mailing List <[email protected]>, Дилян 
Палаузов <[email protected]>
Subject: Re: [SR-Users] What does l_username in UAC do?
Date: 02/23/2023 11:23:28 AM

Hello,

the prefix l_ is used for "local" specific attributes, which refer more
or less to local subscriber, while r_ is for remote service (where the
register is sent).

If the local server is a.com and you have [email protected], that is the
l_username@l_domain. If you want to map it to a remote subscriber
[email protected], then those are r_username@r_domain

The l_uuid is needed because not all deployments are single domain, and
thus the l_username alone is not unique (think about multi-tenant pbx,
with many 101s, like [email protected], [email protected], ... The l_uuid must be unique
over all the susbscribers, being used in places where
l_username@l_domain cannot be used.

Second, there are cases when you do not want to disclose the "real"
local user identity to the remote server, so even it is single domain
and l_username would be unique, with l_uuid you can set a random id,
with no "easy-to-relate" rule to l_username.

If l_username is unique and you are fine with setting l_uuid to the same
value, then it should be no problem. But having only one field instead
of the two limits the functionality and makes it not suitable for some
use cases.

Cheers,
Daniel

On 17.02.23 12:34, Дилян Палаузов wrote:
> Hello,
> 
> the uac module-registrations have the fields
> 
> l_uuid - user for Contact: in REGISTER (before @).  Described at 
> https://kamailio.org/docs/db-tables/kamailio-db-5.6.x.html#idm9037 as “Local 
> unique
> id used to build and match contact addresses.”.  Described at 
> https://www.kamailio.org/docs/modules/devel/modules/uac#idm700 as “local 
> unique user
> id,
> e.g.,: 12345678”
> 
> l_username - Described at 
> https://kamailio.org/docs/db-tables/kamailio-db-5.6.x.html#idm9037 as “Local 
> username”.  Described at
> https://www.kamailio.org/docs/modules/devel/modules/uac#idm700 as “local user 
> name, e.g.,: test ”.  For me there is no difference between “local
> unique id” (as for l_uuid) and “local username“ (here).
> 
> l_domain - used for Contact: in REGISTER (after @), described at 
> https://kamailio.org/docs/db-tables/kamailio-db-5.6.x.html#idm9037 as “local
> domain”
> 
> 
> When is l_username used, what is it purpose?  Does it solely serve as 
> possible filter criterion for the RPC commands:
> 
> uac.reg_info l_username abc
> uac.reg_enable l_username abc
> uac.reg_disable l_username abc, and
> uac.reg_unregister l_username abc
> 
> 
> 
> Do I see correctly, that via UAC-RPC an unREGISTER can be triggered, but 
> there is no way to trigger a REGISTER over UAC-RPC?
> 
> Thanks for the clarifications
>   Дилян
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to [email protected]
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:


__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

Reply via email to