Gigaset "server not available" problem

["Pet @ www.gymratz.co.uk ;¬)"]

Hi folks,
This one has got me confused.
Gigaset at home has been working just fine for a few years. Been on FTTC
via Zen for about a year with no problems, then about Sunday/Monday I
got a call at work from Debs mobile saying the phones weren't working.
Hmmm. Logged on to the box over VPN and checked all settings. All seemed
fine well they should have been as I hadn't touched anything.
Pretty sure I hadn't fiddled with the router (Draytek 2920n on the
weekend either) The gigaset box has web access as it's got the weather
on the display plus I can log into it from local and VPN.

So I disabled all firewall rules on router, disabled all DoS rules. even
changed DNS from open DNS to ZEN's DNS as I have known Open DNS'
clueless (upaid) clasifiers classify VOIPfone server as a "webmail"
server which knocked it out once before. Still no joy. No accounts are
registering. Voipfone, several betamax accounts and a couple of sipgate
accounts.

This is really got me stumped. I've disconnected all voip accounts and
tried enabling them individually but they all still refuse to register.

Only thing left to try is temporarily setting gigaset box as DMZ to
completely eliminate any router rules.. After that I'm snookered.

Any other ideas?
Cheers
Pete

[Graham.]

Have you tried switching it off and back on again ;-) ?

--
Graham.
%Profound_observation%

["Pet @ www.gymratz.co.uk ;¬)"]

On 28/11/2012 22:53, Graham. wrote:

> Have you tried switching it off and back on again ;-) ?

Ha... Quite a number of times, along with the router and the Modem.
My NAS drive vanished for a few days but that's decided to stop sulking
and come out to play which did make me query the switch in the loft
however the Giggleset box is in it's own port on the router, everything
else goes back to the switch.
Results of the Gigaset box on DMZ are same. All accounts showing server
not accessible.

It could only be a port issue as the box has internet and LAN access.
Dropping all Firewall rules and also setting in DMZ have pretty much
eliminated port blocking from my side, all I can think is Zen are
blocking ports (which I've set away from default) as per:
https://gigaset.com/medias/sys_master/VoIP_nat-troubleshooting_en.html
which has been working fine both here and at work.

The only other query is that I'm pretty tight on D/L limits this month
though when I checked a few days ago I still had 6% left which is more
than enough...

Guess I'll have to call them in the morning and see if they're messing
with me.

8ｬ/

Pete

[Graham.]

>8Č/
>
>Pete
>

Try the account credentials on a generic soft phone like x-lite, or
the Betamax softphone that corresponds to your accounts.

If that's the same have you got a 3G dongle or phone you can tether to
bypass your ISP as a test?

You really need an all-you-can-eat plan Pete!

--
Graham.
%Profound_observation%

[alexd]

Pet @ www.gymratz.co.uk ;¬) (for it is he) wrote:

> Any other ideas?

Short of anything else, I would save the config from the Gigaset, factory
it and set it up from scratch. Or maybe factory it and reupload the config
first.

If you've got a separate modem and router, then perhaps it would be possible
to put your Gigaset in place of your router with your router's public IP for
testing purposes, potentially eliminating the router from your enquiries.

Something I might try if my time were free, is to do a packet capture of
what the Gigaset is doing and hope that the problem would be revealed there.

--
<http://ale.cx/> (AIM:troffasky) (UnSoEs...@ale.cx)
08:18:42 up 1 day, 6 min, 4 users, load average: 0.42, 0.70, 0.77
Qua illic est reprehendit, illic est a vindicatum

["Pet @ www.gymratz.co.uk ;¬)"]

On 28/11/2012 23:59, Graham. wrote:

> Try the account credentials on a generic soft phone like x-lite, or
> the Betamax softphone that corresponds to your accounts.

Betamax softphone works on my computer so I guess that partialy rules
out ISP though the softphone isn't running the non-standard ports of the
gigaset box.

> If that's the same have you got a 3G dongle or phone you can tether to
> bypass your ISP as a test?


> You really need an all-you-can-eat plan Pete!

