Continual Registration Failures

#1
Phone - SNOM 360

Using NAT proxy.

I have been having continual registration problems today. Rebooting the phone sorts this out, but it is on and off continually - and then de-registers completely. However I can make calls while the phone isn't registered - although I can't receive calls.

Every time I reboot the phone it's OK again.

Any Ideas Support?

Paul

#2
Please try removing the outbound proxy and ensure that you have support broken register switched on.

You may also find that you will experience registration problems if your using the version 5 firmwares we currently recommend that you use version 4.5
Regards,

Voipfone Customer Services

iNet Telecoms Ltd (Voipfone)
Sovereign House
227 Marsh Wall
London
E14 9SD
United Kingdom

Registered number: 05168033
Vat Registration Number 858850966

Telephone: 020 7043 5555
Fax: 020 7043 5556

Web: http://www.voipfone.co.uk
Blog: http://www.voipfoneblog.co.uk
Forum: http://www.voipfoneuserforum.co.uk
Twitter: http://www.twitter.com/voipfone

#3
I have tried removing the NAT proxy - registered for a short time and the de-registered.

I have not had broken registrar on before - has the need to have this turned on changed?

Paul

Continual Registration Failures

#4
I think I have the same problem... My phone randomly deregisters from Voipfone and remains deregistered for some time. If the phone is reset it registers to Voipfone straight away. If I just leave it then it usually registers again some time later.

I have a Grandstream GXP2000 firmware 1.0.1.9 via NAT firewall with no proxy.

Today I ran an Ethereal packet trace to see what's happening. At approximately 11:53 (22 Apr 06 UK time) I saw the following packets:

Time offset Source Destination Protocol Info
1244.507208 192.168.10.137 212.187.162.178 SIP Request: REGISTER sip:voipfone.co.uk
1244.549623 212.187.162.178 192.168.10.137 SIP Status: 100 Trying (1 bindings)
1245.526303 192.168.10.137 212.187.162.178 SIP Request: REGISTER sip:voipfone.co.uk
1245.569831 212.187.162.178 192.168.10.137 SIP Status: 100 Trying (1 bindings)
1245.574303 212.187.162.178 192.168.10.137 SIP Status: 403 Forbidden (1 bindings)


So the problem is that suddenly Voipfone refuse my registration with a SIP Forbidden message. Following this the phone made no further attempts to register for about an hour. Then it registered normally again.

So please Voipfone, tell me what's going on ? Can you see anything in your logs ? It's nothing to do with DNS or problems with using a proxy (both being possible problems you told other people to look for). The phone had been registering normally once every minute without being used so there was no problem with username or password being incorrect. I imagine the one hour wait before trying to register again is a mechanism to prevent incorrectly configured phones from generating excess traffic.

Re: Continual Registration Failures

#5
thing wrote:I think I have the same problem... My phone randomly deregisters from Voipfone and remains deregistered for some time. If the phone is reset it registers to Voipfone straight away. If I just leave it then it usually registers again some time later.

I have a Grandstream GXP2000 firmware 1.0.1.9 via NAT firewall with no proxy.
Please see the following posts as they should help you to solve your problems http://www.voipfoneuserforum.com/viewto ... =2377#2377
Regards,

Voipfone Customer Services

iNet Telecoms Ltd (Voipfone)
Sovereign House
227 Marsh Wall
London
E14 9SD
United Kingdom

Registered number: 05168033
Vat Registration Number 858850966

Telephone: 020 7043 5555
Fax: 020 7043 5556

Web: http://www.voipfone.co.uk
Blog: http://www.voipfoneblog.co.uk
Forum: http://www.voipfoneuserforum.co.uk
Twitter: http://www.twitter.com/voipfone

#6
I'm aware there are specific techinical problems with the Grandstream that are cured in the later firmware and I see those problems when using other phone service providers.

Note that paulobrien is using a Snom 360 without proxy and has this problem too.

Looking around the forum there seem to be other people with a similar problem and not being to track it down. They say this is only a problem with Voipfone and I can confirm that. I don't see this registration prohibited message with other providers.

I'm willing to help track this down further but I need your help to check logs etc and tell me why the registration was refused. Even if it's a Grandstream fault we need to fully understand it rather than upgrading firmware and hoping it will go away.

#7
I have always had this problem with all three of my Snom 360's using various different firmware from Snom, although it has been alot better recently.

#8
greyt wrote:I have always had this problem with all three of my Snom 360's using various different firmware from Snom, although it has been alot better recently.
Hello greyt.... can you tell us if you saw the 403 Forbidden message ? Otherwise can you trace some packets to check for it ?

