[asterisk-bugs] [LibPRI 0015604]: [patch] Support for called_party_subaddr, currently only calling_party_subaddr is supported

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15604 
====================================================================== 
Reported By:                alecdavis
Assigned To:                rmudgett
====================================================================== 
Project:                    LibPRI
Issue ID:                   15604
Category:                   NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                        
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-07-28 21:51 CDT
Last Modified:              2009-10-01 17:45 CDT
====================================================================== 
Summary:                    [patch] Support for called_party_subaddr, currently
only calling_party_subaddr is supported
Description: 
Looking at q931.c it only has dump_called_party_subaddr
it's missing receive_called_party_subaddr, transmit_called_party_subaddr,
and associated pri_call changes. Maybe more...

The Telecom Specs in NZ suggests that SUB ADDRESS is always on, so doing
"desk to desk" between offices each with an asterisk box over the ISDN
should then be possible, without a whole load of DDI numbers required.

Is there any work beinging done for this?


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001877 Useful enhancement to chan_zap would be...
====================================================================== 

---------------------------------------------------------------------- 
 (0111762) rmudgett (administrator) - 2009-10-01 17:45
 https://issues.asterisk.org/view.php?id=15604#c111762 
---------------------------------------------------------------------- 
I'll save any further code reviews until you are done.

The location of the information is determined by the assumed direction of
a channel.  The names ast->cid.subadress and ast->connected.id.subaddress
assumes that the channel was created by a call coming in from the network. 
The dialplan normally executes on channels of incoming calls.  Thus,
CALLERID() works on ast->cid.subaddress and CONNECTEDLINE() works on
ast->connected.id.subaddress.  What goes where can be confusing with
direction oriented names.

Party-A ----> incoming-channel --- core --- outgoing-channel ---->
Party-B
              Caller: Party A               Caller: Party B
              Connected: Party B            Connected: Party A 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-01 17:45 rmudgett       Note Added: 0111762                          
======================================================================