100GB/month is normally more than ample Graham. I only typically use
about 50% so 6% left to cover to the end of the month is an abundance.
:ｬ)
So I'm now thinking I have 2 more options. First being that I simply
unplug the box and take it to work today where I can plug it in in place
of the gigaset box there and see if it comes to life (remembering to set
the correct IP address etc first) or do a factory reset (if that's
possible) and re-set it all up again.

2 essential things missing from the device. The ability to re-boot the
box from web interface and the ability to back-up and restore settings.

:ｬ(

Pete @
--
http://www.gymratz.co.uk/waterrower/
"I call her Bronwyn"

["Pet @ www.gymratz.co.uk ;¬)"]

On 29/11/2012 04:47, Anthony R. Gold wrote:

> What firmware is the Debs 2920 running? My Gigaset N300A IP worked fine
> while my Vigor 2920 ran firmware version 3.3.7.1 but VOIP registrations
> became flakey and intermittent after I upgraded it to 3.6.0 so I wound it
> back to 3.3.7.1 where it contentedly still remains. I don't believe I ever
> tried v3.6.1 because its release notes did not mention anything about VOIP
> issues or fixes.

Thanks Anthony,
I did indeed upgrade the firmware a while back to 3.6.1
I'm pretty sure I have a copy of the previous firmware somewhere.
I'll try that as a first option later tonight.

Thanks for the suggestion.
I'll let you know how it goes.

Cheers
Pete

[www.GymRatZ.co.uk]

On 29/11/2012 12:53, Anthony R. Gold wrote:
> On Thu, 29 Nov 2012 07:37:48 -0500, "Anthony R. Gold"
> <not-fo...@ahjg.co.uk> wrote:
>
>> I'll be happy to email you Vigor2920_v3.3.6.1.zip if that helps and if your
>> email service will allow a message of 9MB + encoding overhead.
>
> Oops, make that Vigor2920_v3.3.7.1.zip and 9.5MB + overhead. My archives go
> back to 3.3.2.3.

Thanks Anthony.
I wound it back a version 3371 just before I left home. Though a quick
re-boot of everything didn't see any greater joy.

Just logged in from work over VPN and it's still showing "server not
accessible" for all accounts.

Hey ho. I'll continue to twiddle and fiddle. I'm sure I've got an older
config back-up file I can roll the router back to when I know it was
working 100% Will do that tonight

Thanks all for input so-far. I bet I've just done something really
stupid on the weekend and forgotten about it though. Time will tell...
:¬)

--
http://www.GymRatZ.co.uk - Fitness+Gym Equipment.
http://www.bodysolid-gym-equipment.co.uk
http://www.trade-price-supplements.co.uk
http://www.water-rower.co.uk

[Nick]

On 28/11/2012 22:31, "Pet @ www.gymratz.co.uk ;�)" wrote:

> Only thing left to try is temporarily setting gigaset box as DMZ to
> completely eliminate any router rules.. After that I'm snookered.
>

On a GigaSet when the phone says "Server not available" it normally
refers to the info services that allow it to display the temperature etc
when the phone isn't being used. It isn't anything to do with the voip
registrations which could still be working fine.

[www.GymRatZ.co.uk]

On 29/11/2012 16:44, Nick wrote:

> On a GigaSet when the phone says "Server not available" it normally
> refers to the info services that allow it to display the temperature etc
> when the phone isn't being used. It isn't anything to do with the voip
> registrations which could still be working fine.

That's the weird thing Nick.
It's pulling up the info services just fine.
The message we sometimes see is "services not currently available" or
something with the same message repeated in German underneath.

I'm getting the message on the accounts page:
http://172.16.1.200/settings_telephony_voip_multi.html
"Server not accessible"
In fact I thought this used to say "account not registered" but I may be
thinking of the 2910vg when I used it before the Gigaset boxes.

[www.GymRatZ.co.uk]

On 29/11/2012 17:02, www.GymRatZ.co.uk wrote:

> I'm getting the message on the accounts page:
> http://172.16.1.200/settings_telephony_voip_multi.html
> "Server not accessible"

Just to clarify, not the web server of the box but where the individual
voip accounts normally say "Registered" or "Registration failed"

which is why I initially thought DNS issue not looking the registrar server.

Ha... just changed a "registration failed" sipgate account (not really
used) on my shop box from sipgate.de to sipgate.co.uk and the "Server
not accessible" message comes up.

