9 Jun
2009
9 Jun
'09
3 p.m.
Im trying to implement Keep alive to maintain communication with nated
clients. Enabling it in the terminals
We eliminate OPTIONS natpings setbflag(7);
We want to eliminate setbflag(6); because when this is setted openser send 4
bytes packages to maintain the communication with nated clients. But if we
do that we have problems using mediaproxy.
Can you help me with this issue?
I hope to have explained correctly.
Ariadne L. Ramos Solís
Depto. Ingeniería
Aprovisionamiento y Señalización VoIP
Galaxy Communications Corp.
Tel. 2000117
e-mail <mailto:aramos@clarocom.com> aramos(a)clarocom.com
P BE CARBON CONSCIOUS. PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS
E-MAIL
9 Jun
9 Jun
4:53 p.m.
If you are going to 'ping' the server you could deactivate the udp
ping by setting natping_interval to 0.
http://www.kamailio.org/docs/modules/1.5.x/nathelper.html#id2453019
Nevertheless, I would keep it active, and set ping_nated_only to 1, so
you just ping clients which are known to be behind NAT.
--
Saúl -- "Nunca subestimes el ancho de banda de un camión lleno de disketes."
----------------------------------------------------------------
http://www.saghul.net/
5:08 p.m.
El Martes, 9 de Junio de 2009, Saúl Ibarra escribió:
Nevertheless, I would keep it active, and set
ping_nated_only to 1, so
you just ping clients which are known to be behind NAT.
The only problem with it is when a fuc**ng SIP ALG enabled router takes place.
It will modify the request so it'll look as coming from public IP (NAT cannot
be detected in Kamailio), but most of these infernal routers don't mantain the
keepalive so the input traffic is closed after UDP "connection" expires in the
router.
--
Iñaki Baz Castillo <ibc(a)aliax.net>
5:15 p.m.
Iñaki Baz Castillo wrote:
El Martes, 9 de Junio de 2009, Saúl Ibarra escribió:
Yep. Infernal - well said!
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
Nevertheless, I would keep it active, and set
ping_nated_only to 1, so
you just ping clients which are known to be behind NAT.
The only problem with it is when a fuc**ng SIP ALG enabled router takes place.
It will modify the request so it'll look as coming from public IP (NAT cannot
be detected in Kamailio), but most of these infernal routers don't mantain the
keepalive so the input traffic is closed after UDP "connection" expires in the
router.
5:20 p.m.
El Martes, 9 de Junio de 2009, Alex Balashov escribió:
Iñaki Baz Castillo wrote:
This is my personal battle against SIP ALG routers:
http://www.voip-info.org/wiki/view/Routers+SIP+ALG
Please, feel free to add any useful information about infernal routers with
SIP ALG enabled.
Thanks a lot :)
--
Iñaki Baz Castillo <ibc(a)aliax.net>
El Martes, 9 de Junio de 2009, Saúl Ibarra
escribió:
Yep. Infernal - well said! Nevertheless, I would keep it active, and set
ping_nated_only to 1, so
you just ping clients which are known to be behind NAT.
The only problem with it is when a fuc**ng SIP ALG enabled router takes
place. It will modify the request so it'll look as coming from public IP
(NAT cannot be detected in Kamailio), but most of these infernal routers
don't mantain the keepalive so the input traffic is closed after UDP
"connection" expires in the router. 
10 Jun
10 Jun
4:20 a.m.
Iñaki Baz Castillo napsal(a):
El Martes, 9 de Junio de 2009, Alex Balashov
escribió:
SIP ALG routers are big pain, at least for me :-)
What I'm trying to do is automagically detect users behind such a stupid
routers (analyzing INVITEs and REGISTERs in sip-dump) and automatically
send them e-mails aksing to disable SIP ALG.
Just my 2c...
Best regards,
kokoska.rokosoka
Iñaki Baz Castillo wrote:
This is my personal battle against SIP ALG routers:
http://www.voip-info.org/wiki/view/Routers+SIP+ALG
Please, feel free to add any useful information about infernal routers with
SIP ALG enabled.
Thanks a lot :)
El Martes, 9 de Junio de 2009, Saúl Ibarra
escribió:
Yep. Infernal - well said! Nevertheless, I would keep it active, and set
ping_nated_only to 1, so
you just ping clients which are known to be behind NAT.
The only problem with it
is when a fuc**ng SIP ALG enabled router takes
place. It will modify the request so it'll look as coming from public IP
(NAT cannot be detected in Kamailio), but most of these infernal routers
don't mantain the keepalive so the input traffic is closed after UDP
"connection" expires in the router.
1:54 p.m.
El Miércoles, 10 de Junio de 2009, kokoska rokoska escribió:
SIP ALG routers are big pain, at least for me :-)
What I'm trying to do is automagically detect users behind such a stupid
routers (analyzing INVITEs and REGISTERs in sip-dump) and automatically
send them e-mails aksing to disable SIP ALG.
Just my 2c...
I plan to build a small software (hopefully running on Linux and Windows)
which will connect with my server in order to detect if there is a SIP ALG
router in the path.
I just need some spare time :)
--
Iñaki Baz Castillo <ibc(a)aliax.net>
11 Jun
11 Jun
6:40 a.m.
Iñaki Baz Castillo napsal(a):
El Miércoles, 10 de Junio de 2009, kokoska rokoska
escribió:
Sounds interesting :-)
If you think I can help you (at least with testing 'cos I'm not good
programmer), drop me an e-mail...
Best regards,
kokoska.rokoska
SIP ALG routers are big pain, at least for me
:-)
What I'm trying to do is automagically detect users behind such a stupid
routers (analyzing INVITEs and REGISTERs in sip-dump) and automatically
send them e-mails aksing to disable SIP ALG.
Just my 2c...
I plan to build a small software (hopefully running on Linux and Windows)
which will connect with my server in order to detect if there is a SIP ALG
router in the path.
I just need some spare time :)
7:05 a.m.
El Jueves, 11 de Junio de 2009, kokoska rokoska escribió:
Iñaki Baz Castillo napsal(a):
Sure, when I've it ready I'll announce it here so you can test it :)
Thanks.
--
Iñaki Baz Castillo <ibc(a)aliax.net>
El Miércoles, 10 de Junio de 2009, kokoska
rokoska escribió:
Sounds interesting :-)
If you think I can help you (at least with testing 'cos I'm not good
programmer), drop me an e-mail... SIP ALG routers are big pain, at least for me
:-)
What I'm trying to do is automagically detect users behind such a stupid
routers (analyzing INVITEs and REGISTERs in sip-dump) and automatically
send them e-mails aksing to disable SIP ALG.
Just my 2c...
I plan to build a small software (hopefully running on Linux and Windows)
which will connect with my server in order to detect if there is a SIP
ALG router in the path.
I just need some spare time :) 
6:51 a.m.
Hello,
On 06/10/2009 11:20 AM, kokoska rokoska wrote:
Iñaki Baz Castillo napsal(a):
some do not offer any such option, even I googled a lot some time ago, I
couldn't get a solution for a siemens gigaset se36. If someone knows,
would be great.
However, it was easy to trick by listening on 5062 with kamailio and
pointing my phones to use that dst port. I haven't tried with tcp,
another option that should be tried with those algs.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
El Martes, 9 de Junio de 2009, Alex Balashov
escribió:
SIP ALG routers are big pain, at least for me :-)
What I'm trying to do is automagically detect users behind such a stupid
routers (analyzing INVITEs and REGISTERs in sip-dump) and automatically
send them e-mails aksing to disable SIP ALG.
Just my 2c...
Iñaki Baz Castillo wrote:
This is my personal battle against SIP ALG routers:
http://www.voip-info.org/wiki/view/Routers+SIP+ALG
Please, feel free to add any useful information about infernal routers with
SIP ALG enabled.
Thanks a lot :)
El Martes, 9 de Junio de 2009, Saúl Ibarra
escribió:
> Nevertheless, I would keep it active, and set ping_nated_only to 1, so
> you just ping clients which are known to be behind NAT.
>
The only problem with it is when a fuc**ng SIP ALG enabled router takes
place. It will modify the request so it'll look as coming from public IP
(NAT cannot be detected in Kamailio), but most of these infernal routers
don't mantain the keepalive so the input traffic is closed after UDP
"connection" expires in the router.
Yep. Infernal - well said!
6:54 a.m.
On 06/11/2009 01:51 PM, Daniel-Constantin Mierla wrote:
Hello,
On 06/10/2009 11:20 AM, kokoska rokoska wrote:
errata: gigaset se361 ...
Daniel
Iñaki Baz Castillo napsal(a):
some do not offer any such option, even I googled a lot some time ago,
I couldn't get a solution for a siemens gigaset se36 El Martes, 9 de Junio de 2009, Alex Balashov
escribió:
SIP ALG routers are big pain, at least for me :-)
What I'm trying to do is automagically detect users behind such a stupid
routers (analyzing INVITEs and REGISTERs in sip-dump) and automatically
send them e-mails aksing to disable SIP ALG.
Just my 2c...
Iñaki Baz Castillo wrote:
> El Martes, 9 de Junio de 2009, Saúl Ibarra escribió:
>
>> Nevertheless, I would keep it active, and set ping_nated_only to
>> 1, so
>> you just ping clients which are known to be behind NAT.
>>
> The only problem with it is when a fuc**ng SIP ALG enabled router
> takes
> place. It will modify the request so it'll look as coming from
> public IP
> (NAT cannot be detected in Kamailio), but most of these infernal
> routers
> don't mantain the keepalive so the input traffic is closed after UDP
> "connection" expires in the router.
>
Yep. Infernal - well said!
This is my personal battle against SIP ALG routers:
http://www.voip-info.org/wiki/view/Routers+SIP+ALG
Please, feel free to add any useful information about infernal
routers with SIP ALG enabled.
Thanks a lot :)
. If someone knows, would be great.
However, it was easy to trick by listening on 5062 with kamailio and
pointing my phones to use that dst port. I haven't tried with tcp,
another option that should be tried with those algs.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
7:06 a.m.
El Jueves, 11 de Junio de 2009, Daniel-Constantin Mierla escribió:
I haven't tried with tcp,
another option that should be tried with those algs.
I've seen some Cisco routers doing ALG for SIP TCP (port 5060 or whatever port
you configure in the Cisci for it). :(
--
Iñaki Baz Castillo <ibc(a)aliax.net>
7:18 a.m.
Iñaki Baz Castillo napsal(a):
El Jueves, 11 de Junio de 2009, Daniel-Constantin
Mierla escribió:
Yes, at least CISCO ASA and CISCO PIX...
Best regards,
kokoska.rokoska
I haven't tried with tcp,
another option that should be tried with those algs.
I've seen some Cisco routers doing ALG for SIP TCP (port 5060 or whatever port
you configure in the Cisci for it). :(
7:28 a.m.
On 06/11/2009 02:18 PM, kokoska rokoska wrote:
Iñaki Baz Castillo napsal(a):
these are super master ALGs :-) ...
usually these are the steps I try when facing algs:
- if no option to disable alg in router, set a second port in kamailio
- if above fails and phone can do tcp, try it
- if above fails and phone can do tls, try it
- if above fails drop the alg router :-), use it as press-papier, buy a
cheaper one that didn't waste resources for such crap
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
El Jueves, 11 de Junio de 2009, Daniel-Constantin
Mierla escribió:
Yes, at least CISCO ASA and CISCO PIX...
I haven't tried with tcp,
another option that should be tried with those algs.
I've seen some Cisco routers doing ALG for SIP TCP (port 5060 or
whatever port
you configure in the Cisci for it). :(
9 Jun
9 Jun
5:29 p.m.
The only problem with it is when a fuc**ng SIP ALG
enabled router takes place.
It will modify the request so it'll look as coming from public IP (NAT cannot
be detected in Kamailio), but most of these infernal routers don't mantain the
keepalive so the input traffic is closed after UDP "connection" expires in the
router.
Oh, I forgot to take that into account! Thanks for the pointer! :)
--
Saúl -- "Nunca subestimes el ancho de banda de un camión lleno de disketes."
----------------------------------------------------------------
http://www.saghul.net/
5691
days inactive
5693
days old
14 comments
6 participants
participants (6)
-
Alex Balashov -
Ariadne Ramos -
Daniel-Constantin Mierla -
Iñaki Baz Castillo -
kokoska rokoska -
Saúl Ibarra