4 Nov
2016
4 Nov
'16
9:58 a.m.
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
4 Nov
4 Nov
10:05 a.m.
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 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 <mailto:sip%3Agonzalo@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
<mailto:sip%3Agonzalo58@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 <http://test.external.com>;transport=tls
*username*: gonzalo
*domain*: sip.parzee.io <http://sip.parzee.io>
Thanks
-Gonzalo
_______________________________________________
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
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
11:38 a.m.
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(a)gmail.com>
wrote:
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
_______________________________________________
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
--
Alberto Llamas
Phone: +1-786-805-6003
Telecommunications Engineer
Digium Certified Asterisk Professional (dCap)
5 Nov
5 Nov
2:01 p.m.
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 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6
6 p.m.
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* 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 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
6 Nov
6 Nov
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
2755
days inactive
2757
days old
5 comments
4 participants
participants (4)
-
Alberto Llamas -
Anthony Joseph Messina -
Daniel-Constantin Mierla -
Gonzalo Gasca Meza