Upgrade 3CX to v18 and get it hosted free!
Home | PBX & Softphones | Nokia

Nokia

Author image
Posted by , on June 14, 2006

Nokia Cell Phones with VoIP/SIP Support

Nokia S60 Phones with a SIP stack and built-in VoIP Client

Page Contents

Notes about Nokia’s S60 VoIP support

  • Nokia phones have varying revisions of their VoIP stack on their phones.
  • VoIP Release 1.0 does not support STUN or NAT traversal. This applies to the E60 and E70.
  • For best performance, be sure to upgrade the phone’s firmware to the latest revision. Updated versions of the VoIP Releases fix many issues.

Nokia S40 Phones with VoIP Support

S40 devices support two types of VoIP, UMA which is always a cellular operator hosted service and SIP VoIP (based on IETF standards) which is independent from the cellular operator.

  • UMA devices
    • 6086, 6136, 6301
  • SIP VoIP devices
    • 6300i, Nokia 6260 slide, Nokia 207, Nokia 208, Nokia 208 DualSIM, Nokia Asha 302, Nokia Asha 303, Nokia Asha 309, Asha 310, Nokia Asha 311, Nokia 515, Nokia 515 DualSIM, C3-01 Gold Edition, C3-01 Touch and Type and X3-02 Touch and Type

The latest Vertu handset Signature S Design supports VoIP as well and it looks very similar to the 6300i, could it be the same?

Notes about Nokia’s S40 VoIP support

  • S40 UMA phones, only support VoIP through the implementation of UMA.
    • With UMA, VoIP calls can only be made through the cellular service provider, if offered. User-selected VoIP service is not possible.
    • Additionally, these phones can never be used independently of a cellular service plan and must always have a working SIM card installed to make any calls (GSM or Wi-Fi).
  • The 6300i is the first S40 device to support SIP/VoIP.
    • Series40 phones can be used independently of a cellular service plan and without a SIM card installed to make VoIP calls (Wi-Fi or 3G).

S40 SIP VoIP Phone Configuration

Phone configuration consists of the following two steps:

  1. Save a Wi-Fi network
    • GoTo -> WLAN -> Available WLANs -> choose the WiFi network you wish -> Connect -> enter encryption key if needed -> OK
  2. Configure VoIP provider settings
    • GoTo -> Internet tel. -> Accounts -> Add new -> Select VoIP Provider -> Enter username and password -> OK

HINT: If you want to see a longer list of service providers remove SIM card from the phone (the service provider list is filtered somehow based on which SIM card one has in the phone when configuring the phone)

n0kVoIP is a FREE tool to configure many different predefined VoIP providers as well as custom SIP settings to Nokia 6260 Slide, 6300i, C3-01 Touch and Type, C3-01 Gold Edition and X3-02 Touch and Type.

Support for registering to an arbitrary VoIP/SIP servers is possible from the built-in “Internet Telephony Wizard” by choosing “SIP settings” or manually with following steps.

1) Download settings example and modify it to include the VoIP provider settings that are wanted.

  • S40 VoIP v72 example if you have 6300i
  • S40 VoIP v81 example if you have 6260 slide
  • S40 VoIP v92 example if you have C3-01, C3-01 Gold Edition or X3-02

2) Download the wbxml2 tool.
3) Make a .prov file with xml2wbxml.exe tool from your xml file
4) Scan and connect your phone via Bluetooth.
5) Send (OBEX PUSH) the .prov file to the connected phone

Nokia Maemo Phones with SIP Stack and built-in VoIP Client

  • N800 N810 N810 WiMAX
    • N8xx devices are Internet Tablets running Maemo Linux.

