Thanks, Seemed to work that time, many thanks.
Regards Chris -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ovidiu Sas Sent: 12 May 2011 17:14 To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] force rtpproxy not to wait for rtp beforesending Have you tried the 'r' flag: http://www.opensips.org/html/docs/modules/devel/rtpproxy.html#id292737 It should force sending RTP to the IP/port advertised in SDP. Regards, Ovidiu Sas On Thu, May 12, 2011 at 12:07 PM, Chris Martineau <[email protected]> wrote: > Hi, > > > > I have some scenarios where certain gateways are not sending any rtp until a > 200ok message is received. > > I have rtpproxy running to overcome nat issues from customers and to provide > comfort announcements, however calls from some of my main traffic gateways > which are trusted and not nat'ed do not send rtp on receiving a 183, so > rtpproxy does not switch on sending rtp causing my comfort announcement and > subsequent early media ringing to fail. > > Is there anyway to force rtpproxy to trust a connection and not wait for rtp > before sending? > > I notice that there are some flags that indicate that they will do this but > when I invoke them the behaviour doesn't change? > > I know that the main purpose of rtpproxy is to confirm the rtp source before > sending but as I also use it for announcements it useful to have it > permanently in situ. > > > > Any help would be greatly appreciated. > > > > Thanks > > > > Chris > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
