[asterisk-bugs] [LibPRI 0015604]: 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 
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-07-30 20:39 CDT
====================================================================== 
Summary:                    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...
====================================================================== 

---------------------------------------------------------------------- 
 (0108436) alecdavis (reporter) - 2009-07-30 20:39
 https://issues.asterisk.org/view.php?id=15604#c108436 
---------------------------------------------------------------------- 
Looks like both CALLED PARTY SUBADDR and CALLING PARTY SUBADDR transmit and
receive need some attention.

I tried setting SUBADDR from a Jtec's and called into Asterisk, using pri
intense debug, you see calling subaddr come in, and processed, but the
dialplan variable CALLINGSUBADDR isn't set
exten => 8599,1,NoOp(${CALLERID(num):-4}
callingsubaddr=${CALLINGSUBADDR})

calling_party_subaddr although supported, only works under certain
conditions.
https://issues.asterisk.org/view.php?id=1877#37658
"It seems that it only gets set if it's overlap dialling and
immediate=no"

like markster asked https://issues.asterisk.org/view.php?id=1877#11103
"Do you think it's important to be able to transmit it as well" 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-30 20:39 alecdavis      Note Added: 0108436                          
======================================================================