Nokia Phones that support VoIP calling via 3rd Party Software

    • S40 Phones
      • 3250 5500 5700 6110 6120 6121 6290 6630 6680 6681
    • S60 Phones – N Series
      • N70 N71 N73 N75 N77 N80 N81 N82 N90 N91 N92 N93 N95
    • S60 Phones – E Series
      • E50 E51 E60 E61 E61i E65 E66 E70 E71 E90
    • Maemo Phones
      • 770 N800 N810 N810 WiMAX
    • These phones support VoIP via third party software such as Gizmo, fring, and others.
    • Phones in this list are only those that have the Nokia VoIP Framework built in (not necessarily a SIP client).
      • Any application that implements its own full SIP stack (without relying on the Nokia VoIP Framework) will support VoIP regardless of the device’s presence on this list.
    • Phones in this list may also have built-in VoIP clients. See models in previous sections.

    Configuration – S60

    • Nokia has an area on their website dedicated to Internet Calling that covers many of the basics of VoIP calling and configuration with Nokia phones.

    Asterisk Configuration

    sip.conf

    [nokiaphone]
type = peer
username = <username>
secret = <password>
host = dynamic
context = <outgoing phone context>
qualify = no ;saves battery
mailbox = <mailbox extension> ~np~[@ <mailbox context>]~/np~
fromdomain = <FQDN of server> ;necessary to receive MWI
vmexten = <exten to reach voicemail>
disallow=all
allow=ulaw

    Basic Phone Configuration

    Phone configuration consists of three steps:

    • Define an Access point
      • Tools -> Settings -> Connection -> Access points
      • Select Options with left softkey and choose New access point
      • Fill in appropriate parameters to connect to wireless network
    • Create SIP Profile
      • Tools -> Settings -> Connection -> SIP settings
      • Select Options with left softkey and choose New SIP profile and Use default profile
      • Populate as shown in tables below
      • Proxy server can remain empty
    • Create an Internet Telephone Profile
      • Tools -> Settings -> Connection -> Internet tel.
      • Select Options with left softkey and choose New profile
      • Set any name and select newly created SIP profile
    General Profile Settings
    Parameter Value
    Profile name <profile name> (anything)
    Service profile IETF
    Default access point <access point defined above>
    Public user name sip:<username defined in sip.conf>@<hostname/IP of asterisk server>
    Use compression No
    Registration Always on (necessary to receive incoming calls, otherwise can be set to when needed)
    Use Security No
    Proxy Server no need to configure
    Registrar server (see below for configuration)
    Registrar Server
    Parameter Value
    Registrar server address sip:<hostname/IP of asterisk server>
    Realm asterisk (or change to match if overwritten in sip.conf)
    User name <username defined in sip.conf>
    Password <password defined in sip.conf>
    Transport type Auto or UDP
    Port 5060

    Advanced Phone Settings

    Starting with VoIP Release 2.0, Nokia released a tool called SIP VoIP Settings Tool which allows advanced tweaking of many VoIP parameters.
    Of particular importance is the ability to set a STUN server and define NAT firewall traversal parameters. This is crucial for the proper use of the phone behind a NAT firewall or when using a non-routable IP.
    The STUN server is set on a per asterisk server basis and the NAT traversal parameters are set on a per access point basis.

    SIP VoIP Settings Tool and its manual can be downloaded from Nokia

    Setting STUN server

    • Run SIP VoIP Settings Tool
      • Installations -> SIP VoIP Settings Tool
    • NAT FW settings -> Domain parameters -> <asterisk server>
    • Set STUN server name to hostname of STUN server and set STUN server port to 3478 (unless not running on default STUN port)

    Setting NAT firewall traversal parameters

    • Run SIP VoIP Settings Tool
      • Installations -> SIP VoIP Settings Tool
    • NAT FW settings -> IAP parameters -> <target access point>
    • TCP Nat bind. refresh and UDP NAT bind. refresh are in seconds. STUN retransmission is in milliseconds.

    Implementation Issues

    Traversing Multiple Distinct WLANs

    Nokia’s current implementation of SIP profiles binds an account to a given WLAN access point.
    If the phone is used across multiple WLAN networks, then there should be one SIP profile entry for each unique ESSID that it connects to.
    When defining the Internet telephone settings, all SIP profiles should be bound to a single Internet telephone profile.

    Traversing the same WLAN across multiple subnets

    As is the case with many portable devices, the Nokia phones suffer from connectivity problems when traversing a single WLAN (same ESSID) that is broken up into different subnets because of IP limitations or routing simplicity.
    The typical use scenario is in a large university where different regions of the campus have different subnets, but all access points broadcast the same ESSID.
    This is arguably a network design issue instead of a client connectivity issue. Nonetheless, the issue is quite prevalent and can be quite debilitating.
    The Nokia phones, particularly the ones that are pre-S60r3 FP1, have particular difficulty releasing/renewing their DHCP leases when moved to an access point on a different subnet.

    MWI – S60

    Nokia supports VoIP message waiting indicator on all VoIP Release versions.

    A successful MWI delivery will light up the MWI envelope icon on the active standby and screensaver screens, as well as deliver an SMS-like message to the phone’s inbox indicating the number of messages waiting with a callback number defined as follows: <vmexten>@<fromdomain>

    Unforunately, the MWI implementation is buggy.
    The phone will often reply to a SIP NOTIFY MWI notice with a “400 Bad Request” reply. The cause of this is unknown.
    This error results in an unreliable delivery of MWI notices from the server.
    However, the MWI notice is often accepted at each SIP re-registration following an expiration. Thus, a simple workaround to ensure a reliable MWI delivery is to set a relatively low defaultexpirey (around 5 minutes) in sip.conf so that the MWI is nearly guaranteed to arrive no later than a few re-registration cycles.

    SIP Messaging (via MESSAGE method)

    There have been mixed reports of messaging support with Nokia devices.
    SIP messaging appears to work via openSER messaging. However, there is no documented success of this method.
    sipsak based messaging does not appear to work. On both an E70 and an E51, a message sent via sipsak returns as a “415 Unsupported Media Type” for Content-Type: text/plain.
    The apparent only Content-Type accepted on the E70 is application/sdp and the E51 additionally supports application/poc+xml.

    External Resources

     

