2talk incoming calls going to voicemail, port triggering or forwarding?

Forums › VoIP › 2talk incoming calls going to voicemail, port triggering or forwarding?

vroom

89 posts

Master Geek

#110475 9-Oct-2012 22:43

I have a 3G21WZ router (3G) which I've got an IPECS phone on 2talk plugged into. The issue is that after a certain period of time, less than 24 hours, the connection seems to time out somehow, I can make outgoing calls but not receive incoming, they go straight to voicemail. I've searched and it seems to be a fairly common problem, but I'm having trouble fixing it! Is it port triggering that I need, and if so how do I set it up, the below is my attempt so far. Otherwise is it port forwarding, and if so what settings do I need for that? Thanks for any light you can shed.

Application NameTriggerOpenWAN InterfaceRemoveProtocolPort RangeProtocolPortRangeStartEndStartEnd
2tallk2TCP/UDP5060050601TCP/UDP5060050601usb0
2talkTCP/UDP50605061TCP/UDP50605061usb0

edited mod:RC - fixed some formatting that broke the page.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#698829 10-Oct-2012 06:39

A lot more information is required before anybody can help you.

For a start who's the provider and what APN are you using?

vespaman

88 posts

Master Geek

#699118 10-Oct-2012 14:38

Are you using upnp ? what type of NAT does your router support ? if using 2talk does your line show as online or offline ?

jnimmo

1097 posts

Uber Geek

#699323 10-Oct-2012 20:48

You may just need to wind down the registration expiry time on your IP Phone.. I've come across a few which have outrageously high defaults..

vroom

89 posts

Master Geek

#699388 10-Oct-2012 22:33

Registration timer: 600 seconds
Desired lease time: (sec) 691200
Provider: 2talk via 3G modem, Telecom
uPnP is enabled on router
Router says it supports NAT port forwarding, port triggering and DMZ host
Phone shows as online and can make outward calls

Any help would be very much appreciated. Have heard nothing from 2talk support.

Port triggering options on router:
Application Name Protocol Port range start/finish (Trigger and Open)

2tallk2 TCP/UDP 50600 50601 TCP/UDP 50600 50601 usb0
2talk TCP/UDP 5060 5061 TCP/UDP 5060 5061 usb0

DonGould

3892 posts

Uber Geek

#699398 10-Oct-2012 22:51

Have you set the STUN server settings?

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

vroom

89 posts

Master Geek

#699400 10-Oct-2012 22:58

No I haven't set STUN server because I googled it and was confused about whether I needed it or not?

vroom

89 posts

Master Geek

#699402 10-Oct-2012 23:01

Oh and I tried static IP but that hasn't made any difference, it's still on that though.

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

jnimmo

1097 posts

Uber Geek

#699425 10-Oct-2012 23:36

Ahh.. what Telecom 3G APN are you using?
If using internet.telecom.co.nz, the router won't be able to do port forwarding or triggering as unsolicited internet traffic is all firewalled.
direct.telecom.co.nz would let you do port forwarding.

However, as Don said, STUN might help you out and should work on either APN.

vroom

89 posts

Master Geek

#699428 11-Oct-2012 00:04

OK thanks for that, have enabled stun and changed the APN so fingers crossed. Cheers for your suggestions.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#699434 11-Oct-2012 06:46

STUN only allows a device to auto automatically establish the public IP and type of NAT firewall in use. It won't necessarily overcome APN limitations restricting uninitiated inbound traffic.

jnimmo

1097 posts

Uber Geek

#699442 11-Oct-2012 07:19

sbiddle: STUN only allows a device to auto automatically establish the public IP and type of NAT firewall in use. It won't necessarily overcome APN limitations restricting uninitiated inbound traffic.

Ah yes of course.. I was thinking the APN was doing NAT as its firewall, meaning OP would have been double NATed (which STUN may or may not have been able to help with) but realise the standard internet APN is just firewalled not NAT.

Fingers crossed it should keep working this time though having changed that APN :)

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#699462 11-Oct-2012 08:19

Only problem now is some funky stuff what was going on with the XT network that caused VoIP issues. Upon call setup packets were being lost which caused SIP timers to drop calls. I have no idea if it's been resolved at all.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#699496 11-Oct-2012 09:37

sbiddle: Only problem now is some funky stuff what was going on with the XT network that caused VoIP issues. Upon call setup packets were being lost which caused SIP timers to drop calls. I have no idea if it's been resolved at all.

Nope it has not ..no incentive for them to fix it either you will imagine

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

https://www.facebook.com/wxccommunications

vroom

89 posts

Master Geek

#700155 12-Oct-2012 12:26

Well it's been going for 24 hours, so here's hoping. The APN may have been the key. Many thanks for your input, much appreciated.