Re: KamailioProxy: Should kamailio do handshake or asterisk?

Yuriy G via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <CABSP_Vfz9KR2L=84N4gXu6b332vwXkpZqFOM1zky8FPwSZo14Q@mail.gmail.com>
You handle TLS on kamailio in anyways by receiving it on TLS port. Kamailio
will decrypt the message. If your B2BUA is reachable via a trusted network:
there is no need to create yet another TLS connection between kamailio and
B2BUA

On Tue, Jul 1, 2025, 17:02 Alex Balashov via sr-users <
[email protected]> wrote:

> Kamailio can handle the TLS handshake.
>
> > On Jul 1, 2025, at 10:09 AM, Fernando Lopes via sr-users <
> [email protected]> wrote:
> >
> > Hello everyone,
> > I have Kamailio set up as a proxy between external clients and an
> Asterisk server. When traffic comes in over WSS, should Kamailio handle the
> TLS handshake, or should it be passed through to Asterisk?
> >
> > Thank you.
> > __________________________________________________________
> > Kamailio - Users Mailing List - Non Commercial Discussions --
> [email protected]
> > To unsubscribe send an email to [email protected]
> > Important: keep the mailing list in the recipients, do not reply only to
> the sender!
>
> --
> Alex Balashov
> Principal Consultant
> Evariste Systems LLC
> Web: https://evaristesys.com, https://www.csrpswitch.com
> Tel: +1-706-510-6800
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions --
> [email protected]
> To unsubscribe send an email to [email protected]
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
>

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.