Hello,
I am converting a Kamailio WSS/TLS gateway to pure TCP, with an external HAProxy handling TLS termination and emitting the proxied connection as plain TCP. I am using the PROXYv2 protocol, with `tcp_accept_haproxy=yes`, to convey the upstream network and transport-layer reachability info into Kamailio.
I am trying to figure out best practices for mapping the contacts on those connections to the proxied connections themselves.
For registrations, tcp_force_alias() (with `tcp_accept_aliases=yes`) works well, and inbound calls go to the right place. However, I'm not quite sure what to do with other flows, such as, for example, in-dialog requests on inbound calls going to the TLS endpoints.
There are obviously a lot of possibilities, all or most of which I've tinkered with. These generally involve either {s.replace}-ing `;transport=tls` with `;transport=tcp` in the contacts received from the client, or using the traditional `nathelper` contact alias / RURI alias bag of tricks. However, I don't like the former solution because it leads to a non-compliant R-URI going to the endpoint (it's not the ;transport it sent in its contact), and I don't like the latter because it seems like there are too many moving parts.
When tcp_force_alias() works so well for registrations, there must be some small linchpin I'm missing for normal request-reply flows. What is it?
Thanks in advance!
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
Hello,
I am trying to configure the Topos module and have some questions.
# topos:msg-outgoing vs topos:msg-sending
https://www.kamailio.org/docs/modules/5.8.x/modules/topos.html#topos.e.msg_…
I am trying to understand the difference between these two event
routes(beyond the content of the SIP message ). I notice that both are
invoked when OPTIONS are generated by the local Kamailio server but only
msg-sending is invoked for messages transiting the Kamailio( ie proxied,
not locally generated).
Is there some difference in how these event_routers are invoked beyond the
content of the SIP message?
# tops -> requests/replies
When I am in event_route[topos:msg-sending] { and invoke 'drop', does this
apply to the current message or does it apply to the transaction?
I have a Kamailio node with devices on either side. Let's call side A
untrusted and side B trusted.
I want TOPOS happening against the untrusted device but not the trusted
device.
I have found that when I invoke 'drop' on a request coming from A to B, it
disables TOPOS not only on that packet, but also the reply comes from B
back to A, TOPOS isn't applied when the reply exits Kamailio towards A. So
if I call 'drop' on the request coming from A to B, the reply coming from B
to A has no TOPOS applied.
How do I get TOPOS applied to all traffic facing a particular device while
leaving that traffic un-stripped when the same traffic is interacting with
other devices that are trusted?
Thanks,
David
The sex doll torso is a very light mini sex doll. Usually, its weight is 4kg to 20kg. These sex doll torsos are made of TPE or silicone. Of course, they are all very safe materials.
https://www.sextorso.com/
Hello list,
is it possible create a user using sha-256 hash?
My goal is Asterisk PBX Register ----- sha-256 digest authentication ->
Kamailio
Regards
--
---
I'm SoCIaL, MayBe