[asterisk-bugs] [Asterisk 0013034]: 183 response although progressinband=never
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Mar 18 08:54:34 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13034
======================================================================
Reported By: klaus3000
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13034
Category: Channels/chan_dahdi
Reproducibility: always
Severity: minor
Priority: normal
Status: confirmed
Asterisk Version: 1.4.21
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-07-09 07:03 CDT
Last Modified: 2009-03-18 08:54 CDT
======================================================================
Summary: 183 response although progressinband=never
Description:
Hi!
Scenario with Asterisk 1.4.21.1:
SIP Client ----> chan_sip:Dial(zap):chan_zap ---> ISDN
very simple dialplan:
[fromklaus]
exten => _1X.,1,NoOp(1... SIP: Outgoing Call: Asterisk->HiCom)
exten => _1X.,n,Dial(Zap/g1/${EXTEN:1})
Immediately after sending the SETUP message, Asterisk responds with 183
Session Progress. Thus, the SIP client is waiting for inband audio, but
there is no inband audio available. progressinband=never
sip.conf:
[klaus]
type=peer
username=klaus
host=dynamic
context=fromklaus
canreinvite=no
progressinband=never
actually I tried all progressinband settings without any difference
======================================================================
----------------------------------------------------------------------
(0101928) oej (manager) - 2009-03-18 08:54
http://bugs.digium.com/view.php?id=13034#c101928
----------------------------------------------------------------------
Please, please add long debug messages as attachments. It's really hard to
get an overview otherwise.
This issue is shown using woomera channels as well, so I'm wondering if
it's something general that needs to be fixed in the core, or if it's
really up to each channel to handle.
Issue History
Date Modified Username Field Change
======================================================================
2009-03-18 08:54 oej Note Added: 0101928
======================================================================
More information about the asterisk-bugs
mailing list