Cisco’s range of IP phones are known to work well with 2talk. The instructions below should help users of the 7940 and 7960 series models to configure their phones for use with 2talk.
1. Firstly you need to ensure that you are running the SIP version of firmware code on your phone (rather than the SCCP/Skinny version of code which is designed for use with Cisco’s CallManager product). You should see ‘Sip’ in the top right corner of the phone if you are running the SIP code. Another way to check is to click on the Settings button on your phone, select Status and then Firmware Versions. Your firmware version should begin as ‘P0S’ if the firmware is SIP based. For instructions on switching your handset from SCCP to SIP visit the following link:
The firmware upgrade process differs depending on which version you are migrating from and to. It is recommended that you download the latest stable version of SIP firmware for your phone. You can fetch the latest firmware version from:
You will need to be running a TFTP server on your network and a DHCP server capable of specifying custom options. You can find several guides online to help you with this process including:
NOTE 1: When upgrading from SCCP firmware versions less than 5 or less you will need to upgrade first to a SIP firmware version of 5 or less. You cannot upgrade directly from SCCP Version 3 firmware to SIP Version 7 or 8 firmware for example. So find yourself an earlier SIP firmware version that has the firmware file in *.bin format (rather than *.sbn) and then upgrade to the later SIP firmware once you have a 3.x or 5.x SIP firmware version running on the phone correctly.
NOTE 2: If you upgrade to version 7 or 8 of the SIP firmware and upload your configuration via TFTP then you may run into a problem where the phone starts up and says ‘Protocol Application Invalid’. Don’t panic. You need to support an Option that specifies the TFTP server IP address (Option 150). Your own DHCP server may not support Option 150, so you may need to temporarily do this via the DHCP server in Windows or Linux. Below is a link explaining how to setup your DHCP server to pass back the required Option 150 for the phone to bootup correctly.
The hardest part is now over. Upgrading the firmware on the Cisco IP phones can be hard work!
2. Now you are ready to configure your phone to run on 2talk. You can either do this via a TFTP config file or manually using the menu buttons on the phone itself.
TFTP File Method
Create a file called SIPDefault.cnf which lives in the root folder of your TFTP server. There are many settings you can define in the SIPDefault.cnf file but most you can leave set as the default. Typically you put all of your Global settings in the SIPDefault.cnf file and then any phone specific settings in another file in the format SIP000812345678.cnf. (where 000812345678 is the MAC address located on the back of the phone). You can also put the phone specific configs in a sub-directory such as ’sip_phone’ under the root folder of your TFTP server. The following is an example of what you might set in the SIPDefault.cnf file for 2talk. The config assume that you are running firmware version P0S3-08-2-00.
sntp_server: ntp.2talk.co.nz ; SNTP Server IP Address
sntp_mode: unicast ; unicast, multicast, anycast, or directedbroadcast (default)
time_zone: NZST ; Time Zone Phone is in
dst_offset: 1 ; Offset from Phone’s time when DST is in effect
dst_start_month: October ; Month in which DST starts
dst_start_day: “0″ ; Day of month in which DST starts
dst_start_day_of_week: Sunday ; Day of week in which DST starts
dst_start_week_of_month: 1 ; Week of month in which DST starts
dst_start_time: 02:00 ; Time of day in which DST starts
dst_stop_month: March ; Month in which DST stops
dst_stop_day: “0″ ; Day of month in which DST stops
dst_stop_day_of_week: Sunday ; Day of week in which DST stops
dst_stop_week_of_month: 3 ; Week of month in which DST stops 8=last week of month
dst_stop_time: 2:00 ; Time of day in which DST stops
dst_auto_adjust: 1 ; Enable(1-Default)/Disable(0) DST automatic adjustment
The key settings in the default config are proxy_register, proxy1_address, outbound_proxy, dtmf_inband, dtmf_outofband, sntp_server, dtmf_avt_payload, nat_enable and nat_address. If you do not set the proxy and NAT settings correctly then you may experience no audio or one way audio problems when making/receiving phone calls.
Next build a config specific for your phone using the MAC address of the phone and your own personal 2talk username/password settings. The following is an example only for 2 lines ‘099749000′ and ‘049749000′. On the 7960 you can have up to 6 lines, so define your other lines in the same way but changing the number (e.g. line6_name etc.) In our example we place the individual phone config in a sub-directory called ’sip_phone’ on the TFTP server.
SIP000812345678.cnf (i.e. your phones individual config - replace this filename with your own MAC address)
line1_displayname: “Your Name ”
line2_displayname: “Your Name ”
phone_label: “2talk Phone “
The manual method basically means programming all your settings via the buttons on your phone. This can be quite time consuming so be prepared to spend some time setting your phone up. Before you can edit your settings you need to ‘Unlock config’ (option 9 in the settings menu). Default password to unlock the config is ‘cisco’. Again, the settings are largely up to you but here are the key settings you need to be aware of to get your phone running on 2talk:
Network Configuration Menu
Settings in this menu will be specific to your own network. We recommend using DHCP if possible and you may also set (optional) your DNS Server 1 to 188.8.131.52 and DNS Server 2 to 184.108.40.206 which are 2talk’s main DNS server IP addresses.
SIP Configuration Menu
- Line 1/2/3/4/5/6 Configuration
- Name - Your phone number
- Shortname - Whatever you want to display on the phone e.g. Area, phone number etc)
- Authentication Name - Your 2talk phone number (e.g. 099749000)
- Authentication Password - Your 2talk password
- Display Name - Your Actual Name (e.g. Fred Bloggs)
- Proxy Address - sip.2talk.co.nz
- Proxy Port - 5060
- Messages URI - 028890000 (or *55)
- Preferred Codec - g729a (Recommended unless you have plenty of bandwidth)
- Out of Band DTMF - avt_always
- Register with Proxy - Yes
- Register Expires - 600
- Phone Label - 2talk Phone (or whatever you prefer!)
- Enabled VAD - No
- VoIP Control Port - 5060
- Start Media Port - 16384
- End Media Port - 32766
- Backup Proxy - Unprovisioned
- Emergency Proxy - Unprovisioned
- Outbound Proxy - sip.2talk.co.nz
- Outbound Proxy Port - 5060
- NAT Enabled - Yes
- NAT Address - Unprovisioned
Call Preferences Menu
- Do Not Disturb - No
- Caller ID Blocking - No
- Anonymous Call Block - No
- Auto-Complete Numbers - Yes
- Call Waiting - Yes
- Call Hold Ringback - No
- Stutter Message Waiting - No (Yes if you prefer both Lamp and stuttered dialtone for message waiting indication)
- Time Zone - NZST
- SNTP Settings
- SNTP Server - ntp.2talk.co.nz
- SNTP Mode - Unicast
- DST Auto Adjust - Yes
- Logo URL - http://live.2talk.co.nz/2talklogo.bmp (optional)
Hopefully, the above should provide enough of a guide to get you set up and running on 2talk with your Cisco 7940 and 7960 phones. Settings may differ for your own setup, but the main thing to remember is that NAT and Proxy settings must be enabled and set as sip.2talk.co.nz. If you have any feedback on this guide please add your comments below or contact email@example.com