Freshphone Offline

waynehooper

waynehooper

Senior Member
Joined
Sep 4, 2008
Messages
927
Reaction score
205
Location
East London
I have Yealink W60P that is working perfectly, and I can receive and make calls.

However if I reboot my router (Asus RT-AC66U B1), I can make calls, but cannot receive any. On the site the status shows as Offline.

If I reboot the Yealink, then I can receive calls again, and the status on the site changes to online.
 
Check the "SIP ALG" setting on your router. Try with it on, and then off, and then see which state resolves your problem.
 
Tried with both, same result after I reboot the router - status goes to Offline until I reboot the Yealink.
 
waynehooper said:
Tried with both, same result after I reboot the router - status goes to Offline until I reboot the Yealink.
Click to expand...
Assign a static/mac reserved IP for the VOIP phone on your router. If it is on DHCP now.
 
Might be related to upnp . I would make sure the yeastar has a static or reserved DHCP IP address first, then forward ports 5060 and 5061 (tcp and UDP to it) on the router.
 
Hamish McPanji said:
Might be related to upnp . I would make sure the yeastar has a static or reserved DHCP IP address first, then forward ports 5060 and 5061 (tcp and UDP to it) on the router
Click to expand...

This is dangerous advice. There's absolutely no need to have port forwarding enabled for server-connected SIP devices.
 
I'm using a Fanvil IP phone

If the router is rebooted, it always assigns a different IP address to the one before.
Eg: 192.168.1.103. then next time 192.168.1.104 and so on.
Its been in 4 months now and the IP address today is 192.168.1.119

Who knows why? I don't have the same problem as the OP

Is a revised firmware available for the Yealink?

I fitted a Grandstream ATA adaptor and this improved after the firmware upgrade

The fellow with the Grandstream had his phone ringing all hours of the day and night. I changed the port from 5060 to 5090 and this problem went away
 
deweyzeph said:
This is dangerous advice. There's absolutely no need to have port forwarding enabled for server-connected SIP devices.
Click to expand...
It allows the packets to traverse to the endpoint. I've done it since forever, and it has always solved my issues.

It's a better option than upnp , which is what is probably happening at the moment

 
Hamish McPanji said:
It allows the packets to traverse to the endpoint. I've done it since forever, and it has always solved my issues.

It's a better option than upnp , which is what is probably happening at the moment

Click to expand...

Will give it a try, and see if it works.

Edit - still doing it with ports forwarded - beginning to suspect its Freshphone.
 
Last edited:
Hamish McPanji said:
It allows the packets to traverse to the endpoint. I've done it since forever, and it has always solved my issues.

It's a better option than upnp , which is what is probably happening at the moment

Click to expand...

You don't need to have port forwarding enabled (directly or via upnp) when you connect to a SIP server, because it's a standard client-server setup. Because the SIP phone is connected permanently to the SIP server as a client, it can still receive incoming calls even if you don't open up port 5060 to the outside world.
 
waynehooper said:
I have Yealink W60P that is working perfectly, and I can receive and make calls.

However if I reboot my router (Asus RT-AC66U B1), I can make calls, but cannot receive any. On the site the status shows as Offline.

If I reboot the Yealink, then I can receive calls again, and the status on the site changes to online.
Click to expand...
I've also been having this problem with Yealink w60b & Freshphone recently.
Changing Transport to TLS or TCP seemed to help for me.

1591818884434.png

The benefit of TLS is encryption. TLS runs over TCP.
It's generally recommended to use UDP for real time traffic like VoIP.
If you have a reliable un-conjested fibre line TLS/TCP should not affect the call quality.
 
system32 said:
I've also been having this problem with Yealink w60b & Freshphone recently.
Changing Transport to TLS or TCP seemed to help for me.
The benefit of TLS is encryption. TLS runs over TCP.
It's generally recommended to use UDP for real time traffic like VoIP.
If you have a reliable un-conjested fibre line TLS/TCP should not affect the call quality.
Click to expand...

Strangely enough my Afrihost fiber line was installed today, and after changing the wan setting to DHCP, I have not had any more offline issues after rebooting the router. I will keep your solution in mind though if I have any further issues. Could have been an issue with Telkom PPPOE
 
Have a FF service. On a slower LTE service, Transportation service can be set to TCP instead of UDP and it will become more reliable
 
I have had endless issues with FF over the past 3-4 weeks. Device had issues registering, then miraculously registered again, then registration failed, on and off. Then it registered, accepted incoming calls, but did not allow outbound. I was at the point of cancelling, but eventually managed to get it right. FF support desk was not much help either.
I will be monitoring it more regularly now.

I prefer UDP because I am on fibre.
The device needs UDP outbound on ANY destination port to sip1.freshphone.co.za
 
My ISP (Afrihost LTE via Telkom) in the shop does not support UDP, so unless TCP is used, there is intermittent service.

Asked them about it, but no reply
 
I'm setting up a FF service with a friend who has RAIN 4G and a DLink DWR-922 router. 4G very good - 38 mbps down and 8 mbps up

But, does RAIN 4G support VOIP? Have submitted questions via website 3 times without reply
 
chrisc said:
I'm setting up a FF service with a friend who has RAIN 4G and a DLink DWR-922 router. 4G very good - 38 mbps down and 8 mbps up

But, does RAIN 4G support VOIP? Have submitted questions via website 3 times without reply
Click to expand...
Why not just test it?
 
I did
The IP phone says "trying" but will not connect
The same phone connects in 20 seconds at my place (100mb fibre line)
 
chrisc said:
I did
The IP phone says "trying" but will not connect
The same phone connects in 20 seconds at my place (100mb fibre line)
Click to expand...
Maybe contact FF? See if they have any knowledge?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X