[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-20 17:17 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0112501) rmudgett (administrator) - 2009-10-20 17:17
 https://issues.asterisk.org/view.php?id=15604#c112501 
---------------------------------------------------------------------- 
I have committed the libpri_subaddr_trunk.diff11.txt and
asterisk_subaddr_trunk.diff11.txt with some modifications (mostly spacing
anomalies and line length) to branches:
libpri/team/rmudgett/subaddr
asterisk/team/rmudgett/subaddr
respectively.

I fixed some off by one errors in the CALLERID and CONNECTEDLINE
functions.
I also fixed the CONNECTEDLINE(subaddr) set problem you mentioned in the
-dev list.

I was also thinking that when a call is redirected/diverted, we could
simply set the call_forward channel string to redirect to a number with a
subaddress as number:subaddress.  See how AST_STRING_FIELD(call_forward) is
used in struct ast_channel.  Then in the dialplan you could have:
exten => number:subaddress,n,NoOp()

Maybe, we should consider making an incoming call set the exten to
number:subaddress to further integrate subaddressing in the dialplan. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-20 17:17 rmudgett       Note Added: 0112501                          
======================================================================