Bruce,

The issue was caused by a hardware failure on the SIP-06 server
earlier today that resulted in the drives on the system going into
read only mode.  This read-only mode caused issues processing calls
and SIP registrations.  Around 10:20 AM the issue was resolved and
service resumed.  We will be doing further maintenance tomorrow
morning (2AM-4AM) to find the root cause of the failure and replace
any necessary hardware to ensure this doesn't happen again.

If you have any further questions, please don't hesitate to ask.

Matthew M. Gamble
Team Manager, Service Platform Engineering
Primus Telecommunications Canada

On Thu, Jul 14, 2011 at 1:27 PM, Bruce N <[email protected]> wrote:
>
> My clients complained as well. I would like to hear about this as well.
> -Bruce
>
>> Date: Thu, 14 Jul 2011 10:51:40 -0400
>> From: [email protected]
>> To: [email protected]
>> Subject: Fwd: [on-asterisk] Unlimitel issues
>>
>> Me too, my all my SIP06 trunks at Unlimitel couldn't register but  they came
>> back up at 10.33am
>> At the time I thought it was my router so I rebooted and concluded that was
>> the problem. But if you had the same problem then it must have been
>> Unlimitel .
>> I hope we get an explanation from Stephan.
>> Henry
>>
>> ---------- Forwarded message ----------
>> From: Sean Healy <[email protected]>
>> Date: Thu, Jul 14, 2011 at 10:22 AM
>> Subject: [on-asterisk] Unlimitel issues
>> To: "[email protected]" <[email protected]>
>>
>>
>> We're having trouble connecting to sip06 at Unlimitel this morning,
>> since about 8:30am - does anyone know what's up?
>>
>> Seems their other servers are OK, just the numbers on sip06 aren't
>> registering.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>>
>> --
>> * Henry Coleman*
>> [image: Picture]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to