16 Jan
2009
16 Jan
'09
6:22 p.m.
Daniel,
You are rude and over the limit. I clearly see that the project is your
play ground and place to show your frustration.....just a huge lack of
respect for other people here....
Technically speaking, I will not comment your aberrations ....
Regards,
Bogdan
PS: you know, do try to lie yourself and accept that openser split in 2
parts....whatever you like it or not.....if you think a SVN repo defines
a project, well....good luck....
Daniel-Constantin Mierla wrote:
:-)) ...
now you are a good subject to make funny of....
You rushed and did a quick commit and then came back providing a link
to a feature that didn't existed few minutes ago ... and yes it is
funny, because the similar behavior could be achieved already (so
initial link with few more details could get it done).
The newer being better (how much better, have you tested?!?!) or not
is another topic. Don't forget to remove the old, lazy one, you can do
it in 30sec... (or, ahhh, you may want to preserve backward
compatibility, sorry...)
You mean: opensips got it when
replicated the source repository, as
Kamailio is the same project with OpenSER, you may want to check the
source tree repository:
http://openser.svn.sourceforge.net/viewvc/openser/
So nothing to get from openser to kamailio, the are the same and only
one project.
kamailio (openser) has for quite some time a parameter
in registrar
module that can overwrite from where to get the aor:
http://www.kamailio.org/docs/modules/devel/registrar.html#id2467548
It is in the last two major release at least: openser 1.3.x and
kamailio 1.4.x
I like you logic here :)..you are funny man :)...
modparam("registrar", "aor_avp", "$avp(i:3223)")
$avp(i:3223) = $fu;
if(registered())
{
...
}
Of course this notation is present since openser 1.3 and it was
inherited by both OpenSIPS 1.4.4 and Kamilio 1.4.3, but now we try to get a better approach of this
functionality: why
put the value into an AVP and let the function search all the time
for that AVP (set or not set), when you can simply take advantage and
directly pass the value as parameter to the function. You get read of
(1) useless transit via an AVP and (2) useless AVP search all the
time. Also you get a more compact and clear scripting....
Then start moving module
parameters specifying avps to be get as input
for functions to parameters of the functions (e.g., you can begin with
tm) -- you know that also from openser, opensips got support for
config functions with more than two parameters.
Daniel
Regards,
Bogdan
Cheers,
Daniel
Michel,
The proper way to do this -- assuming your motive is security and
authorisation -- is to challenge the incoming INVITE initial
request of the caller (who is supposed to be registered) with a 407
proxy challenge, i.e. proxy_authorize()/proxy_challenge().
Bogdan-Andrei Iancu wrote:
> Hi Michel,
>
> See the registered() function from the registrar module:
>
> http://www.opensips.org/html/docs/modules/1.4.x/registrar.html#id271407
>
>
> Regards,
> Bogdan
>
> michel freiha wrote:
>
>> Dear All,
>> I need to ask please about which function should I use in order
>> to check while making a call if the user who is dialing the
>> number is making the call from a registered account or not?
>>
>> Regards
>> ------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users(a)lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>