[asterisk-bugs] [Asterisk 0014385]: Unhold fails if first SDP on OK, particularly Cisco CCM 6
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Feb 13 11:27:47 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-13 11:27 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.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0014448 [patch] chan_sip fails to remove hold w...
======================================================================
----------------------------------------------------------------------
(0100114) davidw (reporter) - 2009-02-13 11:27
http://bugs.digium.com/view.php?id=14385#c100114
----------------------------------------------------------------------
I was trying to understand the patch in the context of the 1.6.0.1 which we
are actually using.
I think I need to understand how it got removed, and how it works in the
1.4 context, before I can say that the removal is the problem (I've only
just come back to this today, after various higher priority jobs).
At the moment I'm just going on what the comment says, although Cisco
always sends its SDP on the ACK, so I don't think it is actually signalling
unhold by late SDP.
Issue History
Date Modified Username Field Change
======================================================================
2009-02-13 11:27 davidw Note Added: 0100114
======================================================================
More information about the asterisk-bugs
mailing list