[asterisk-bugs] [Asterisk 0014385]: Unhold fails if first SDP on OK, particularly Cisco CCM 6
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Feb 11 09:36:36 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14385
======================================================================
Reported By: davidw
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14385
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.6.0.1
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-02-02 06:39 CST
Last Modified: 2009-02-11 09:36 CST
======================================================================
Summary: Unhold fails if first SDP on OK, particularly Cisco
CCM 6
Description:
Cisco CCM 6 appears never to send SDP on the INVITE, so Asterisk
effectively makes the offer, even when the Cisco is re-inviting because a
CCM hosted phone has gone on hold. Asterisk sets up its SDP from flags[1]
in the channel private data structure, which means that, if the channel was
on hold, it will offer a=inactive (observed, although a=recvonly also seems
possible). Even if the CCM intended to unhold, the only possible response
to an a=inactive offer, is a=inactive. Asterisk should only actually use
saved state if it is making the response. For an offer, as it looks like
it can never locally hold, it should offer a=sendrecv.
======================================================================
----------------------------------------------------------------------
(0099890) davidw (reporter) - 2009-02-11 09:36
http://bugs.digium.com/view.php?id=14385#c99890
----------------------------------------------------------------------
This may be related to http://bugs.digium.com/view.php?id=14448, although, at
the moment I can't be sure
that it would fix it, or even that it would not make things worse. I think
adding a related link would be useful, if only to make "frawd" aware of
this one.
Issue History
Date Modified Username Field Change
======================================================================
2009-02-11 09:36 davidw Note Added: 0099890
======================================================================
More information about the asterisk-bugs
mailing list