I had the same problem when calling mediaproxy twice by mistake.
rtpproxy_manage( ) calls implicitely rtpproxy_offer( ). This is the problem.
Either you use only rtpproxy_manage once on the INVITE and let it start and
terminate the session, or you use rtpproxy_offer, rtpproxy_answer and
rtpproxy_
I call rtpproxy_offer() once, but i use also rtpproxy_manage().
When i disable rttproxy_mange(), it works well.
Thanks!
On Wed, May 9, 2012 at 2:57 PM, Andreas Granig wrote:
> Hi,
>
> On 05/09/2012 02:40 PM, Openser Kamailio wrote:
> > *Owner/Connection Information (o)*: doubango 1983 678901 IN
Hi,
On 05/09/2012 02:40 PM, Openser Kamailio wrote:
> *Owner/Connection Information (o)*: doubango 1983 678901 IN IP4
> *172.27.170.984* 172.27.170.98
> *Connection Information (c)*: IN IP4 *172.27.170.984* 172.27.170.98
Could it be possible that you're calling rtpproxy_offer() twice?
Andreas
Hi,
i'm currently working with kamailio 3.2 and rtpproxy 1.2.1. Both are set up
on the same computer.
When rtpproxy adds an SDP to an Invite, it adds two IPv4 addresses in
owner/creator session and connection information field with an error, i.e:
*Owner/Connection Information (o)*: doubango 1983
