[asterisk-bugs] [Asterisk 0015734]: [patch] CALLINGSUBADDR incorrectly stated as "Called PRI Subaddress"

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15734 
====================================================================== 
Reported By:                alecdavis
Assigned To:                lmadsen
====================================================================== 
Project:                    Asterisk
Issue ID:                   15734
Category:                   Documentation
Reproducibility:            always
Severity:                   text
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 212672 
Request Review:              
====================================================================== 
Date Submitted:             2009-08-17 22:35 CDT
Last Modified:              2009-09-09 07:30 CDT
====================================================================== 
Summary:                    [patch] CALLINGSUBADDR incorrectly stated as "Called
PRI Subaddress"
Description: 
When infact it is the "Calling parties Sub Address", as apposed to "Called
parties Sub Address".

PRI is too restricting, as it also applies to BRI.

====================================================================== 

---------------------------------------------------------------------- 
 (0110418) lmadsen (administrator) - 2009-09-09 07:30
 https://issues.asterisk.org/view.php?id=15734#c110418 
---------------------------------------------------------------------- 
It would be more trivial if all versions of Asterisk used TeX. They don't,
so I have to make sure I merge this correctly (and manually) into a couple
of branches.

I'm not a developer by nature, so I have to make sure I do this correctly.
Monday was a holiday, and yesterday was catch up day. It's also low on the
priority list right now (I have 18 issues assigned to me), so this probably
won't make it in until tomorrow or Friday at the earliest.

Unless someone else decides to pick it up. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-09 07:30 lmadsen        Note Added: 0110418                          
======================================================================