Thanks!
That is working well.
Spencer
On Feb 7, 2012, at 6:18 PM, Alex Balashov wrote:
> On 02/07/2012 08:59 PM, Spencer Thomason wrote:
>
>> Can I replace the To: username and then call save():
>
> No, but check this out:
>
> http://www.kamailio.org/docs/modules/3.2.x/modules_k/registrar.ht
On 02/07/2012 08:59 PM, Spencer Thomason wrote:
Can I replace the To: username and then call save():
No, but check this out:
http://www.kamailio.org/docs/modules/3.2.x/modules_k/registrar.html#id2540034
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atla
Can I replace the To: username and then call save():
On Feb 7, 2012, at 5:56 PM, Alex Balashov wrote:
> Spencer,
>
> With registrations, it is the To URI, not the From URI, that determines the
> AOR stored. The From URI is only used as the asserted identity for requests
> like INVITE.
>
> N
Spencer,
With registrations, it is the To URI, not the From URI, that determines the AOR
stored. The From URI is only used as the asserted identity for requests like
INVITE.
Not sure if that helps.
--
This message was painstakingly thumbed out on my mobile, so apologies for
brevity and error
I'm sorry I meant contact URI not From.
On Feb 7, 2012, at 5:48 PM, Spencer Thomason wrote:
> Hello,
> I have clients which register to Kamailio using an auth username. The from
> username is used for caller id on an INVITE. This causes a problem if the
> client does not use the auth username
Hello,
I have clients which register to Kamailio using an auth username. The from
username is used for caller id on an INVITE. This causes a problem if the
client does not use the auth username in the from for the REGISTER. The caller
id number is then saved as the AOR username which doesn't
