[asterisk-bugs] [Asterisk 0019010]: Call stuck with "music on hold"

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19010 
====================================================================== 
Reported By:                ovi
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19010
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.3.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-03-22 15:03 CDT
Last Modified:              2011-03-23 06:58 CDT
====================================================================== 
Summary:                    Call stuck with "music on hold"
Description: 
We have a simple call scenario: caller calls callee and callee puts caller
on hold.  The caller receives music on hold.
When the callee tries to resume the call, music on hold is still being
played to the caller.  What is different from a regular scenario here is
the fact that the port and IP in SDP in the resume reINVITE is not the same
as it was before (when the media was active).
====================================================================== 

---------------------------------------------------------------------- 
 (0133090) davidw (reporter) - 2011-03-23 06:58
 https://issues.asterisk.org/view.php?id=19010#c133090 
---------------------------------------------------------------------- 
The session version has gone backwards, which may be sufficient to cause it
to be ignored (I'm not sure about the simultaneous change in session-ID). 
There is an option to ignore session version, to deal with peers with
broken session versions.

If you still think this is an Asterisk bug, you need to:

1) provide the standard SIP bug reporting information - verbose and debug
logging for sip set debug on and sip history output;

2) explain what ...92 and ...93 are.

Incidentally, I do not believe this affects large numbers of users, so it
is not "major". 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-23 06:58 davidw         Note Added: 0133090                          
======================================================================