Sometimes it's a lot better for me too but the problem never seems to go away permanently.

#10
greyt wrote:I have always had this problem with all three of my Snom 360's using various different firmware from Snom, although it has been alot better recently.
We use the Snom 360's here with firmware version 4.5

Registrar voipfone.co.uk
Registration expiry set to 60 seconds
no Nat proxy
support broken registrar set you yes

And we have not seen any problems since our network problems were resolved a few weeks ago

can you confirm the settings in your snom 360 please
Regards,

Voipfone Customer Services

iNet Telecoms Ltd (Voipfone)
Sovereign House
227 Marsh Wall
London
E14 9SD
United Kingdom

Registered number: 05168033
Vat Registration Number 858850966

Telephone: 020 7043 5555
Fax: 020 7043 5556

Web: http://www.voipfone.co.uk
Blog: http://www.voipfoneblog.co.uk
Forum: http://www.voipfoneuserforum.co.uk
Twitter: http://www.twitter.com/voipfone

#11
I have now collected a lot of data about this problem. After some analysis and reading the SIP specifications (RFC 2617 and RFC 3261) I believe that the Voipfone registrar is not working as it should.

Here's why... The problem occurs when the Grandstream GXP2000 phone attempts a registration update and doesn't get the expected "SIP 401 Unauthorized" message. The phone resends the register request after 1 second. It is this double request that triggers the production of the "SIP 403 Forbidden" message. The phone then waits one hour before retrying.

I can't say why the Voipfone registrar does this and we don't know if the "401 unauthorized" packet was or wasn't sent or if it was lost by the ISP or even my router. That doesn't matter as packet loss in IP networks is an expected hazard commonly dealt with by resending after a timeout interval. What seems unreasonable then is that the registrar behaves differently in a situation where a registration request had to be resent.

The normal expected and required behaviour would be a "401 Unauthorized" packet advertising a new nonce value to replace the stale one which can no longer be used for authentication. Instead, the "403 Forbidden" message doesn't contain a new nonce so is not a suitable way of rejecting the stale nonce.

I found a similar Bugzilla report for one particular SIP package:
http://bugzilla.vovida.org/bugzilla/show_bug.cgi?id=605
The case was similar in that they felt that 401 Unauthorized should have been used instead of 403 Forbidden.

I noted that this problem seems to be client specific so I ran the same test with X-Lite to see what happens. One difference seems to be that X-Lite initiates all registration updates without any authentication header so there are no credentials (nonce etc) to reject although his may not be the only difference. The fact remains that the Grandstream way of doing things is reasonable and within the limits of the specifications. Just because one client works and Grandstream does not is insufficient evidence to point at Grandstream and say that it's broken.

I'm still not prepared to replace my Grandstream firmware with a later beta release just because it has been suggested that the later firmware gets round the issue. There is currently no way to revert back to the full release firmware from the beta on the Grandstream so I'm not going to take that risk. Anyway I don't believe Grandstream is at fault here.

Voipfone... please look into this seriously. You have customers relying on your network to run businesses and they want to see a stable and professionally run network.

403 Forbidden

#13
I have a SIPURA 3000 which has been working perfectly with Vopifone until a couple of days ago when the same "403 - forbidden" started occuring.

There have been no firmware or setting changes to the Sipura. The same 403 error is reported by eyeBeam.

If I change the provider to Voiptalk or SipDiscount I do not get this problem - which implies to me that the cause lies with the voipfone servers.

I have had to divert my voipfone to my voiptalk account because I can not afford to miss any phone calls - I dont see why I should have to pay for this when the fault seems to be with voipfone.

#14
Please read and follow this; if the problem persists email support and we'll look into it for you.

http://www.voipfoneuserforum.com/viewto ... =3032#3032
Regards,

Voipfone Customer Services

iNet Telecoms Ltd (Voipfone)
Sovereign House
227 Marsh Wall
London
E14 9SD
United Kingdom

Registered number: 05168033
Vat Registration Number 858850966

Telephone: 020 7043 5555
Fax: 020 7043 5556

Web: http://www.voipfone.co.uk
Blog: http://www.voipfoneblog.co.uk
Forum: http://www.voipfoneuserforum.co.uk
Twitter: http://www.twitter.com/voipfone

Who is online

Users browsing this forum: No registered users and 0 guests

Copyright 2004 - 2017, iNet Telecoms® Ltd. All rights reserved.


cron