[asterisk-bugs] [Asterisk 0010217]: [patch] proper user information layer 1 handling

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10217 
====================================================================== 
Reported By:                klaus3000
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10217
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             07-17-2007 04:49 CDT
Last Modified:              12-17-2007 04:42 CST
====================================================================== 
Summary:                    [patch] proper user information layer 1 handling
Description: 
Hi!

Using Asterisk as H324M Gateway requires correct Q.931 signaling.
Currently Asterisk does not care about User Information Layer 1 signaling
in Bearer Capability IE.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0010189 Incorrect "user information layer ...
====================================================================== 

---------------------------------------------------------------------- 
 klaus3000 - 12-17-07 04:42  
---------------------------------------------------------------------- 
@corydon76: Sorry, yes you are right. I added UL1 to channel structure. But
the channel structure also already contains "transfercapability" which is
also a proprietary ISDN parameter.

Further, if UL1 is not stored in ast_chan but somehwere inside private
channel memory, how can it be retrieved from the second channel? e.g.:

-> incoming ZAP call -> UL1 is stored in zt_pvt
-> dial plan execution -> Dial(Zap/....)
-> outgoing ZAP call -> outgoing zap channel needs to know UL1 of incoming
ZAP channel - how can the outgoing zap channel know about the other zap
channel which holds the UL1 data? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-17-07 04:42  klaus3000      Note Added: 0075537                          
======================================================================