for those who want to patch their SIP, here is a quck fix to make
Asterisk do a little better:
--- chan_sip.c 2004-05-16 01:33:06.000000000 -0400
+++ chan_sip.c_OPTIONS 2004-05-17 14:30:36.000000000 -0400
@@ -5916,6 +5916,7 @@
/* Initialize the context if it hasn't been already */
if (!strcasecmp(cmd, "OPTIONS")) {
+ check_user(p, req, cmd, e, 0, sin, 0);
res = get_destination(p, req);
build_contact(p);
/* XXX Should we authenticate OPTIONS? XXX */
Olle E. Johansson wrote:
Karl Brose wrote:
Btw, Ignoring OPTIONS is not a valid option (:-) whether sip proxy or
not, Asterisk doesn't do it correctly either.
The host should respond with 200/OK if the call >could< succeed
theoretically if it were an INVITE or else it should send a
404 or maybe a 487(? hmm, have to look) see the RFC for details.
Interesting, didn't know that. Where in the RFC?
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
