[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-02 10:00 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0111793) rmudgett (administrator) - 2009-10-02 10:00
 https://issues.asterisk.org/view.php?id=15604#c111793 
---------------------------------------------------------------------- 
Please do not put dnid_subaddress in ast_party_connected_line.  It does not
belong there as it is information for a different party.  I think the
Dial(DAHDI/g1/number:subaddress) method is a better way to go for passing
that information to the outgoing side.  It allows the possibility of
forking the call.  i.e.,
Dial(DAHDI/g1/number:subaddress&DAHDI/g2/number:subaddress)

I think the encoding of the odd BCD digit (subaddress 12345) is supposed
to be encoded as 12 34 50 and not 12 34 05.  Also if you allow for full hex
digits, you are able to hedge your bets if the user_specified encoding is
not really BCD.  You only really know for certain if the encoding is BCD if
the odd flag is set. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-02 10:00 rmudgett       Note Added: 0111793                          
======================================================================