[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
Tue Aug 4 05:40:47 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-04 05:40 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0108579) alecdavis (reporter) - 2009-08-04 05:40
 https://issues.asterisk.org/view.php?id=15604#c108579 
---------------------------------------------------------------------- 
please remove the follwoing 2 files
  chan_dahdi_called_subaddr.diff.txt
  libpri-called-subaddr.diff2.txt

uploaded:
  libpri-subaddress.diff3.txt
  chan_dahdi-subaddress.diff3.txt

Both Called/Calling Party Subaddress support for transmit and receive.

There seems to be a race condition, where the call is being accepted after
the dialplan has started, and I'm missing the Subaddress.

<u>Correct:</u>
!! Unknown IE 50 (cs5, Unknown Information Element)
    -- <b>Accepting call from</b> '45609100' to '8599' on channel 0/1,
span 1
    -- Executing [8599 at incoming:1] Proceeding("DAHDI/1-1", "") in new
stack
    -- Executing [8599 at incoming:2] NoOp("DAHDI/1-1", "9100 callingsubaddr=
calledsubaddr=8765") in new stack


<u>Incorrect!!!:</u> Next call 30 seconds later. 
!! Unknown IE 50 (cs5, Unknown Information Element)
    -- Executing [8599 at incoming:1] Proceeding("DAHDI/1-1", "") in new
stack
    -- Executing [8599 at incoming:2] NoOp("DAHDI/1-1", "9100 callingsubaddr=
calledsubaddr=") in new stack
    -- Executing [8599 at incoming:3] GotoIf("DAHDI/1-1", "0?wait2:endwait")
in new stack
    -- Goto (incoming,8599,6)
    -- Executing [8599 at incoming:6] NoOp("DAHDI/1-1", "") in new stack
    -- Executing [8599 at incoming:7] GotoIf("DAHDI/1-1", "0?unavail") in new
stack
    -- Executing [8599 at incoming:8] VoiceMailMain("DAHDI/1-1", "") in new
stack
    -- <b>Accepting call from</b> '45609100' to '8599' on channel 0/1,
span 1



I 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-04 05:40 alecdavis      Note Added: 0108579                          
======================================================================




More information about the asterisk-bugs mailing list