<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-ZA" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal">Hi Guys,</p><p class="MsoNormal"> </p><p class="MsoNormal">I’m not an Kamalio expert, so I don’t really know what scales well etc. </p>
<p class="MsoNormal"> </p><p class="MsoNormal">So I must be honest the thread goes a little past what I currently know how to use in something to implement.</p><p class="MsoNormal"> </p><p class="MsoNormal">I’m also not sure what I can and can’t do in terms of making calls to something outside (if this is scalable or not) – I’m assuming making tons of webservice calls is not very efficient <span style="font-family:Wingdings">J</span>, which can track those timestamps, and each time something missed, mark it, or report it to the other system thats receiving these calls, where I can then report on devices that have say missed 10 pings this last x minutes, or missed 20 consecutive pings at any point in y minutes and so forth.</p>
<p class="MsoNormal">But obviously you don’t want it to only scale to 20 clients and then fall over.</p><p class="MsoNormal"> </p><p class="MsoNormal">We are small now, so I imagine this is quite possible. Other alternatives would be SNMP traps or SNMP queries etc. My client devices are configured themselves to use the options command anyhow every 10 seconds, if there is anyway to get a log of the last x minutes chatter summary times, or max interval in in the last x minutes where there was no chatter to a queriable dataset, this would be good. I don’t want to go down a bad road, I also don’t want to it to be “NASA ready”, it must just be workable for up to a few hundred clients (although I’m nowhere near that in size now).</p>
<p class="MsoNormal"> </p><p class="MsoNormal">Regards</p><p class="MsoNormal"><span style="color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:spce-user-bounces@lists.sipwise.com">spce-user-bounces@lists.sipwise.com</a> [mailto:<a href="mailto:spce-user-bounces@lists.sipwise.com">spce-user-bounces@lists.sipwise.com</a>] <b>On Behalf Of </b>Skyler<br>
<b>Sent:</b> 26 August 2012 08:50 AM<br><b>To:</b> Jon Bonilla<br><b>Cc:</b> <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br><b>Subject:</b> Re: [Spce-user] monitoring registered clients</span></p>
</div></div><p class="MsoNormal"> </p><p class="MsoNormal">Hi,</p><div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><div><p class="MsoNormal">
</p></div><p class="MsoNormal">From the server point of view, I've just seen this thread in the sip-router<br>mailing list. This might be useful as start for monitoring alive clients.<br><br><a href="http://lists.sip-router.org/pipermail/sr-users/2012-August/074337.html" target="_blank">http://lists.sip-router.org/pipermail/sr-users/2012-August/074337.html</a><br>
<br>Once the "dead" clients are removed from registration, one could just check<br>registered vs provisioned subscribers.<br><br>We have freezed 2.6 and we're working hard on releasing it before the end of<br>
this month. Once it's released we'll discuss the 2.7-2.8 roadmap and update it.<br>Not sure if this kind of feature (over the time flapping subscriber detection)<br>is something we can include in early or later releases. But it's something we<br>
could discuss in the mailing list and check what should be the best approach.<br><br><br>cheers<br><br>Jon</p></blockquote></div><div><p class="MsoNormal"><br> I saw that thread as well, its a great addition to Kamailio. Generally speaking though, I personally prefer that the client-side be in charge by sending NOTIFY to spce rather than the other way around. Monitoring from SPCE is not a bad idea if all of your endpoints are an Asterisk or similar PBX. Though a subscriber could be a soft-phone/mobile or ATA which may or may not always be registered, so monitoring all subscribers would not always 'fit'.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> A few months back I had ventured into end-device monitoring for ATA's and while it was just an OPTIONS ping and email, it became a PIA receiving 100's of emails when ppl simply moved the device to another room or took it with them on a plane for example. Also I really wanted to have more info on the device since I was already communicating with it regularly; such as calculating the MOS score. That turned out to be near impossible so I just dropped the whole idea and moved on with placing the responsibility onto the PBX rather than SPCE.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> What about creating a 'Monitor Subscriber' as an option for each subscriber with an email address field to notify? I could see this working as then you could enter the subscriber's email and they are notified that "Hey, Your device is not working. Check that it is plugged to the Internet." or something like that. Put the responsibility onto the person that can 'touch' the device.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Skyler</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> </p></div></div></div></body></html>