["Pet @ www.gymratz.co.uk ;¬)"]

On 28/11/2012 22:31, "Pet @ www.gymratz.co.uk ;�)" wrote:

> Hi folks,
> This one has got me confused.

Update: Last thing Thursday eve. I got it working again.
One thing added to possible errors in earlier problem solving which was
the plug (under the desk in a wire tray with another 8 plugs/adaptors)
which I thought was the gigaset plug was actually the router plug. So I
thought I was re-booting the router because the blue light was going off
when the plug was removed but in fact it went off because the router was
powered down, which I didn't notice as I was under the desk.

So, the combination of rolling back firmware in router, rolling back
router config to one saved before firmware update and double checking
modem, router AND Gigaset box were all powered down, saw all accounts
bounce back to former health.

I think I'm going to leave the blame on the "IPV6" draytek 2920n
firmware which obviously dabbles with VOIP as it has an extra box in QOS
settings just for VOIP as highest priority, in the previous firmware one
had to set this up manually.

But it's now working again and I thank you all for your help. Much
appreciated.
Cheers - Pete

["Pet @ www.gymratz.co.uk ;¬)"]

On 23/12/2012 19:01, Anthony R. Gold wrote:
> On Thu, 29 Nov 2012 13:41:21 +0000, "www.GymRatZ.co.uk"

> I see Draytek has deployed firmware v3.6.3 for the Vigor 2920. I'm around
> 5,000 miles from my London 2920 and so won't be able to try it for a few
> weeks, but it certainly sounds worthwhile testing.

Ah... There's a huge list of things that have been "corrected"
I'll give it a go shortly and see if the phone keeps working as it should.

Cheers
Pete
--
http://www.facebook.com/Gym.Equipment.uk
"Like" us to win £50 ........... Not!

[www.GymRatZ.co.uk]

On 28/12/2012 18:13, "Pet @ www.gymratz.co.uk ;Ź)" wrote:

> Ah... There's a huge list of things that have been "corrected"
> I'll give it a go shortly and see if the phone keeps working as it should.

It's been running now for nearly 5 days an so far the phones are still
registering and working fine. Even the QOS seems to be working as it
should. Time will tell though.

["Pet @ www.gymratz.co.uk ;¬)"]

On 20/01/2013 12:11, Anthony R. Gold wrote:
> On Sat, 19 Jan 2013 18:35:45 +0000, "Anthony R. Gold"
> <not-fo...@ahjg.co.uk> wrote:
>
>> I upgraded my Vigor 2920 to v3.6.3 and found failures in all the VOIP
>> provider registrations. I then opened the 2920 on both its WANs for incoming
>> UDP:5060 directed towards the LAN address of my Gigaset N300A IP and now all
>> appears to be well.
>
> v3.6.3 proved not to be well and the Gigaset's SIP registrations not stable.
> So I've wound the Vigor 2920 back to v3.3.7.1 which is totally reliable.

Just double checked my gigaset box.
5 out of 6 accounts are registered. Sipgate, voipfone, smslisto,
voipcheap.co.uk, smartvoip. Even gigaset.net is working. The only one
that doesn't register is one I played with a long time ago and it didn't
work on old firmware UKDD
No problem calling in or out so it's good for me. Thanks for feedback
Anthony.

Cheers
Pete

[www.GymRatZ.co.uk]

On 21/01/2013 12:12, Anthony R. Gold wrote:

> From time to time all the providers did register, but it was just not
> sufficiently reliable - I am 100% dependent on VOIP for all this property's
> incoming calls.
>
> Did you make any particular configuration adjustments?
>
> Under QoS I had checked the box to give priority to VOIP and I also opened
> the router towards the Gigaset for incoming UDP:5060 just in case some
> router glitch caused incoming packets to be unmatched to correct sessions.
> Is there any settings that you find useful, Pete?

I have/had non-standard ports set up.
Today's update.... I've been trying to call home and it appears home is
not working as it should :¬( even though all accounts are registered
correctly.

The main benefit for me was the QoS appeared to be working more reliably
but I'm going to have to do a bit more experimenting now to see if it's
the router giving problems... at least I know that there's a chance it
could still be dodgy firmware messing about..

Thanks for the heads up Anthony.

Pete