Start a new topic
Solved

Intermittant registration failed

 Hi there!


I have recently moved to FreshPhone and ported our Telkom number over. I'm using a Gigaset A540IP and D-Link DIR-825 router with Vumatel Fiber connection and Afrihost as the ISP.


I followed the set up instructions for the A540IP and it is able to register and make calls and appears to be working normally but sometimes when I check again the A540IP reports that "Registration has failed". It is unpredictable and unreliable: it appears to be fine for a while and the suddenly it loses registration :( I can't go and check each morning if it is still registered.


Any help is much appreciated!


Thanks in advance,

Pieter


P.S. When I cycle the A540IP's power then it registers again.

Hi Pieter,


If the account is not holding the registration it means the internet connection is not keeping the registration alive. I will advise you to ask your ISP to make traffic going to the Freshphone server address to set it as priority on your internet line. 

Hi!


Thanks for the reply. My problem is that I do not know when registration has failed. It will be fine for a while and I only suspect that something is wrong when I wonder why I have not received any calls for the last week.


Why does the A540IP immediately re-establish the registration when I cycle it's power? Is there a way to configure it to automatically retry every X minutes if the registration goes down?


Alternatively, is there an option on the tms.freshphone.co.za dashboard that I can set to e-mail me if registration is down? Then I can go and manually reset the A540IP to reestablish registration. This is not a great solution but better than nothing.


Before I contact Afrihost (my ISP) can you provide me with technical details so that they can help me appropriately? I'm not an internet expert but the A540IP has been set up to use UDP only so there is no TCP connection to keep alive (?). What is the Freshphone server address? What exactly should be prioritized?


Thanks in advance,

Pieter


P.S. Is there a correlation with losing registration and load shedding?

Hi Pieter,


You can check the the device to see if it has a registration retry time-out setting which will keep trying to register the account. 


At this moment there is no notification system on the website to warn you of the status of the account. 


Please ask your ISP to priorities traffic to the IP address below. Advise them you have a VoIP system and the account does not hold registration. The priorities traffic speed should be at least 1mb up and down, I would suggest trying the retry time-out setting first before contacting your ISP.



41.221.5.107


Hi Pieter


Why does the A540IP immediately re-establish the registration when I cycle it's power? Is there a way to configure it to automatically retry every X minutes if the registration goes down?

It is losing access to the port that it is connecting through your router with. The phones autoreg every 60 minutes. The fact that yours only registers after reboot is simply because it then establishes a new connection with your router. This is not the 5060 port that it registers to our server with, it is a local SIP port on your router that is handed out when a connection is established.  The DIR-825 is notorious for VoIP issues. Try and disable something called SIP ALG on your router. It should be in security/firewall settings. In a nutshell, your firewall is closing that port after a certain amount of time has passed


Alternatively, is there an option on the tms.freshphone.co.za dashboard that I can set to e-mail me if registration is down? Then I can go and manually reset the A540IP to reestablish registration. This is not a great solution but better than nothing.

This option is not available


P.S. Is there a correlation with losing registration and load shedding?

Yes, during loadshedding, internet towers that are down cause saturation of the networks when devices try and connect to other towers, in turn causing the towers in non-loadshedded areas suffering as well due to the number of devices trying to connect


This is most probably not your provider, but your router causing this. You ISP will not be able to assist

Hi Fresh Man,


I battled the whole of yesterday during business hours: the A540IP would not register. It finally registered late afternoon / evening and kept registration until this morning. I made 3 calls and then it dropped registration. Please note that this was with the DIR-825's SIP ALG setting enabled. I'm trying to "scientifically" change only one setting at a time to get to the root of the problem. I have now disabled the SIP ALG setting on the DIR-825, rebooted it and after that rebooted the A540IP. No luck: it is still unable to register.


I don't deny that the DIR-825 could be the problem, but why is the A540IP then able to register and keep registration overnight but then lose it in the morning around 09h00. To me it seems that it is unable to keep registration when VoIP traffic or in general internet traffic increases during business hours (?).


Unfortunately there are a lot of players involved and we need to narrow it down:

1. Gigaset A540IP VoiP

2. Dir-link DIR-825 Router

3. Vumatel Fibre

4. Afrihost ISP

5. sip1.freshphone.co.za server


I'm an electronic engineer and not an IT specialist but I can provide a Wireshark sniff when the A540IP tried to register. See attached. Unfortunately I don't have the expertise to comprehend what is happening.


Could the A540IP be timing out too fast, because the response from the freshphone server is not reaching it in time?


Thanks,

Pieter

Hi Pieter


.

In bold are the ones that it could be

1. Gigaset A540IP VoiP  - These either work, or they don't ( maybe a dodgy ethernet cable sitting next to a power cable) unlikely

2. Dir-link DIR-825 Router

3. Vumatel Fibre - Vumatel are one of our customers. Many of our clients use them

4. Afrihost ISP

5. sip1.freshphone.co.za server - If it was the server, there would be thousands of customers complaining.


I have asked our SysOps Team to take a look at the WS sniff



Hi Pieter


SysOps reckon that you are being blacklisted by our system due to strange things being sent to us. Like the to and from in that sniff. The from should definitely not say Marvinrouter.


Our system is seeing it as a hacking attempt and then blocks your public IP.


What is your public IP? Just type what is my IP on google

Hi Pieter


Have you managed to get to the bottom of it?>



Hi Fresh Man,


Thanks for following up! Sorry, I did not see your feedback from SysOps 8 days ago :( My DIR-825's DHCP host name is "marvinrouter". My public IP is 165.73.110.238


I set the outbound proxy address to 41.221.5.251 on the A540IP and kept SIP ALG enabled on the DIR-825. I assumed that did the trick (?).


I think/hope that your SysOps unblocked my IP, because it has been working ever since with no interruptions. My A540IP stays registered and I have received calls.


Best regards,

Pieter

Hi Pieter


That's great. I am guessing the outbound proxy did the trick. 


The blocked IP's are flushed every 8 hours, so we should be all good.

Login or Signup to post a comment