FS doesn't save registration to db in case of TLS + unusual param order in sip contact header

FreeSWITCH
1

Hello. I noted that FS doesn’t save registration to db in case contact header looks like this:

Contact: sip:username@ip:51739;rinstance=08f9f2fed28d968c;transport=tls

and everything is fine in case:

Contact: sip:username@ip:59149;transport=TLS;rinstance=d6be1964cd7342d8

At first I thought that was the problem related with uppercase or lowercase (TLS or tls) but it is not the case. The problem related with order.
If ;transport= comes immediately after the port number - everything is fine.

Please advice.

2

What version of FreeSWITCH is this? Does it only happen with TLS or are you seeing the same thing with other transports?

3

It is not FS issue. This happens because of the weird TLS registration logic in Zoiper Pro. It does unregistration after 1st registration and send second attempt (wih TLS instead of tls) in the contact header. Mid-registrar caches second attempt and therefore registration does not appear in the database.