[asterisk-bugs] [Asterisk 0014711]: directrpsetup=yes does not work when canreinvite=n
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Sep 3 14:39:52 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=14711
======================================================================
Reported By: rrb3942
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14711
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.6.0.6
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-03-20 09:47 CDT
Last Modified: 2009-09-03 14:39 CDT
======================================================================
Summary: directrpsetup=yes does not work when canreinvite=n
Description:
If directrtpsetup is set to to 'yes' and canreinvite is set to 'no'
Asterisk will not perform native bridging on the channels during the call
setup.
If directrtpsetup is set to 'yes' and canreinvite is set to 'yes' Asterisk
will perform native bridging on the channels during the call setup.
I did not see any note in the documentation that directrtpsetup requires
the peer to also support canreinvite=yes.
I am not sure if this is intended behavior because without being able to
RE-INVITE Asterisk would not be able to re-insert itself into the media
path for possible features later in the dialplan.
======================================================================
----------------------------------------------------------------------
(0110173) oej (manager) - 2009-09-03 14:39
https://issues.asterisk.org/view.php?id=14711#c110173
----------------------------------------------------------------------
1) Directrtpsetup is marked experimental and not officially supported
2) canreinvite=n is really overriding directrtpsetup and should, since you
by setting this disable all remote bridges. We've renamed canreinvite to
"directmedia" to give it a better name that is easier to understand.
So I don't consider the fact that directrtpsetup=y and canreinvite=n means
that there will be no directrtpsetup. It's correct behaviour.
And yes, if you're using directrtpsetup a lot of strange stuff may happen.
There's a reason why it's still considered experimental after many releases
- it's very hard to fix it properly and will require a large rewrite of our
media negotiation and handling structure.
Issue History
Date Modified Username Field Change
======================================================================
2009-09-03 14:39 oej Note Added: 0110173
======================================================================
More information about the asterisk-bugs
mailing list