Handset wont register

[Iain]

I have a Gigaset A540H handset and a Gigaset N300 IP base station. Been
working perfectly for over 2 years until last weekend when we had an
electrical storm and power failure. Now the handset wont register with
the base station.
I've tried going through the registration process repeatedly with no
success.
Anyone got suggestions on how to resolve this issue.

TIA Iain

[Chris Green]

Have you tried a reset of the handset? There's a menu option to do
this (if it's like our Gigasets). Strangely the base station doesn't
seem to have the ability to reset.

--
Chris Green
·

[Chris Green]

You can also reset the base station, basically power up while holding
the blue button down, had to search for that! :-)

--
Chris Green
·

[notya...@gmail.com]

The N300 IP is the only Gigaset base station I have not used, but the thunderstorm is more likely to have confused that than the handset. Reset as suggested. You will have to reconfigure from scratch.

[Iain]

On 06/07/2021 11:57, Chris Green wrote:
I've just tried both of your suggestions Chris, but no joy.

Iain

[Iain]

On 06/07/2021 12:16, notya...@gmail.com wrote:


>> ·
> The N300 IP is the only Gigaset base station I have not used, but the thunderstorm is more likely to have confused that than the handset. Reset as suggested. You will have to reconfigure from scratch.
>

Tried that. Powered off for 30 seconds, powered on whilst holding down
the button. Original configuration was unchanged. Still no joy

Iain

[Iain]

On 06/07/2021 12:56, Anthony R. Gold wrote:

>
> First, can you reach the N300's web setting page via your LAN? If not and if
> you had a phone line plugged in at the time the device may have been toasted
> by a nearby lightening strike.
>
> But if the N300 is not dead and just sulking I suggest performing factory
> resets to both base and handset. You can first backup the base's settings to
> a file but without a base connection you will lose your handset's saved
> directory entries.
>

Yes I can reach the web setting page. There is no landline connected.
I have returned handset to factory settings.
I have powered down the N300, left it for 30 seconds or so, then held
down the button and powered on again. None of the settings had been
changed on power up.

I can still use the allocated VOIP number on my Snom 300 desk phone.

Iain

[Iain]

On 06/07/2021 14:50, Anthony R. Gold wrote:
>
> After making a backup of the settings do the reset from the admin screen in
> Settings / Management / Reboot & Reset / Factory Settings / Start Factory
> Reset. And you can then also start the base registration process from nearby
> in Management / Miscellaneous.
>
>>

Tried that. Did not make any difference.
Tried registering handset from base station as above. Got a box saying
"Register from handset", or words to that effect.
I'm about ready to throw this thing out the window.

Iain

[notya...@gmail.com]

Take the batteries out of the handset for a minute or two, replace and try again.

Is the base station registering on the network - what do you get if you ring from your mobile (unplug any other phone).

[Iain]

The N300 number is a second line on my Snom 300 desk phone. I
disconnected my desk phone then rang the N300 IP from my mobile phone
and got nothing. On reconnecting the Snom I was able to ring the N300
from my mobile.
So I think either the N300 is not registered with the VOIP server or it
is totally borked.
Looking on the N300 status page it shows that the last sincronization
was at 03:09 this morning.

I am totally confused now.

Iain

[notya...@gmail.com]

If you look on the telephony page it should show whether it is registered or not, although sometimes there is a lag.

[Iain]

On 07/07/2021 11:15, notya...@gmail.com wrote:

>
> If you look on the telephony page it should show whether it is registered or not, although sometimes there is a lag.
>

Yes, it is registered to the correct VOIP server.
When attempting to register the handset the handset indicates that a
successful data transfer occurred although there is no data on the
handset. Then it indicates registration failed.

Iain

[David Woolley]

I don't recall seeing, anywhere in the thread, what you have done to
verify that the phone or base station DECT transceivers are working.
I'd expect at least a test with a known working phone and and an attempt
to register to someone else's base station. GAP devices should
interwork with other GAP device at that level.

[Iain]

On 07/07/2021 11:15, notya...@gmail.com
>

> If you look on the telephony page it should show whether it is registered or not, although sometimes there is a lag.
>

Just noticed that the Handset is identifying as INT2 but base station is
set for INT1. How do I set the handset to INT1 ?

Iain

[Iain]

On 06/07/2021 10:14, Iain wrote:

Thanks to everyone who tried to help. I've now got the handset
registered but still can't make or receive calls on it, so it looks like
the base station is truly borked.

Iain

[notya...@gmail.com]

If the handset is registered to the base and the base has registered on your Voip server then you need to enable calls to and from the handset.

On that basis there is no permanent electrical damage, but you need to sort out configuration.

You can also name handsets - ours are called "lounge", "kitchen", "study" etc.

[Iain]

I think the handset is trying to access the non-existant land line.
I can't see how to force it to use VOIP.

The landline (Fixed Line)entry on the base station is definately shown
as Disconnected.

Iain

[Roger Barrett]

Settings ->Telephony->number assignment is where you tell which handset
which VOIP service (of the 6 you can configure) to use for both incoming
and outgoing calls . Then scroll down and amake sure automatic fallback
to fixed line is set to "no"

[Iain]

On 08/07/2021 21:15, Roger Barrett wrote:



>>
> Settings ->Telephony->number assignment is where you tell which handset
> which VOIP service (of the 6 you can configure) to use for both incoming
> and outgoing calls . Then scroll down and amake sure automatic fallback
> to fixed line is set to "no"

Thank you Roger, problem is now solved and a backup of settings made.

Iain