[asterisk-bugs] [Asterisk 0014711]: directrpsetup=yes does not work when canreinvite=n
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Jul 26 06:03:50 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=14711
======================================================================
Reported By: rrb3942
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 14711
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
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-07-26 06:03 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.
======================================================================
----------------------------------------------------------------------
(0108230) hzshlomi (reporter) - 2009-07-26 06:03
https://issues.asterisk.org/view.php?id=14711#c108230
----------------------------------------------------------------------
This is not the complete story with "directrtpsetup":
the disconnect handling is wrong: when asterisk receives the BYE, it
initiates a re-invite (connecting media back to asterisk) instead of simply
disconnecting the call.
Further and much more problematic, if the re-invite fails, the call is
left dangling forever! This is not a minor bug.
it should be at least possible to configure whether to re-invite on bye
and maybe support it directly in Dial().
Issue History
Date Modified Username Field Change
======================================================================
2009-07-26 06:03 hzshlomi Note Added: 0108230
======================================================================
More information about the asterisk-bugs
mailing list