Hi Kamailions,
Kamailio 4.3 will receive calls (SIP TLS) for users in this domain: *sip.parzee.io http://sip.parzee.io. *Example
sip:gonzalo@sip.parzee.io
When call is received by Kamailio I need to overwrite R-URI and transport. I should keep a mapping per user. ( gonzalo -> gonzalo58)
Example.
sip:gonzalo58@test.external.com;transport=tls
I started looking into *dbaliases* table in LOCATION.
#!ifdef WITH_ALIASDB # search in DB-based aliases if(alias_db_lookup("dbaliases")) route(SIPOUT); #!endif
In dbaliases table I see 4 columns. Is the following configuration correct?
*alias_username*: gonzalo58 *alias_domain*: test.external.com;transport=tls *username*: gonzalo *domain*: sip.parzee.io
Thanks
-Gonzalo
Hello,
it's not very clear for me what you try to achieve. Do you get the call via TLS and want to forward to another server via a different hostname also using TLS?
In alias_db module, the alias record is matching in coming r-uri and it is translated to user record.
Cheers, Daniel
On 04/11/16 09:58, Gonzalo Gasca Meza wrote:
Hi Gonzalo,
I think you are doing wrong setting 'transport=tls' in the alias_domain. You should implement a combination of aliasdb and checking for protocol as below:
*alias_username*: gonzalo58 *alias_domain*: test.external.com *username*: gonzalo *domain*: sip.parzee.io
In kamailio's script (example):
#!ifdef WITH_ALIASDB # search in DB-based aliases if(proto==TLS) { if(alias_db_lookup("dbaliases")) { route(SIPOUT); } } #!endif
Regards,
On Fri, Nov 4, 2016 at 9:58 AM, Gonzalo Gasca Meza gascagonzalo@gmail.com wrote:
On Friday, November 4, 2016 1:58:48 AM CDT Gonzalo Gasca Meza wrote:
Adding the transport in the domain column as you have has worked for me in the past, though I'm not sure it's supposed to. -A
Thanks for replying,
What I want to achieve is once I receive the SIP INVITE, I need to translate it to a different SIP URI, this new SIP request needs to be initiated using different URI and TLS. Example:
INVITE -> sip:gonzalo@sip.parzee.io -- TLS/TCP/UDP -> *KAMAILIO* - DB Lookup -> INVITE sip:gonzalo58@test.external.com;transport=tls -> INVITE TLS - ...
I need to convert *gonzalo@sip.parzee.io gonzalo@sip.parzee.io* to *gonzalo58@test.external.com* and guarantee this new request now is sent in TLS. My logic was to use *alias_db_lookup* to handle the conversion as well as adding the Transport in order to have Kamailio force the new SIP request in TLS. Is this the right way?
Thank you
-Gonzalo
On Sat, Nov 5, 2016 at 6:01 AM, Anthony Joseph Messina < amessina@messinet.com> wrote:
It worked perfectly with alias_db_lookup and add transport in domain field.
Thanks
On Sat, Nov 5, 2016 at 10:00 AM, Gonzalo Gasca Meza gascagonzalo@gmail.com wrote:
-
Alberto Llamas -
Anthony Joseph Messina -
Daniel-Constantin Mierla -
Gonzalo Gasca Meza