THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Magnus Nordström (mnnojd) Attached to Project - sip-router Summary - Some cases when rtp proxy not change port numbers in media Task Type - Bug Report Category - Core Status - Assigned Assigned To - Andrei Pelinescu-Onciul Operating System - Linux Severity - Low Priority - Normal Reported Version - 3.0 Due in Version - Undecided Due Date - Undecided Details - We use the rtp proxy and we have seen problems in some cases when rtp proxy should change port numbers for the media. We have a sip-client which also send position information included in the INVITE. The problem seems to be that the rtp proxy cannot handle the INVITE when the header in parameter "boundary=" has the value between "". And it cannot handle if the body has the parameter "Content-Length:". It results with that the ports will not be changed. May there is some modules which can solve this problem? Here I give three cases with INVITE packets which one is handled fine by rtp proxy. ***** Case 1 - Handles fine by rtp proxy and changes port numbers ***** INVITE ... .... Geolocation: <cid:123@sip.domain.com> Geolocation-Routing: yes Content-Type: multipart/mixed;boundary=MessageBoundary --MessageBoundary Content-Type: application/sdp .... --MessageBoundary Content-Type: application/pidf+xml Content-ID: &lt;123(a)sip.domain.com&gt; .... --MessageBoundary-- ***** Case 2 - rtp proxy dont change the port numbers (problems with "" in boundary value?) ***** INVITE ... .... Geolocation: <cid:123@sip.domain.com> Geolocation-Routing: yes Content-Type: multipart/mixed;boundary="----=_Part_46_780035120.1327568255734" ------=_Part_46_780035120.1327568255734 Content-Type: application/sdp .... ------=_Part_46_780035120.1327568255734 Content-Type: application/pidf+xml Content-ID: &lt;123(a)sip.domain.com&gt; .... ------=_Part_46_780035120.1327568255734-- ***** Case 3 - rtp proxy dont change the port numbers (problems with Content-Length in body?) ***** INVITE ... .... Geolocation: <cid:123@sip.domain.com> Geolocation-Routing: yes Content-Type: multipart/mixed;boundary=MessageBoundary --MessageBoundary Content-Type: application/sdp Content-Length: 454 .... --MessageBoundary Content-Type: application/pidf+xml Content-ID: &lt;123(a)sip.domain.com&gt; Content-Length: 553 .... --MessageBoundary-- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=200 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.