I'm using set_contact_alias() to fix nat registrations, in this case with a
Bria client.
Somehow Bria learns that I'm using this - probably through the Contact in the
200 OK reply of save(). Bria then adds this to the Contact when replying to
incoming INVITE.
After some time, something happens
Thank you for your reply.
Does the manual somewhere state that set_contact_alias() should not be used for
REGISTER?
Actually, some examples suggest using this instead of fix_nated_contact() -
http://www.evaristesys.com/blog/server-side-nat-traversal-with-kamailio-the-definitive-guide/
The reas
All done on edge proxy. I'm not a regex-pro.
It will not work if done locally on the registrar (the node doing the save()).
https://gist.github.com/mtryfoss/9a0811dbc4462b91afe87d7dd5a210e8
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
handle_ruri_alias() only handle alias in Request-URI, not the Contact returned
by the registrar for REGISTER.
For most phone clients this is not a problem but Bria used that info in
subsequent requests.
So, when the proxy again doing set_contact_alias() on an INVITE from Bria
(already containin
I've only been testing 5.3.3. Of course, the alias should probably be replaced
if it exists rather than append one more without the need for a specific
setting/parameter.
I'm not that into Kamailio source and did not have time to get going there when
I found the issue, so I fixed it quickly by
Thanks!
I've lost my staging environment temporarily because of some physical
re-location of our servers.
I will try to test it when I'm returning from vacation.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://gith
- using LM_INFO cause a lot of log events on a busy server with normal log level