You are right.
I just escalated the scenario to de...@rtpproxy.org
Thank you.
On 11 February 2011 19:15, Ovidiu Sas <o...@voipembedded.com> wrote:
> Please report your crash on the rtpproxy list and provide a way to
> reproduce it.
> Rtpproxy should not crash that easy.
>
> Regards,
> Ovidiu Sas
>
> On Fri, Feb 11, 2011 at 12:04 PM, Kamen Petrov <kamen.pet...@gmail.com>
> wrote:
> > Hi Anca,
> >
> > Ok, I managed it work your way.
> >
> > The key was not in the rtpproxy_answer but the rtpproxy_offer :)
> >
> > Once again thanks to you and Ovidiu for your great help !
> >
> > So just for the record if someone else face the same issue: segfault in
> the
> > rtpproxy on the onreply_route: don't look only the rtpproxy_answer but
> also
> > play with the rtpproxy_offer
> >
> >
> >
> >
> >
> > On 11 February 2011 18:30, Anca Vamanu <a...@opensips.org> wrote:
> >>
> >> On 02/11/2011 03:31 PM, Kamen Petrov wrote:
> >>
> >> onreply_route[1] {
> >> if (!(status=~"183" || status=~"200")) {
> >> drop;
> >> }
> >>
> >> rtpproxy_answer("FA");
> >>
> >> Maybe you could try to use other flags, or renounce at one at a time to
> >> see which one results in segmentation fault. You should also report this
> to
> >> the rtpproxy list.
> >>
> >> --
> >> Anca Vamanu
> >> OpenSIPS Developer
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users@lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >>
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
>
> _______________________________________________
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
