6 Nov
2016
6 Nov
'16
11:09 a.m.
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(a)gmail.com>
wrote:
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(a)sip.parzee.io <gonzalo(a)sip.parzee.io>* to
*gonzalo58(a)test.external.com
<gonzalo58(a)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(a)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"))
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 <https://messinet.com/~amessina/galleryF9B6> 560E 68EA 037D 8C3D
D1C9 FF31 3BDB D9D8 99B6
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users