Re: Paging might be broken again today?

What happened on the 21st (I think ?) is that pager RICs that aren't 
fire/ambos/hospitals have been deleted from the system - they're now 
returning the error "Record not found for ID: 2583495"  (that's not a 
real number).  This may have been done as part of the steps of the 
handover to FENZ (Fire Emergency NZ).   Sending messages to fire service 
RICs are successful, *if* you manage to get a modem that actually 
answers the phone.

The paging software that I'm using treats this message as a recoverable 
error, and so it requeues the message and retries.  I suspect that other 
email/web paging services are doing the same, and that the modem banks 
that answer the calls to 026 400 1283 are therefore getting overloaded 
with retries, and only the dead modems - the ones that pick up but don't 
give a modem tone (which have been broken for ages, but were worked 
around by calling back and getting another modem) are now getting the 
majority of calls since they disconnect more quickly, making them more 
available than the ones tied up doing retries.

This is of course just a theory, based on my observations.




On 24/07/2017 16:14, David Maclagan wrote:
> On 2017-07-24 15:32, Michael Fincham wrote:
>> On Thu, 20 Jul 2017 19:01:49 +1200, Ian Batterbee 
>> <[email protected]> wrote:
>>> Does anyone here look after, or know who looks after, the 026 400 1283
>>> modem interface to spark paging ?
>>>
>>> It's currently answering calls, but not giving a modem handshake.
>>
>> We're getting modemy sounding noises today but NO CARRIER :(
>>
>> Anyone know what's up? Spark has not been helpful so far.
>
> Talking to a firie contact, they're under the impression that the 
> platform's been EoLed for everyone other than the firies. So that 
> could be the issue?
>
> Cheers
> David
> _______________________________________________
> NZNOG mailing list
> [email protected]
> https://list.waikato.ac.nz/mailman/listinfo/nznog