Related Posts:

Common VoIP Security Threats and Protection Ways
March 2, 2023
The wide adoption of VoIP (Voice over Internet Protocol) technology has become a popular way for businesses and individuals to communicate with one another. Sti...
WebRTC performance testing is complicated
February 23, 2023
One of the things that boggle the mind is WebRTC performance testing. It stems from the fact that WebRTC has many moving parts AND that it incorporates differe...
Nortel Phones
September 23, 2005
Nortel IP phones use the proprietary Unified Networks IP Stimulus (UNISTIM) protocol. Details of the initial implementation and theory of operation of the UNIST...
3rd Party SIP End Points with Avaya IP Office 500
November 28, 2010
Here I’m going to discuss 3rd party sip endpoint registration with Avaya IP Office 500 v2 PBX. You have to have a “3rd Party IP Endpoints” license in orde...
PBX Calling ID
September 7, 2004
Calling ID Calling ID represents the digits passed from the carrier (or PABX) to the end user device (or between PABXs) that identify who the caller is. Otherwi...
IP Centrex
July 11, 2005
IP Centrex is a service where the call platform and PBX features are hosted at the service provider location. The business end users connect via IP to the provi...
SJphone
August 1, 2005
SJphone is a softphone that allows you to speak over the Internet using any desktops, notebooks, PDAs, stand-alone IP phones, and even any traditional landline ...
Vonage Router
April 24, 2012
The Vonage router connects up to two Vonage phone lines using a high-speed cable or DSL (Digital Subscriber Line) Internet connections. As a result, customers c...
Vonage Adapter
January 13, 2012
The Vonage adapter is an ATA that connects your traditional phones to Vonage’s VoIP service. With the adapter, you can use your existing phones and high s...
PBX Do Not Disturb
September 14, 2004
PBX Do Not Disturb or DND functionality is the ability of a phone or client to ignore any incoming calls. This can be implemented in several ways. Ringer Off or...
Get 3CX - Absolutely Free!
Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Verify your Email

Check your inbox!

We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).

Upon verification you will be directed to the 3CX setup wizard.