Hi Bogdan and thanks for the answer. I was under the assumption that this logic was "hardcoded", but now i understand i need to setup the rules to enforce this.
Best Regards Wilhelm On Mon, 4 Feb 2019 at 08:58, Bogdan-Andrei Iancu <bog...@opensips.org> wrote: > Hi Wilhelm, > > Keep in mind that OPenSIPS is a routing engine that does what you tell it > to do. > > The OpenSIPS does the translation from TLS to UDP as the callee device is > registered via UDP. > > Now, how to handle a sips enforcement in the RURI is up to the logic in > the proxy - if allows it to switch to a non-secure protocol or if applies > constraints to stay with a secure protocol - but if you want this, you need > to script it in your opensips.cfg. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 01/16/2019 06:03 PM, Wilhelm Lundgren wrote: > > Hi, > > Im trying out some tls / sips things in my client. But im seeing something > strange in opensips. > I am using opensips 2.2.2, x64. > > Im registering my client with TLS and SIPS. Another client is registering > over UDP. I expected that when i send a SIP MESSAGE with sips: in request > and to / from tags etc, the UDP client should not receive the message. > However, opensips downgrades this message to normal sip and sends it. > > Have i missunderstood "sips:" feature or have i configed something wrong > or is it not supported? > > Best Regards > Wilhelm > > > > _______________________________________________ > Users mailing > listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users