[asterisk-bugs] [Zaptel 0011554]: Invalid status reported when line are physically unpluged

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11554 
====================================================================== 
Reported By:                pascallambert
Assigned To:                qwell
====================================================================== 
Project:                    Zaptel
Issue ID:                   11554
Category:                   zaptel (the module)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Zaptel Version:             1.4.7.1  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             12-14-2007 11:19 CST
Last Modified:              12-14-2007 13:29 CST
====================================================================== 
Summary:                    Invalid status reported when line are physically
unpluged
Description: 
If one of my FXO line is unplugged (for whatever reason including a broken
cable) the call progression goes as normal as oppose to reported it wrong.

Setup:
Zap/1-1: FXS
Zap/3-1: FXO

plug Zap/1-1 to a phone and unplugged Zap/3-1. Then place a call using the
phone on Zap/1-1. This is what you see:
test-mdc*CLI>
    -- Starting simple switch on 'Zap/1-1'
    -- Executing [83909015 at default:1] Dial("Zap/1-1", "Zap/g1/83909015")
in newstack
     -- Called g1/83909015
    -- Zap/3-1 answered Zap/1-1
     -- Native bridging Zap/1-1 and Zap/3-1
test-mdc*CLI> core show channels
Channel              Location             State   Application(Data)

Zap/3-1              (None)               Up      Bridged Call(Zap/1-1)

Zap/1-1              83909015 at default:1   Up      Dial(Zap/g1/83909015)

2 active channels
1 active call
    -- Hungup 'Zap/3-1'
   == Spawn extension (default, 83909015, 1) exited non-zero on 'Zap/1-1'
     -- Hungup 'Zap/1-1'
test-mdc*CLI>

The major problem with this for us is we have developed a alarm callout
system running on Asterisk. But if a line is broken/disconnected everything
is reported as OK but of course the call never occurs and our customer
complain they never received the alarm message but our system stated they
have :-(
Of course those situation don't occur often but when they are a lot of
erroneous call may have been place in between the time we figured out what
is the problem.

====================================================================== 

---------------------------------------------------------------------- 
 qwell - 12-14-07 13:29  
---------------------------------------------------------------------- 
loloski is correct.  There isn't a whole heck of a lot we can do about this
on an analog line. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-14-07 13:29  qwell          Status                   new => resolved     
12-14-07 13:29  qwell          Resolution               open => fixed       
12-14-07 13:29  qwell          Assigned To               => qwell           
12-14-07 13:29  qwell          Note Added: 0075414                          
======================================================================