[asterisk-dev] Flag to disable Packet2packet bridging

[Richard Brady]

2009/8/13 Joshua Colp <jcolp at digium.com>
>
> ----- "Richard Brady" <rnbrady at gmail.com> wrote:
>
> > Hi folks
> >
> > I am looking for a way to turn off Packet2packet bridging. I found the
> > following bug report:
> >
> > 0010943: [PATCH] Flag to disable Packet2packet bridging
> >
> > which states:
> >
> > "This patch adds a disablep2p flag to rtp.conf. It will force all
> > bridges to be native."
> >
> > The reporter (julianjm) attaches two patches to do just that. But the
> > corresponding svn revision makes a completely different change, and
> > does not introduce such a flag at all.
> >
> > I want to ask what happened, but the issue is closed so it doesn't
> > seem possible to comment.
>
> The underlying issue was that the code did not already do a generic bridge when it should have.

Agreed.

>
> > Can I submit a new issue for this?
>
> Why do you want to have a way to turn off Packet2Packet bridging? Is something going wrong that you think will be solved
> by doing so?

I am interested in the ability of Asterisk to "normalise" RTP to some
extent. It's smarter than a lot of other implementations out there
with respect to things like payload types, sequence numbers or
timestamps. So if an Asterisk box is between a bad implementation of
RTP and another bad (or just strict) implementation of RTP, it might
be able to help.

An example would be by converting an RFC2833 payload type from 98 to
101, which helps to overcome some compatibility issues (which
admittedly shouldn't exit, but do). I suppose this is analogous to how
Asterisk works with SIP, i.e. as a B2BUA.

I was hoping to fool around with this and came across the bug which I
found ambiguous. I suppose if I am going to motivate for the
introduction of such a flag I should do so one a more appropriate
mailing list.

Thanks very much for the response.

Richard