[sr-dev] [tracker] Task opened: Added Record Route Header incorrect when Request-URI contains a SIPS URI

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Hugh James (hugh.james) Attached to Project - sip-router Summary - Added Record Route Header incorrect when Request-URI contains a SIPS URI Task Type - Bug Report Category - Module Status - Unconfirmed Assigned To - Operating System - Linux Severity - High Priority - Normal Reported Version - 3.1 Due in Version - Undecided Due Date - Undecided Details - The record-route header added by Kamailio to a SIPS (TLS) call using the record_route(); operation is incorrectly generated by Kamailio. Page 101 (second sentence) of RFC3261 states "If the Request-URI contains a SIPS URI [...] the URI placed into the Record-Route header field MUST be a SIPS URI." Kamailio incorrectly generates record-route headers with the sip: URI scheme. All other fields are correctly generated with the sips: URI scheme. In response to this deviation from RFC3261, a Cisco ISR rejects the call with code 403. Module rr source code in release 3.3.3 checked and problem is caused by #define RR_PREFIX "Record-Route: <sip:" in record.c possible solution is check the Request URI for SIPS URI , and use #define RR_PREFIX_SIPS "Record-Route: <sips:" instead. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=277 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.