[OpenSIPS-Users] TLS traffic is being relayed as UDP but on the TLS Port?

David Villasmil david.villasmil.work at gmail.com
Wed Apr 24 18:36:01 EDT 2019


You can still switch to udp, but you have to rewrite the ruri. Do you want
to relay in tls as well?

On Wed, 24 Apr 2019 at 22:19, Liviu Chircu <liviu at opensips.org> wrote:

> And the PBX never processes the registration request (it's being
>> communicated via the wrong protocol on the wrong port so it's ignoring it
>> which it should)
>>
>> How can mid_registrar return code '2' if there is no response from the
>> PBX?
>>
> Correct - '2' means you should STOP processing this REGISTER.  On a '1'
> code, you should relay it.
> On 25.03.2019 17:57, John Kiniston wrote:
>
> I'm still fighting with this and would love some assistance.
>
> Is there more data I should be collecting? do I need to post more
> configuration details?
>
> Johan gave an excellent hint earlier on, did you try it?  You should
> modify your R-URI so you switch to TLS.  A nomadic (but 99% healthy) way to
> do this would be:
>
> $ru = $ru + ";transport=TLS";
>
> --
> Liviu Chircu
> OpenSIPS Developerhttp://www.opensips-solutions.com
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 
Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190424/b1499143/attachment.html>


More information about the Users mailing list