### Description
In my config used `msrp` and `tls` modules. When MSRP client is connected using TCP socket (not TLS), then `$msrp(srcaddr)` always returns "msrps" URL. When used TCP socket, then must be returned "msrp" URL. And no matter TLS module is loaded or not.
[Relevant code](https://github.com/kamailio/kamailio/blob/d737c876cc36b4de802da77dfcd361323a...)
I think the this version is more correct [Link](https://github.com/kamailio/kamailio/blame/30c8ead0b18678950b7596d4247d51cb5...)
Probable need revert commits 32951506dff11df32c03230c1548553838140574 116daef9b55d82a016d1fd3e3d877a2468c55d1a
According to 116daef9b55d82a016d1fd3e3d877a2468c55d1a commit description
modules/msrp: Use "msrps://" URIs for the server when TLS is
loaded. TLS is mandatory for MSRP relays.
According [rfc4976#section-9.2](https://datatracker.ietf.org/doc/html/rfc4976#section-9.2)
9.2. Using TLS
TLS is used to authenticate relays to senders and to provide integrity and confidentiality for the headers being transported. MSRP clients and relays MUST implement TLS.
Yes, according to RTF proxy must support TLS, but this does not dictate the TLS usage on the client side. I think the client a free to use TCP only. I will check RFC restrictions for the client.
Closed #2881.
yes, looks as TLS always must be used on the proxy side. Closing ticket.
-
sergey-safarov