Hello,
Printing in script the return code of the www_authorize function will
give you a clue why the auth failed (see
http://www.opensips.org/html/docs/modules/1.10.x/auth_db.html#id250137).
Keep in mind that auth are per SIP request (each must be individually
authenticated) and the auth non
Ya, that is what I thought, but I was wondering if there is a way to just
have the opensips validate on first try because first registration SIP
already have the username and password. The reason I ask is that it seems
something it will take more then 2 try for opensips to reply a 200OK. So
here
Why is it that when I use this function call on registration and opensips
will always reject the first registration request and then on the second one
it will sent back 200OK?
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/www-authorize-tp7589427.html
Sen
http://tools.ietf.org/id/draft-ietf-sip-call-flows-05.txt
Chapter 2.1
Vincent
Le 4 févr. 2014 à 17:46, bluerain a écrit :
> Why is it that when I use this function call on registration and opensips
> will always reject the first registration request and then on the second one
> it will sent ba
Thank you Bogdan... It is working now.
From: Bogdan-Andrei Iancu
To: OpenSIPS users mailling list
Sent: Wed, 7 July, 2010 9:35:46
Subject: Re: [OpenSIPS-Users] www_authorize return codes
Hi Bruce,
There is a small typo in the script (also the one I sent
tch: running default statement
> Jul 7 07:19:11 rambo /usr/sbin/opensips[20498]: Default
>
> So I guess -4 is being returned but it is still using default for some
> reason..?
>
> Thanks again Bogdan.
>
> Regards,
> Bruce
>
>
>
>
>
>
> -
using default for some reason..?
Thanks again Bogdan.
Regards,
Bruce
From: Bogdan-Andrei Iancu
To: OpenSIPS users mailling list
Sent: Tue, 6 July, 2010 22:40:45
Subject: Re: [OpenSIPS-Users] www_authorize return codes
The script is a bit buggy
just
case -2:
> xlog("L_INFO","Wrong password");
> break;
> case -1:
> xlog("L_INFO","User doesnt exist");
> break;
> def
O","Default");
}
}
Thanks,
Bruce
____
From: Bogdan-Andrei Iancu
To: OpenSIPS users mailling list
Sent: Tue, 6 July, 2010 20:13:03
Subject: Re: [OpenSIPS-Users] www_authorize return codes
Hi Bruce,
no, they did not change. P
Hi Bruce,
no, they did not change. Post your switch to see if correct or not.
Regards,
Bogdan
Bruce Borrett wrote:
> Hi all
>
> I cant get switch to catch any return codes for www_authorize. The
> default catch works, but -5 through -1 as stated in the docs do not
> work, I also tried positive
Hi all
I cant get switch to catch any return codes for www_authorize. The default
catch works, but -5 through -1 as stated in the docs do not work, I also tried
positive 1 through 5... Have these codes changed?
Thanks in advance..
Regards,
Bruce
___
Hi Jayesh,
$retcode gives the return code of the LAST command you run in script. I
your case that is "log()" which is always true :DYou need to test
the $retcode value just after the pv_www_authorize(), otherwise you will
loose it.
Regards,
Bogdan
Jayesh Nambiar wrote:
> Hello All,
> I wa
Hello All,
I want to take my logic to a different route when authorize fails because of
an invalid password. Ideally the www_authorize should return -2 when it
fails because of invalid password.
But the return code stays as 1 only every time, even if the auth fails or
auth succeeds. I check the ret
13 matches
Mail list logo
