I needed to switch mine off last Saturday and did get a correct notification.

I've not had any false positives for a while now...
As Xp says

Rich,
It would be nice to get some sort of info from Gradwell as to whether they think they have actually done something to fix it and not that it has just gone away ...

I believe they've moved everyone to the new nat proxy but i'm awaiting confirmation of that.

ok, so the problem is solved if your using natproxy.plus.net - nat.plus.net will still point to the old proxies until we do some ANAME changes which i'll plan for the new year.

Rich
Thank you for helping.

Ok....

How about this for timing!!! 40mins ago I got this:-

The SIP ID 68***** which has been connected since 2008-11-26 13:23:45, went offline at 2008-12-22 16:28:59

Connected nearly a month without problems, then a false positive out of the blue. I am still using the old "nat.plus.net" proxy, with sip.plus.net.
I'm still not sure about the whether the reporting is working correctly with genuine drop-outs. I will try that later tonight or tomorrow night when I am happy to take my SIP client offline for a few hours.

Mike

Rich,


and what about those of us who dont use either proxy ?

Rich,

Does your post mean that users of natproxy.plus.net won't have got the false positive I got this afternoon? And that if I change myself over to natproxy.plus.net, then I now won't get false positives any more?

Did anyone else get the false positive this afternoon? Can you post here whether you got it or not, and what proxy & sip servers combination you are you using?
(Of course it might have been a local glitch here or something odd with just my account. It'd interesting to see the wider picture.)

Can others test to see if they are getting genuine offline messages when their sip system is turned off... and again report which nat & sip combination you are using.

Thanks

Mike

I am set to natproxy.plus.net and did not get the false alert this afternoon.

Mike,


'fraid I won't know until tomorrow as up until now ( see below ) my notifications went to my office address.


I've changed my email ( I Think! ) on my voip account so I will try turning my C475 off now, its due to expire at 18:12 so will post results later...

I also am set to natproxy.plus.net and did not get the false alert this afternoon.

Is there anyone still on nat.plus.net .... and if so did you get a offline notification this afternoon?

(of course it might have just been me... not that I'm aware of any interruption to my router... but I'll check the logs to be sure).

Mike

Mike/Rich,

Well I deregistered  my C475 , voip account control panel shows offline since 18:12 , its now 18:32 and still no offline notification email!!!

I've got to turn it on again now as I use it...
Will check my office email tomorrow and post   

Well, what do you know.... I take it all back.... I looked in my router logs and found this lot:-

Dec 22 14:27:21 home.gateway:sip_SipTransactionManager_?:none: SIP Registration successful for phone 68*****
Dec 22 16:22:19 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:23:22 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:23:54 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:24:56 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:25:28 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:26:30 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:27:02 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:28:04 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:28:37 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:29:39 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:30:11 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:31:13 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:31:45 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:32:47 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:33:19 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:34:21 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:34:53 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:35:55 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:36:28 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:37:30 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:38:02 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:39:04 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:39:36 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:40:38 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:41:10 home.gateway:sip_SipTransactionManager_?:none: SIP Registration Error 1 for phone 68*****
Dec 22 16:41:31 home.gateway:sip_SipTransactionManager_?:none: SIP Registration successful for phone 68*****
Dec 22 16:41:31 home.gateway:sip_SipTransactionManager_?:none: SIP Registration successful for phone 68*****
Dec 22 18:35:34 home.gateway:sip_SipTransactionManager_?:none: SIP Registration successful for phone 68*****

My registration interval is 7200secs (eg 2 hours) and there was 20 min period where the client was refusing to register. I'm not aware of having seen that before (I periodically scan my logs for anomalies), and my other sip client (on other port of the same router with a different VOIP provider) worked right through fine without any errors.

I was planning on reducing my registration time right down to 5 mins or so (once the platform had stabilised again - with offline notifications working properly again). Maybe now is the time to try that reduction... since the email clearly did warn me of a genuine outage!!! (Oh how little faith I had in the warnings, to instantly assume it was a glitch in the reporting!).

Still a bit mysterious as to why my sip client refused to register for those 20 mins, when I clearly still had net access. Maybe there was a problem with nat.plus.net ... who knows!

I'll still try a manual test of turning my sip clients off this evening, to check it again. Hopefully it'll give me another offline notification email. I'll then move myself over to natproxy.plus.net at the same time (whilst offline) and drop my re-registration interval to 300 secs (5mins).

It is starting to look like this has finally been fixed properly! I'll report back tomorrow.

Mike

Well, mixed results here I'm sorry to say

I got 2 offline mails yesterday , both to my office address ( maybe the system hadn't had time to spot the email change on my account for the second one).

The first one I believe is spurious , and note the 'identified as n/a' , odd since my C475 has been the only sip device registered for some while!!!. The second is a correct notification when I deregistered my C475 as a test.

So Rich, close, but no cigar I'm afraid...

BTW I'm using sip.plus.net as the registrar and do not use any outbound proxy.

That's odd. I was wondering if your 4pm one could be related to mine... but there is no overlap in the timings... yours failed around 16:07:04 and was back online by 16:17:58, whereas mine failed at 16:22:19 and kept failing until 16:41:31. Still mystified as to my outage...

Anyway, my tests last night where mostly positive. I managed to get  correct message when I took my system down. I have updated the registration interval to 300 secs and updated the proxy to natproxy.plus.net

I then conducted another test of taking the system down a while later that also worked.

However in the middle of all the updating I got no report, despite having re-registered in between and left it on for a short while. It could be that the emails are set to not send again within a certain time interval to stop you getting lots of emails if the system is flaky... maybe only sending one per hour or something. That would certainly explain what I saw (or didn't see) last night.

So it looks like good news from me. Both nat & natproxy are correctly reporting now. I haven't had a false positive since late November. I still have the odd outage yesterday, which might have been a glitch with Gradwell's servers.... I would be concerned if I saw it happen again.