Files
asterisk/channels
Richard Mudgett c453d72423 Merged revisions 283049 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.6.2

................
  r283049 | rmudgett | 2010-08-20 10:31:03 -0500 (Fri, 20 Aug 2010) | 29 lines
  
  Merged revisions 283048 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r283048 | rmudgett | 2010-08-20 10:24:36 -0500 (Fri, 20 Aug 2010) | 22 lines
    
    Q931 - Sending PROGRESS after sending ALERTING is a protocol error
    
    The PRI layer in chan_dadhi will check if a PROGRESS message has already
    been sent, and not allow sending another (although that is technically
    allowed by the Q931 spec), however it does not protect against sending an
    ALERTING and then sending a PROGRESS message, which is a violation of the
    specification.
    
    Most switches don't seem to care too deeply about this, but some do, and
    will disconnect the call when receiving this invalid sequence.
    
    Protocol specification reference: T-REC-Q.931-199805-I page 223, "Figure
    A.5/Q.931 -- Overview protocol control (network side) point-point
    (sheet 3 of 8)"
    
    (closes issue #17874)
    Reported by: nic_bellamy
    Patches:
          asterisk-1.4-r282537_no-progress-after-alerting.patch uploaded by nic bellamy (license 299)
          asterisk-1.6.2-r282537_no-progress-after-alerting.patch uploaded by nic bellamy (license 299)
          asterisk-trunk-r282537_no-progress-after-alerting.patch uploaded by nic bellamy (license 299)
  ........
................


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.8@283050 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2010-08-20 15:35:38 +00:00
..
2009-08-10 19:20:57 +00:00
2010-07-14 15:48:36 +00:00
2008-10-09 14:17:33 +00:00
2009-08-10 19:20:57 +00:00
2010-06-07 20:04:42 +00:00