[asterisk-bugs] [Asterisk 0017180]: SetCallerpres not honored on SIP Redirect

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17180 
====================================================================== 
Reported By:                Dovid
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17180
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.18 
JIRA:                       SWP-1290 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-14 04:30 CDT
Last Modified:              2010-04-28 06:00 CDT
====================================================================== 
Summary:                    SetCallerpres not honored on SIP Redirect
Description: 
Hi,
If you set CallerPres to prohib_passed_screen on the initial invite it
goes out with out CID. If the peer sends a 302 re-direct when Asterisk
sends out the new invite it sends out the users CID when it should send
nothing because we set CallerPres to prohib_passed_screen.
====================================================================== 

---------------------------------------------------------------------- 
 (0121062) Dovid (reporter) - 2010-04-28 06:00
 https://issues.asterisk.org/view.php?id=17180#c121062 
---------------------------------------------------------------------- 
davidw:

I didn't understand what you said in the first message. I understand that
it is not related to the actual technology and that the issue is that when
asterisk gets the 302 it constructs a new channel and in the new channel it
does not pass to it that the CID should be blocked like it did in the first
channel which seems to be a bug when asterisk creates the second channel
just like pabelanger  stated. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-28 06:00 Dovid          Note Added: 0121062                          
======================================================================