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
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 reques
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:
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("dbalias
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
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
