Grandstream Budgetone

Below are instructions on setting up a Grandstream Budgetone 102 on the 2talk service. For more details on the Grandstream Budgetone product click on the Link below:

The Grandstream site should offer a comprehensive User Guide as well as the latest firmware releases for the Grandstream Budgetone IP phones. You may also find that the instructions below apply to the other Grandstream IP Phones such as the Budgetone 101 and 200 series. Below are some links to help you get your Grandstream Budgetone setup and running:

Full User Manual:

Firmware Downloads Page:

To upgrade your firmware you first get your Budgetone phone setup with access to the Internet following the install guide above and then set your TFTP server IP to that specified on the firmware downloads page above. You should be able to see all the relevant information in the ‘Menu’ options on the phone such as IP addres, TFTP IP etc.

Read the User Guide in the above link for more information.Once you have managed to setup and connect to the web interface on your Grandstream Budgetone, you can then configure it as follows to connect up to the 2talk service:

Step 1: Login to your Budgetone using a web browser. If you do not know the IP address of the phone then hit the ‘Menu’ button and scroll down to IP Address menu option and hit ‘menu’ again


The default password on the Grandstream Budgetone is ‘admin’. If this does not work then you may need to do a factory reset of the phone to revert it back to the default settings. For more information on how to do this see Section 8 of the User Guide above.

Step 2: Setup your basic settings by clicking on the basic settings tab. In here you should have DHCP setup as the default network mode and the time zone and daylight savings settings as appropriate. Remember to click ‘Update’ to commit you settings if you decide to change any!

Step 3: Now switch to the Advanced tab. The following screenshots show the an example of the advanced config page in sections. You will need to setup your advanced settings to match these (where appropriate). The main settings you will need to setup are:

Admin password: your-own-admin-password (You should reset this from the default ‘admin’ for security reasons)

SIP Server:

Outbound Proxy:

SIP User ID: your-own-2talk-number (You should enter your own 2talk phone number here. e.g. 028890000)

Authenticate ID: your-own-2talk-number (Again enter your own 2talk phone number here. e.g. 028890000)

Authenticate Password: your-2talk-password (This should be the password you received during signup)

Name: your-name (You should enter your Full Name here. e.g. John Smith)

The preferred codec order is up to you. But for most people you should select the lower bit rate codecs first (e.g. iLBC, G729) and then the higher bit rate codecs (e.g. G711):

1. iLBC

2. G729A/B

3. G723.1

4. G726-32

5. G722 (Wideband)



iLBC Frame Rate: 20ms (Ensure this is set to 20ms as 30ms will not work correctly)

iLBC payload type: 98

Silence Supression: No

Use DNS SRV: Yes

Regitsration Expiration: 300 (5 minutes - you can set this higher if you wish to use less bandwidth for registrations)

NAT Travseral: Yes

Stun Server:

Enable Call Features: No

Send DTMF: Via RTP (RFC 2833)

DTMF Payload Type: 101

NTP Server:

Send Anonymous: No

You can browse the rest of the settings in the screenshots below…

Step 4: Now Click on ‘Update’ to commit your changes and then ‘Reboot’ the ATA for them to take effect.

Having Problems getting your phone to work?  Read on…

Some users have reported that their routers were interfering with the SIP signalling traffic.  To get around this you can try changing the port numbers you use for outbound and inbound calls.  Simply change your settings to:

SIP Server:

Outbound Proxy:

Local SIP Port: 50600

Update your settings and reboot the phone and see if changing the above helps.  Some other users also reported that Disabling STUN support helped fix their phone registration problems.  So you can try setting:

NAT Traversal:  No

Another thing you can try is disabling DNS SRV record support by setting:


Some users noted that their local DNS cache on their proxy could not understand SRV records and cause the phone to fail registrations.

If you still have no success after trying these work-arounds then contact