Good day.
Need tips for radius auth/accounting.
At fist, if I understand correctly, some changes here:
modparam("acc", "service_type", 15)
modparam("acc", "radius_extra", "Sip-Src-IP=$si;Sip-Src-Port=$sp")
must be replaced to
modparam("acc_radius", "service_type", 15)
modparam("acc_radius", "r
On 4/10/13 1:25 PM, Iñaki Baz Castillo wrote:
Please, RFC 5626 is the solution for NAT.
I thought Olle was about to agree, except the RFC number
being in fact 2460 :)
jiri
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
Juha Heinanen writes:
> if i understood the above correctly, existence of received param in path
> header of register request, automatically sets nat bflag that (in my
> case 7). where is that documented?
it is documented here:
3.19. path_use_received (integer)
If set to 1, the “received” p
Juha Heinanen writes:
> however, when i look what gets stores in location table, cflags column
> of the contact has value 384. it is also shown by ul_dump:
>
> Cflag:: 384
>
> 384 = 256 + 128. i must be missing something trivial. how is it
> possible that also flag 7 (which is my nat_bflag) ge
i have in config:
setbflag(8);
xlog("L_INFO", "bflags are <$bf/$bF>\n");
save("location", "0x02");
and i correctly get to syslog:
Apr 10 19:51:48 wheezy1 /usr/sbin/sip-proxy[6722]: INFO: bflags
José Luis Millán writes:
> That is a wrong formed URI but a right formed URI parameter. The right URI
> format for the above is:
>
> sip:192.98.102.11:35453;transport=tcp
>
> While the right format for the same info when it is used as an URI
> parameter is:
>
> sip:192.98.102.11:35453%3Btranspo
Hi,
On 04/10/2013 02:54 PM, Juha Heinanen wrote:
i consider it a bad idea to call the new media proxy mediaproxy-ng,
because it gives impression that this is a new incarnation of ag projects
mediaproxy that has existed for years.
mediaproxy-ng also exists for years (since 2007, prior to the re
El Wed, 10 Apr 2013 14:41:33 +0200
"Olle E. Johansson" escribió:
>
> 10 apr 2013 kl. 14:38 skrev Richard Fuchs :
>
> > On 04/10/13 04:17, Klaus Darilion wrote:
> >
> >> I think it is a bad idea to name the relay "mediaproxy-ng" and the
> >> corresponding Kamailio module "rtpproxy-ng".
> >
> >
Remember that Outbound also works for UDP. In that case:
a) The Outbound Flow Token (the URI username in the Record-Route) must
encode the public source IP:port of the request, and the Outbound
proxy must be capable of encoding and decoding it for routing the
request to the client (OverSIP does it
10 apr 2013 kl. 15:32 skrev Peter Dunkley :
> When using a non-outbound client like Jitsi you can keep-alive by getting it
> to re-REGISTER, OPTIONS ping, or '\r\n' frequently.
>
> IMHO that is far better solution than having the server run timers and
> generate keep-alives.
>
> Regards,
>
>
Olle E. Johansson writes:
> > Who does keep-alive when outbound is used? If it is the client, then
> > there still must be some tweaks in the server as the non-outbound
> > client will not send keep-alive.
>
> Outbound puts all the client connection management burden upon the
> client.
yes, but
When using a non-outbound client like Jitsi you can keep-alive by
getting it to re-REGISTER, OPTIONS ping, or '\r\n' frequently.
IMHO that is far better solution than having the server run timers and
generate keep-alives.
Regards,
Peter
On 10/04/13 13:53, Klaus Darilion wrote:
Who does keep
10 apr 2013 kl. 14:53 skrev Klaus Darilion :
>
>
> On 10.04.2013 12:58, Iñaki Baz Castillo wrote:
>> There is no need at all for clients to be Outbound aware. The proxy can
>> force it in the same way current "alias" / "contact mangling" /
>> "received stuff" is used.
>
> Who does keep-alive w
Hi,
Try to give is_user_in() the whole URI as in sip:username@domain or just
username@domain. I am not sure what format it expects.
/Morten
On Wed, Apr 10, 2013 at 12:03 PM, phillman25 wrote:
>
> Thank you Daniel and Morten for your assistance and prompt reply.
>
> To use the tobody transform
i consider it a bad idea to call the new media proxy mediaproxy-ng,
because it gives impression that this is a new incarnation of ag projects
mediaproxy that has existed for years.
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users m
On 10.04.2013 12:58, Iñaki Baz Castillo wrote:
There is no need at all for clients to be Outbound aware. The proxy can
force it in the same way current "alias" / "contact mangling" /
"received stuff" is used.
Who does keep-alive when outbound is used? If it is the client, then
there still mu
10 apr 2013 kl. 14:38 skrev Richard Fuchs :
> On 04/10/13 04:17, Klaus Darilion wrote:
>
>> I think it is a bad idea to name the relay "mediaproxy-ng" and the
>> corresponding Kamailio module "rtpproxy-ng".
>
> I've considered that. Apart from the other reasons already mentioned,
> for me the d
On 04/10/13 04:17, Klaus Darilion wrote:
> I think it is a bad idea to name the relay "mediaproxy-ng" and the
> corresponding Kamailio module "rtpproxy-ng".
I've considered that. Apart from the other reasons already mentioned,
for me the deciding factor was that the new module forms a drop-in
rep
2013/4/10 Juha Heinanen :
> Olle E. Johansson writes:
>
>> Can't you add and forward to yourself again? I do crazy stuff like that in
>> many places. Just loop around to force a new transaction with new headers.
>>
>> Just an idea. Maybe totally stupid.
>
> could be done, but it adds complexity and
10 apr 2013 kl. 13:09 skrev Juha Heinanen :
> Olle E. Johansson writes:
>
>> Can't you add and forward to yourself again? I do crazy stuff like that in
>> many places. Just loop around to force a new transaction with new headers.
>>
>> Just an idea. Maybe totally stupid.
>
> could be done, but
Olle E. Johansson writes:
> Can't you add and forward to yourself again? I do crazy stuff like that in
> many places. Just loop around to force a new transaction with new headers.
>
> Just an idea. Maybe totally stupid.
could be done, but it adds complexity and overhead. there is enough
time be
10 apr 2013 kl. 12:54 skrev Juha Heinanen :
> Peter Dunkley writes:
>
>> You can use the force_outbound option in the outbound module to make
>> path and rr add flow-tokens even when the client isn't doing outbound.
>
> thank for info. it may not work though, if registrar and edge proxy are
>
There is no need at all for clients to be Outbound aware. The proxy can
force it in the same way current "alias" / "contact mangling" / "received
stuff" is used.
--
Iñaki Baz Castillo
El 10/04/2013 12:44, "Juha Heinanen" escribió:
> Iñaki Baz Castillo writes:
>
> > Anyhow, why is the received s
Single server outbound is on my todo list. I have put the details of
what is needed here: http://www.kamailio.org/wiki/devel/completing_outbound
Don't know if or when I'll get time to do it though.
Regards,
Peter
On 10/04/13 11:54, Juha Heinanen wrote:
Peter Dunkley writes:
You can use th
José Luis Millán writes:
> That is a wrong formed URI but a right formed URI parameter. The right URI
> format for the above is:
>
> sip:192.98.102.11:35453;transport=tcp
>
> While the right format for the same info when it is used as an URI
> parameter is:
>
> sip:192.98.102.11:35453%3Btranspo
Peter Dunkley writes:
> You can use the force_outbound option in the outbound module to make
> path and rr add flow-tokens even when the client isn't doing outbound.
thank for info. it may not work though, if registrar and edge proxy are
combined. in my current test, i have two proxies/registr
You can use the force_outbound option in the outbound module to make
path and rr add flow-tokens even when the client isn't doing outbound.
Regards,
Peter
On 10/04/13 11:44, Juha Heinanen wrote:
Iñaki Baz Castillo writes:
Anyhow, why is the received stuff required at all? IMHO it is time fo
Iñaki Baz Castillo writes:
> Anyhow, why is the received stuff required at all? IMHO it is time for
> dropping custom/proprietary hacks and use rfc 5626 Outbound instead.
> Otherwise we must live with hacks in lot of places of the code and
> modules.
unfortunately it will take years before most s
Of course I assume that modules dont implement unescaping uris encoded as
URI param value. That needs to be coded.
Anyhow, why is the received stuff required at all? IMHO it is time for
dropping custom/proprietary hacks and use rfc 5626 Outbound instead.
Otherwise we must live with hacks in lot of
Thank you Daniel and Morten for your assistance and prompt reply.
To use the tobody transformation, i see that i would need to upgrade to 4.1
right? Im currently on 3.3.
I tried the below code:
$var(i)=0;
while($(hdr(Diversion)[$var(i)]) != $null )
Hi,
2013/4/10 Juha Heinanen
> Juha Heinanen writes:
>
> > i tested and even when url path field contains escaped chars. however,
> > i started to get these to syslog every 20 seconds
> >
> > Apr 10 12:17:08 wheezy1 /usr/sbin/sip-proxy[3900]: ERROR: nathelper
> [nathelper.c:2018]: can't parse
Hi,
On 04/10/2013 11:02 AM, Jon Bonilla (Manwe) wrote:
I think it is a bad idea to name the relay "mediaproxy-ng" and the
corresponding Kamailio module "rtpproxy-ng".
Indeed
Well, the point is that it's "just" an enhancement of the rtpproxy
module. In the past, the rtpproxy module was used
Juha Heinanen writes:
> i tested and even when url path field contains escaped chars. however,
> i started to get these to syslog every 20 seconds
>
> Apr 10 12:17:08 wheezy1 /usr/sbin/sip-proxy[3900]: ERROR: nathelper
> [nathelper.c:2018]: can't parse contact uri
>
>
> most likely due to nat
i tested and even when url path field contains escaped chars. however,
i started to get these to syslog every 20 seconds
Apr 10 12:17:08 wheezy1 /usr/sbin/sip-proxy[3900]: ERROR: nathelper
[nathelper.c:2018]: can't parse contact uri
most likely due to nat pinging. i haven't checked yet where
El Wed, 10 Apr 2013 10:17:18 +0200
Klaus Darilion escribió:
>
>
> On 02.04.2013 15:05, Richard Fuchs wrote:
> > Hi,
> >
> > On 04/01/13 10:03, Aft nix wrote:
> >
> >> I stumbled upon this git://github.com/sipwise/mediaproxy-ng.git which
> >> looked very neat to me. Its said that it can be used
2013/4/10 Juha Heinanen :
> here is an example:
>
> Path:
> .
Perfect.
> as you see, single quotes are gone, because they don't serve any purpose
> after escape.
Not exactly, I want to insist on this: Single quotes did not server
any purpose previously because using single quotes to delimit an
Iñaki Baz Castillo writes:
> Juha, could you please paste here how the Path above looks with your
> change?
here is an example:
Path:
.
as you see, single quotes are gone, because they don't serve any purpose
after escape.
-- juha
___
SIP Express R
BTW not sure if your patch does it but I strongly suggest removing the
useless and wrong single quotes around the received value (once such a
value is properly hex-escaped it becomes a valid URI param value).
Please remember that single quote is NOT a valid delimitator AT ALL
for a SIP URI paramete
Good day!
I had in config:
modparam("acc_radius", "radius_extra", "User-Name=XXX")
and get same error when start kamailio:
ERROR: acc [acc_extra.c:192]: parse failed in around position 10
Any attributes from dictionary anyway got same message.
--
SY,
Victor
JID: coy...@bks.tv
Juha, could you please paste here how the Path above looks with your change?
Thanks a lot.
2013/4/10 Juha Heinanen :
> below is patch that fixes receiced param value. i have not tested if
> kamalio that gets such a value is able to unescape the escaped chars.
> if not, that is a bug too.
>
> --
Youngjin Park writes:
> I have a problem with "Route" header in my proxy server. Incoming
> invite has "Route" header with the IP of the proxy. So, the proxied
> invite from proxy server is looping back to the proxy server.
> I believe that "Route" cannot be removed or deleted because it is one
>
On 02.04.2013 15:05, Richard Fuchs wrote:
Hi,
On 04/01/13 10:03, Aft nix wrote:
I stumbled upon this git://github.com/sipwise/mediaproxy-ng.git which
looked very neat to me. Its said that it can be used with kamailio. It
seems like its backed sipwise inc.
But no documentation is given there
Hi,
I have a problem with "Route" header in my proxy server. Incoming
invite has "Route" header with the IP of the proxy. So, the proxied
invite from proxy server is looping back to the proxy server.
I believe that "Route" cannot be removed or deleted because it is one
of system header. Is there a
В Thu, 04 Apr 2013 21:07:34 +0200
Daniel-Constantin Mierla пишет:
> Hello,
>
> a rather old tutorial, from openser time, is available at:
>
> - http://www.kamailio.org/docs/openser-radius-1.0.x.html
>
> That should be still useful to get the idea of configuring radius
> side. Regarding Kamaili
44 matches
Mail list logo
