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

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Aug 3 05:28:41 CDT 2009


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-08-03 05:28 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0108529) alecdavis (reporter) - 2009-08-03 05:28
 https://issues.asterisk.org/view.php?id=15604#c108529 
---------------------------------------------------------------------- 
uploaded:
 chan_dahdi_called_subaddr.diff.txt
 libpri-called-subaddr.diff.txt

dialplan code:
exten => 4888,1,Set(__CALLEDSUBADDR=1234)
exten => 4888,n,NoOp(calledsubaddr = ${CALLEDSUBADDR})
exten => 4888,n,Dial(DAHDI/G0/4888)

console output with 'pri debug span 1'
> [6c 05 00 80 38 35 35]
> Calling Number (len= 7) [ Ext: 0  TON: Unknown Number Type (0)  NPI:
Unknown Number Plan (0)
>                           Presentation: Presentation permitted, user
number not screened (0)  '855' ]
> [70 05 80 34 38 38 38]
> Called Number (len= 7) [ Ext: 1  TON: Unknown Number Type (0)  NPI:
Unknown Number Plan (0)  '4888' ]
> [71 05 80 31 32 33 34]
> Called Sub-Address (len= 7) [ Ext: 1  Type: NSAP (X.213/ISO 8348 AD2)
(0)  O: 0  '1234' ]
q931.c:3237 q931_setup: call 32771 on channel 31 enters state 1 (Call
Initiated)
    -- Called G0/4888 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-03 05:28 alecdavis      Note Added: 0108529                          
======================================================================




More information about the asterisk-bugs mailing list