Help needed with VoIP adapter please

BarGin

Sorry to repeat this but hoping more will see it this way.

BarGin wrote:

I've just bought a HandyTone 486 adapter to use with voipbuster.

I had seen lots of configuration information on the voipbuster forum so was going to refer to that but now when I need it the forum seems to have been deleted from the site!

Does anyone have one of these gadgets and if so could they advise me how to configure mine please?

BarGin

gavinp

I have a Handytone 486 connected to VoIPBuster. It took a lot of fiddling about to get it to work...

Some tips for you:

1. STUN doesn't seem to work for VoIPBuster (it does for Sipgate so it looks like a service problem with VoIPBuster than a fault with the device).

2. If you don't use STUN, the 486 needs to be directly connected to the Internet and using DHCP, needs to have your proper ISP IP address. If you have an ADSL router, it needs to be re-configured as a modem (or bridge mode).
If you are connected using NTL or BlueYonder cable, the ATA486 needs to be connected directly to the cable modem.

3. The other settings are:

SIP Server: sip.voipbuster.com
Outbound proxy: <blank>

SIP User ID: <VoIPBuster username>
Authenticate ID: <VoIPBuster username>

Set all of the vocoder settings (1 to 7) to PCMU

NAT Transversal: No

Send DTMF: via SIP INFO

FXS Impedence: CTR21


The settings above definitely work. If you are not able to reconfigure your ADSL router as a modem, you *may* be able to use another company's STUN server.

Try setting NAT Transversal to "Yes, Stun Server is stun.sipgate.net:10000"

I haven't tried this personally so it may not work.

The port forwarding allegedly required for the ATA486 to sit behind NAT is:

Port: 5060/UDP (SIP signaling)
Port: 5004/UDP (RTP, language)
Port: 8000-8012 (Voice)
Port: 10000 UDP (STUN)
Port: 3478 UDP & TCP

With STUN working properly, it should work straightaway without port forwarding but unfortunately it doesn't seem to (for VoIPBuster)...

Good luck.

Thanks

Gavin

BarGin

Thanks Gavin for all that info but I still don't believe it's working correctly.

I have the 486 plugged directly into my NTL cable modem but don't as yet have an RJ11 adapter for my telephone so can't try making any calls with it. I shall see if Maplins have one tomorrow.

The reason I don't think its working is because the red light is flashing constantly every couple of seconds so I assume its not logged in.

Do I need to set the port forwarding with my setup and if so where would I do that? The only router I have is the 486.

Thanks again for your help.

BarGin

Graham1

I have completely different hardware but maybe some of this might help.

For my Linksys PAP2 phone adapter I found it a lot more difficult to get it to work with VOIPbuster compared to other service like sipphone.com and sipgate.co.uk

The final step I used to get it to work was in the phone adapter to use a restricted range of ports for RTP (I used 16384 through 16391) and then in my router to individually forward each of the following UDP ports (my router doesn't allow you to specify a range so I had to do these individually):

5060
5061
16384
16385
16386
16387
16388
16389
16390
16391

in each case forwarded to the IP used for the phone adapter

after these steps it finally sprung to life on VOIPbuster.

Of course, if your cable modem is not using NAT then none of this will be applicable.

gavinp

Yes, the flashing indicates it is not logging in properly.

What is your WAN IP address showing as in the ATA config?

Is it your proper NTL IP address ? I have heard that the order the devices are powered up sometimes causes funnies with cable modems - it might be worth powering off your cable modem and back on again to see if this has any effect.

You won't need to worry about port forwarding or STUN with a cable modem assuming it is directly attached to the WAN port and obtaining the IP address.

What happens if you start a command prompt and type "ping sip.voipbuster.com" ?

I get the following - the address is the important part - you can ignore the response timed out messages as they aren't relevant.

Pinging sip.voipbuster.com [213.61.187.147] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.61.187.147:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

If NTL are reporting a different IP address then this will stop it working - entering the IP address as the SIP server may suffice but only do this if NTL are resolving to the wrong address.

It could be that the ATA detects that no phone is connected and causes the problem as well ?

Thanks

Gavin

BarGin

Thanks again for your help.

WAN IP Address: deleted

If I type ipconfig at a command prompt I get:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

If I go to: http://whatismyipaddress.com it reports: deleted

Pinging sip.voipbuster.com [213.61.187.156] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.61.187.156:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

I have also tried changing the sip server from sip.voipbuster.com to 213.61.187.147

Also the phone is now plugged in properly and the pstn pass through works ok.

Any more assistance would be greatly appreciated.

Thanks,

BarGin

gavinp

Bargin,

Please edit your last post and remove your IP address as a safety precaution.

The WhatsmyIP address is one of the NTL proxy servers as far as I can tell.

From the details supplied, it sounds like it is working properly regarding addresses etc.

I think the next step would be to setup a free account with Sipgate and see if that works. They provide you with specific instructions to setup a Grandstream ATA486 in their help section. This will prove that your Internet connection etc is working OK and the problem lies with the VoIPBuster config.

http://www.sipgate.co.uk/

Thanks

Gavin

BarGin

Works perfectly with Sipgate. Will have to keep trying with voipbuster now.

Thanks,

BarGin

BarGin

Got it working with voipbuster now. Seems I was too impatient, wasn't giving it enough time to register before changing settings again!

Thanks for all your help.

BarGin

gavinp

Bargin,

If you send me a private message with your email address, I'll email you the screenshots from my ATA486 so you can compare.

Thanks

Gavin