[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-26 08:32 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0120888) davidw (reporter) - 2010-04-26 08:32
 https://issues.asterisk.org/view.php?id=17180#c120888 
---------------------------------------------------------------------- 
1) it is not a SIP issue, even if it turns out that SIP is the only
technology for which far end initiated redirects are supported (some sort
of forward support exists for several channel technologies);

2) it doesn't even require that the bit before the / be the same for the
original and the redirected channel;

3) the most likely source file that will require changing is app_dial.c
(actually it looks like main_dial.c handles forwards, as well, and may be
what has to change).


All that the SIP 302 handler does is to set a field in the non-technology
specific channel structure.  Higher level, non-channel driver, code detects
that and initiates the redirected call.

(Telling me precisely which point you did not understand would have helped
me to give a better reply.) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-26 08:32 davidw         Note Added: 0120888                          
======================================================================