Hello Saul, You are right. Removing the checks did the trick (since indeed the authentication took place in the core opensips). Btw, I've noticed that when having the 'presence' OpenSIPS listening on a different IP that the 'core' OpenSIPS certain messages fail to go through since the realm cannot be matched. Do you know of a way to go around this?
Regards, Paris Stamatopoulos -----Original Message----- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Saúl Ibarra Corretgé Sent: Tuesday, March 23, 2010 10:05 AM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] OpenSIPS & OpenXCAP > The message is generated from this part of OpenSIPS-Presence configuration: > > if (is_from_local()) { > if (avp_check("$hdr(Event)", "fm/presence*/i")&& ($au != $rU || $ar != > $rd)) { > xlog("L_WARN", "Account $...@$ar tried to publish $hdr(Event) > event for $ru\n"); > sl_send_reply("403", "Publishing $hdr(Event) events for others > is forbidden"); > > return; > } > } > If you authenticated the request in the 'core' OpenSIPS and then relayed it to the 'presence' OpenSIPS, the request won't have the authorization headers, so you can't check $au nor $ar. Regards, -- Saúl Ibarra Corretgé AG Projects _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
