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 to gonzalo58@test.external.comand 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-GonzaloOn Sat, Nov 5, 2016 at 6:01 AM, Anthony Joseph Messina <amessina@messinet.com> wrote:______________________________On Friday, November 4, 2016 1:58:48 AM CDT Gonzalo Gasca Meza wrote:
> 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")) Adding the transport in the domain column as you have has worked for me in the
> 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
past, though I'm not sure it's supposed to. -A
--
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6
F9B6
_________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-user s