Gigaset N300 IP

A friend has said that every time he checks the 'Uptime since:' value on the status>device page of his Gigaset N300 IP it always shows a date\time that is less than 24 hours ago. Can anyone with the same device check theirs and confirm if this is the case for you, for interest he is running firmware version 42.250 (which I believe is the latest) and wants to find out if his device is frequently rebooting or if its a bug with its 'uptime since:'

Mine is running 42.254. The Uptime Since shows 09:49 this morning.

I don't believe it is rebooting as one of the four VOIP connections would show an error and I have not noticed any.

AFAIK there has been a bug in the firmware for some time. You'll probably see the uptime change to the current time every 18h 12m 15s which equals 65535 seconds, the max size of a 32-bit short integer. I guess someone defined the variable incorrectly in one of the updates.

Does it on my GO 100 box too.

In reply to a post by adrenalize_:

Does it on my GO 100 box too.

the GO 100 is just a "renamed" N300IP, as are the GO850, GO430, GO630 ...

In reply to a post by adrenalize_:

You'll probably see the uptime change to the current time every 18h 12m 15s which equals 65535 seconds,

Thanks, that makes sense as he told me it was never more than a little over 18 hours, so that tallies with what you said.

In reply to a post by MHC:

I don't believe it is rebooting as one of the four VOIP connections would show an error and I have not noticed any.

He is convince something is happening as he said a few random times (not always) he has received a VOIP call and when he has tried to answer it the handset has shown the 'No Base' message and when he checked the 'Uptime since:' field it shows the time and date the call was received. That lead to the question about the 'Uptime since:' field never being more than 24 hours old which now seems like a red herring although its strange that the 'Uptime since:' field would be exactly the same time as the failed incoming VOIP call.

Checked mine again and it has now been up since 04:02 today ... 5h34 short of a day or 18h 13 since the previous value which almost ties in with the other comment.


No call was received at that time - phone by the bed.

Edited by MHC (Wed 29-Apr-20 11:32:16)

Mine rebooted at around 2:18 this morning.

The one by the bed, I tend to use as a clock as it is the easiest to see. I had a shock at 6:30 this morning when it was telling me it was 10:40.

When I checked the status just now at 09:20 it was saying:

Time 13:30
Date: 07.02.2036
Last sync 07.02.2036 06:28
Optime since: 07.02.2036 06:27

A minor sync glitch or I have been asleep rather a long time.

In reply to a post by MHC:

Date: 07.02.2036
Last sync 07.02.2036 06:28
Uptime since: 07.02.2036 06:27

Wow, it did take me 3 attempts at reading your message before I spotted the month and year

Do you use the standard sync source?

Standard source, and all I did was change time zone to UTC+1, <Set> back to UTC+0 <Set> and all was fine.