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_destroy and if finer control is needed.
Best is to call rtpproxy_manage and let it do its magic unless you have specific reason to "manually" control the session, such as terminating the rtpproxy session when transferring the call to a pstn gateway that handles rtp for example.
You can find more details in the rttpproxy module documentation.
Reda
On Wed, May 9, 2012 at 4:16 PM, Openser Kamailio kamailioopenser@gmail.comwrote:
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 agranig@sipwise.comwrote:
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
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users