I assume that the registrar is rewriting the request URI of the request to the
SIPS scheme. The behaviour of the registrar by adding a SIPS also to its
Record-Route header is then according to the standard:
```
The URI placed in the Record-Route header field MUST resolve to
the element inserting it (or a suitable stand-in) when the
server location procedures of [4] are applied to it, so that
subsequent requests reach the same SIP element. If the
Request-URI contains a SIPS URI, or the topmost Route header
field value (after the post processing of bullet 6) contains a
SIPS URI, the URI placed into the Record-Route header field
MUST be a SIPS URI.
```
You could set the rr parameter "ignore_sips" on the registrar, if you want them
to only insert the SIP scheme.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4092#issuecomment-2567974843
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4092/2567974...@github.com>_______________________________________________
Kamailio - Development Mailing List -- sr-dev@lists.kamailio.org
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
