6 Sep
2010
6 Sep
'10
11:17 a.m.
Hi!
Recently Asterisk implemented authentication of incoming OPTIONS
request. This means, that OPTIONS might be challenged - responding with
401/407.
Currently, the respone codes which are accept by dispatcher module as
SUCCESS are hard coded. Maybe there should be a configuration option to
configure SUCCESS response code.
regards
klaus
-------- Original-Nachricht --------
Betreff: Re: [asterisk-dev] [Code Review] SIP: authenticate OPTIONS
requests just like we would an INVITE
Datum: Fri, 3 Sep 2010 13:07:18 -0500 (CDT)
Von: David Vossel <dvossel(a)digium.com>
Antwort an: Asterisk Developers Mailing List <asterisk-dev(a)lists.digium.com>
An: Asterisk Developers Mailing List <asterisk-dev(a)lists.digium.com>
----- Original Message -----
From: "Klaus Darilion"
<klaus.mailinglists(a)pernau.at>
To: "Asterisk Developers Mailing List" <asterisk-dev(a)lists.digium.com>
Cc: "Olle E. Johansson" <oej(a)edvina.net>
Sent: Wednesday, September 1, 2010 12:53:41 PM
Subject: Re: [asterisk-dev] [Code Review] SIP: authenticate OPTIONS requests just like we
would an INVITE
looks like 401 will be an error, only 200, 501, 403
and 405 will be
accepted. So we have to add 401 for Asterisk? ;-)
Yes, it appears the 401 response will have to be added there. Do you
have commit access to this project? How can we get that done?
David Vossel
Digium, Inc. | Software Developer, Open Source Software
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org
The_Boy_Wonder in #asterisk-dev
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev