[asterisk-bugs] [Asterisk 0011349]: [patch] Deprecate SIPPEER() and move functionality into CHANNEL()

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11349 
====================================================================== 
Reported By:                blitzrage
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11349
Category:                   Functions/func_channel
Reproducibility:            N/A
Severity:                   tweak
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             11-22-2007 09:00 CST
Last Modified:              11-22-2007 09:14 CST
====================================================================== 
Summary:                    [patch] Deprecate SIPPEER() and move functionality
into CHANNEL()
Description: 
Here is a patch that I worked on while on the train in order to get my feet
wet with some C coding.

I'm not entirely sure I like the sip_peerinfo item name... maybe that
should just be sippeer?

I'm gonna try moving the IAXPEER() function into CHANNEL() as well, but
here is the first half of it for review.
====================================================================== 

---------------------------------------------------------------------- 
 dimas - 11-22-07 09:14  
---------------------------------------------------------------------- 
I'm not familar with the Asterisk release process, but doesn't "deprecate
something" also mean that some documentation like UPGRADE.txt/README.txt
should be updated as well?

And I know, it is personal preferrences but it would be easier to check
that all types properly described in description text if they appear in the
acf_channel_read and in the channel_function in the same order... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-22-07 09:14  dimas          Note Added: 0074198                          
======================================================================