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:gonz...@sip.parzee.io -- TLS/TCP/UDP -> *KAMAILIO* - DB Lookup -> INVITE sip:gonzal...@test.external.com;transport=tls -> INVITE TLS - ... I need to convert *gonz...@sip.parzee.io <gonz...@sip.parzee.io>* to *gonzal...@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 < amess...@messinet.com> wrote: > On Friday, November 4, 2016 1:58:48 AM CDT Gonzalo Gasca Meza wrote: > > Example. > > > > sip:gonzal...@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 > > 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 > > -- > Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery > F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6 > > _______________________________________________ > 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-users > >
_______________________________________________ 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-users