[OpenSIPS-Users] siprec with rtpproxy

[Răzvan Crainea]

Hi, Martin!

You are right, the c= element is missing in the SDP. And according to 
the RFC[1], the body should have at least one c= element. Regarding the 
o= line, the IP over there is not that important, and it can be 
anything, provided that the entire o= line is unique.

Now the main problem came from the fact that RTPProxy does not advertise 
the IP it will be sending RTP from, so we don't really know what to have 
in the c= line. The only way I am thinking we can solve this is to 
provide the RTP IP as a parameter to the siprec_start_recording() 
command[2]. In case this is missing, we add something dummy, such as the 
first interface of OpenSIPS or something.

Note that the same issue is with the port advertised in SDP: since 
rtpproxy does not indicate which port it will be using for streaming the 
media, those ports are completely dummy.

[1] https://tools.ietf.org/html/rfc4566#section-5.7
[2] 
http://www.opensips.org/html/docs/modules/2.4.x/siprec.html#siprec_start_recording

PS: in the future, please attach file contents on an external storage.

Best regards,

Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com

On 01/23/2018 10:15 AM, Martin Nyström wrote:
>
> Hi,
>
> I am having issues with siprec and rtpproxy.
>
> Running the latest 2.4 dev version.
>
> The issue I am having is that when an 200 OK is received, the siprec 
> is sending an incorrect SDP block to the recording provider. As a 
> result of this they are unable to process the recording properly.
>
> For an example the SDP element c= is missing completely and the o= 
> element are sending the incorrect IP. I am thinking there is some 
> issue between rtpproxy and opensips that causes this.
>
> I have attached below some relevant configurations, please note that 
> “my.externalip.com” is a pseudo for my external IP. The server only 
> has an interface with an external address.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180123/db89689b/attachment.html>