<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [Users] Natping in "dispatcher scenario"</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi,<BR>
<BR>
It sounds reasonable to "dispatch" the nat ping function from the core due to load.<BR>
I'm trying to load share my clients based on DNS SRV and spread them over several OBP's.<BR>
<BR>
In my scenario I'm only ping'ing UA's without keep-alives implemented (flag'ing based on UA info in header). Fortunately these are not so many. That is why I wanted to see if the scenario I mentioend was possible.<BR>
<BR>
Looking forward to the updates.<BR>
<BR>
Thanks for your reply.<BR>
<BR>
Br,<BR>
Helge Waastad<BR>
Senior Engineer<BR>
Smartnet<BR>
tlf: 67830017<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Andreas Granig [<A HREF="mailto:andreas.granig@inode.info">mailto:andreas.granig@inode.info</A>]<BR>
Sent: Wed 2/8/2006 8:55 PM<BR>
To: Helge Waastad<BR>
Cc: users@openser.org<BR>
Subject: Re: [Users] Natping in "dispatcher scenario"<BR>
<BR>
Helge Waastad wrote:<BR>
> Does anyone else find it interesting to have the ping also relayed via<BR>
> the OBP?<BR>
> If not, I just have to move the registrar more towards the frontend.<BR>
<BR>
We ended up in implementing a simple stand-alone natping application for<BR>
a proof-of-concept design using raw sockets for spoofing the OBP<BR>
address, mainly for two reasons:<BR>
<BR>
- Performance: a possibility would be to evaluate the Path uri in the<BR>
registrar and send a sip-based nat-ping (OPTION) with a pre-set route,<BR>
but this would really stress the OBP (assume you've to ping 50.000 UACs<BR>
every 60 seconds).<BR>
<BR>
- Simplicity: it would require quite a lot of changes in<BR>
registrar/usrloc/nathelper/mediaproxy, so we just query the<BR>
received-column of usrloc from the external natping application(s) and<BR>
send empty udp packets.<BR>
<BR>
Patches to the registrar and a new path module for accomplishing this<BR>
(inserting proper Path headers in an OBP, and taking the<BR>
received-address from a Path uri parameter and saving it into usrloc in<BR>
a registrar) will be contributed the next days...<BR>
<BR>
Bye,<BR>
Andy<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>