Summary:	ASTERISK-03740: The opaque has returned!
Reporter:	brads (brads)	Labels:
Date Opened:	2005-03-22 12:11:53.000-0600	Date Closed:	2011-06-07 14:10:36
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Registration
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) chan_sip.zip
Description:	Authentication to Primus tel denies the opaque field. RFC on sip authentication does not request the opaque statement, but Primus is supposed to be ignoring it. I was sent this patch to remove the opaque. Can you kindly include this in your next stable release? It is 100% confirmed that this opaque is the main problem.
Comments:	By: Kevin P. Fleming (kpfleming) 2005-03-22 12:28:39.000-0600 You did not upload a patch, you uploaded a zipped copy of chan_sip. In addition, we cannot accept patches for Asterisk without proper disclaimers being in place. Since you have stated that you are not the source of this patch, we cannot accept it until the copyright owner of the patch submits a proper disclaimer to Digium. In fact, we really cannot even look at it before that is done. By: Mark Spencer (markster) 2005-03-22 13:32:56.000-0600 This is the second time you have placed a bug report without following the bug guidelines for its severity and the fourth time you have placed a bug in violation of the bug guidelines generally.  If it weren't for your at least attempting to supply a patch, I would have already deleted this bug by now. Please read the directions before placing any more bugs! By: Olle Johansson (oej) 2005-03-22 14:28:49.000-0600 And for SIP bugs, especially if you want us to change anything in STABLE, we need sip.conf, a SIP debug of the session and references to proper RFCs. There is no SIP authentication RFC; some of it is in the SIP rfc and some of it in various RFCs on HTTP authentication... By: damin (damin) 2005-03-22 20:23:14.000-0600 Per the comments of the developers, this is not a bug and there is not enough information to actually do anything. Please keep the bug number (3830) handy and if you have a patch, or a sip trace to add, please feel free to add it. In the meantime, I'm going to close this out.