VOIP =/= Telecom Broadband?

Forums › Spark New Zealand › VOIP =/= Telecom Broadband?

Batman

Mad Scientist
18436 posts

Uber Geek
+1 received by user: 2337

Trusted

Lifetime subscriber

Topic # 62964 18-Jun-2010 08:47

After 1 year of switching from SS to telecom, our VOIP has not been able to receive calls for 1 year.
The box is from singapore, and it goes to sleep and cannot be woken up to receive calls. If it has been recently activated/woken up it can receive calls. The provider in singapore is very sure the problem lies herein within telecom.

Would that be a fair comment?
(i have no idea so please correct my ignorance!)
(yes i could've posted in voip but i dont even know where to start to troubleshoot the router settings and have been assured it probably isnt that - although the router we have is a restrictive device called thomson)

freitasm

BDFL - Memuneh
60598 posts

Uber Geek
+1 received by user: 11531

Administrator

Trusted

Geekzone

Lifetime subscriber

Reply # 342860 18-Jun-2010 08:57

joker97: The box is from singapore, and it goes to sleep and cannot be woken up to receive calls. If it has been recently activated/woken up it can receive calls. The provider in singapore is very sure the problem lies herein within telecom.

AFAIK, Telecom does not block any traffic. Unless you are in a "managed" plan and the box can't see any activity (or the delays are too high) and decides to sleep because of that.

If the box goes to sleep, certainly there should be a setting to change this behaviour?

You can support content creators (and Geekzone) by using the Brave browser.

old3eyes

7799 posts

Uber Geek
+1 received by user: 779

Subscriber

Reply # 342886 18-Jun-2010 09:57

Does the box wake up after an outgoing call has been made. If so it sounds liker a firewall issue..

Regards,

Old3eyes

maverick

3594 posts

Uber Geek
+1 received by user: 79

Trusted

WorldxChange

Reply # 342910 18-Jun-2010 10:23

I can tell you Telecom does not block VOIP (SIP) traffic, you most definetly have a nating issue with the device and the router in front where it is blocking inbound SIP packets where they originate from the public internet... Outbound works becasue your router will pass it it out with no restrictions.

Check if you have an option for a SIP keep alive .. drop this this to 30 secs and see how you go, it can be adjusted then top find the sweet spot for your router before it kills the pinhole.

Secondly try setting a static route for SIP to your device

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

sbiddle

26482 posts

Uber Geek
+1 received by user: 6034

Moderator

Trusted

Biddle Corp

Lifetime subscriber

Reply # 342949 18-Jun-2010 11:34

My first pick would be an issue with long registration times and your NAT firewall blocking inbound traffic. It certainly won't be an issue with Telecom.

Forwarding port 5060 (assuming your provider uses 5060 which is the standard SIP port) would probably fix the issue.

Batman

Mad Scientist
18436 posts

Uber Geek
+1 received by user: 2337

Trusted

Lifetime subscriber

Reply # 342950 18-Jun-2010 11:35

oh oops.

oldeyes: yes box wakes up after making outgoing call.
maverick: no option to keep SIP alive the thomson router is really very restrictive.

thanks anyway, i'll leave it to the person using the voip to sort it out as i am not able to help them - coz i dont understand router settings!