[asterisk-bugs] [Asterisk 0018946]: (Call Completion / SIP) PUBLISH Fails (412 Conditional Request Failed)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18946 
====================================================================== 
Reported By:                GeorgeKonopacki
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18946
Category:                  
Channels/chan_sip/CallCompletionSupplementaryServices
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-03-09 09:16 CST
Last Modified:              2011-03-09 11:03 CST
====================================================================== 
Summary:                    (Call Completion / SIP) PUBLISH Fails (412
Conditional Request Failed)
Description: 
Tested with release version of 1.8.0.

When the asterisk server receives a PUBLISH message for call completion,
the function ‘cc_esc_publish_handler’ gets called in ‘chan_sip.c’.

This function then calls ‘find_sip_cc_agent_by_notify_uri’. This
function always fails to find the agent so a response of ‘412 Conditional
Request Failed’ is sent.

By replacing ‘find_sip_cc_agent_by_notify_uri’ with
‘find_sip_cc_agent_by_subscribe_uri’ then everything then works as
expected.


This bug also appears to be in 1.8.3 (not tested, only looked at the
source code).
====================================================================== 

---------------------------------------------------------------------- 
 (0132774) mmichelson (administrator) - 2011-03-09 11:03
 https://issues.asterisk.org/view.php?id=18946#c132774 
---------------------------------------------------------------------- 
Which URI are you putting in the R-URI when you send the PUBLISH? The
NOTIFY that said the target was ready contained a new URI, and that's what
Asterisk is expecting the PUBLISH to use. If you're re-using the URI from
the SUBSCRIBE, that would be why the bug is occurring.

I think the best solution to this would be for Asterisk to expect the URI
from the NOTIFY to be used, but fall back to trying the URI from the
SUBSCRIBE if the first try does not succeed. Does this sound reasonable to
you? I can re-read the call completion draft just to be certain we didn't
misinterpret which URI the PUBLISH is supposed to use. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-09 11:03 mmichelson     Note Added: 0132774                          
======================================================================