login | register
Fri 16 of May, 2008 [07:50 UTC]

voip-info.org

Navigation
Today's Deals
Recently Visited Pages
Search with Google
Search this site with Google. Results may not include recent changes.
 
Google Ads
Last Changes
Shoutbox
  • Juan Ortega, Thu 15 of May, 2008 [10:33 UTC]: Hi everybody, I'm Juan, an ITCom student, and I need to know what basic elements I need to create a VoIP network. Can anybody helpme, please?,Thank you very much
  • gineta, Wed 14 of May, 2008 [03:58 UTC]: any here not fine the configuration of firewall juniper -screem for VOIP asterisk????
  • Anoop Prabhakaran, Tue 13 of May, 2008 [12:16 UTC]: I am developing Asterisk IVR, Whenever i make a internation call to the IVR system, the DTMF is not getting detected properly, this happens only for the first time, second call onwards system works fine. why this is happening
  • joe, Mon 12 of May, 2008 [04:27 UTC]: Is there an opensource browser based softphone, or a system like Busta where everything is not manages through their website?
  • Nick Barnes, Fri 09 of May, 2008 [11:36 UTC]: Christopher - yesterday I tried an Asterisk install on a CentOS 5.1 box with stock GUI and it all worked fine. Sorry I can't help.
  • aero, Fri 09 of May, 2008 [08:20 UTC]: can someone help me out on this, i tried to play some sound files on my asterisk box and this is the error message i got. WARNING[4429]: format_wav.c:169 check_header: Unexpected freqency 22050 May 8 11:17:39 WARNING[4433]: codec_gsm.c:194 gsmtolin_fra
  • Christopher Faust, Thu 08 of May, 2008 [14:15 UTC]: I beleive that I may have to change something in the xserver configuration. Please advise
  • Christopher Faust, Thu 08 of May, 2008 [14:14 UTC]: Everything was perfect. In the bios I have increased the memory allocated Still receive input not supported on my display.
  • Christopher Faust, Thu 08 of May, 2008 [14:13 UTC]: This would not be my main box. I am doing some testing to see if I can install zaptel and asterisk 1.4 on a full centos 5.1 box with development software Its bizzare, because before I went through the asterisk and zaptel installation everything was perfe
  • Nick Barnes, Thu 08 of May, 2008 [13:44 UTC]: Christopher - I can't see any way in which an Asterisk installation would muck your GUI, but remember that it is advised not to use a GUI on an Asterisk box anyway.
Server Stats
  • Execution time: 0.96s
  • Memory usage: 2.24MB
  • Database queries: 29
  • GZIP: Disabled
  • Server load: 1.72

Nokia

Nokia Cell Phones with VoIP/SIP Support


Nokia S60 Phones with a SIP stack


  • Nokia E51
  • Nokia E60
  • Nokia E61
  • Nokia E61i
  • Nokia E65
  • Nokia E70
  • Nokia E90
  • Nokia N80ie
  • Nokia N81 (8GB)
  • Nokia N82
  • Nokia N95

Nokia Series40 Phones with a SIP stack


Notes about Nokia's VoIP support

  • Nokia phones have varying revisions of their VoIP stack on their phones.
    • Nokia maintains a chart of VoIP support across different Nokia devies
  • S60 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.



Configuration



Asterisk Configuration


sip.conf
  
[nokiaphone]
username=<username>
type=friend
secret=<password>
host=dynamic
context=<outgoing phone context>
qualify=60000

Qualify timing. While the phone is in power save mode (screen saver), it responds more slowly. It appears that during power save mode the response time can go up to about 30 seconds. By default qualify in asterisk is sent every 60 seconds (chan_sip.c) and expects a response within 250 (or timed specified by the qualify parameter). Because of this, asterisk will see the phone as unavailable as soon as power save mode comes on. In order to keep alive the Nokia phones and have inbound ringing always working, set qualify to at least 30000 (30 seconds). By doing this, the nokia phones should be reachable behind most firewalls. This was tested using a trendnet router and a linksys router. On the linksys, the phone was reachable after 9 hours of power saving and on the trendnet for 4 hours.


Basic Phone Configuration


The latest official VoIP configuration manual from Nokia

Phone configuration consists of three steps:

  1. 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
  2. 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
  3. 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
ParameterValue
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
ParameterValue
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.
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 (see device specification matrix), have particular difficulty releasing/renewing their DHCP leases when moved to an access point on a different subnet.

MWI


Despite Nokia's claim to the contrary (see feature matirx), no VoIP Release versions support message waiting indicators. This prevents notification of new voicemail on the asterisk server.
This has been a long-standing bug, but Nokia has yet to fix it.
There is a potential fix for this mentioned here by sending the urgent message count in addition to the messages waiting in the same notify packet, but this has not been confirmed.

SIP Messaging (via MESSAGE method)


There have been mixed reports of messaging support with Nokia devices.
Functionality appears to completely vary with phone, working well on some devices and not at all on others.
There has been reported success with E61i and E70, but it does not appear to work with E51.



External Resources





Where to Buy




Created by Joseph John, Last modification by 6300i on Sun 11 of May, 2008 [06:16 UTC]

Comments

Comments Filter

Nokia E51 Freezes

by Rafael Lobo on Tuesday 13 of May, 2008 [17:30:43 UTC]
I am having the same issue. The phone connects just fine to the asterisk server. It does makes calls, but when it receives a call it locks up and won't go anywher. The only way to get back working is taking the battery off and then power on again. Please somebody help us to find a fix for that. I hope nokia release a new firmware fixing this soon.

Re: Strange Problems with Netfilter Modules

by Andres Artigas on Tuesday 13 of May, 2008 [15:12:06 UTC]
Hi,
 I am having the same ploblem. Is wierd, i register in asterisk using my notebook(wifi) but the E65 runs into timeout.  Did you solve the issue?

Nokia E51 Freezes with Asterisk when called

by Marco Davids on Monday 28 of April, 2008 [18:07:26 UTC]
I can call out over SIP with my E51 via Asterisk, but I can not receive calls on the phone.
The phone rings, but freezes when I answer the call. The only thing that helps is removing the battery.
I run version 100.4.20 RM-244

However, I have it working all well via sip.xs4all.nl. Both incoming and outgoing calls :-/

Nokia E51

by ABU NUHA on Wednesday 19 of March, 2008 [18:25:40 UTC]
I have Nokia E51, Itis settings are same like E65.

But I could not connect to my SIP server or I couldnt use voip Phone yet.
My Wlan is working fine and connecting all servers.

I am expecting a detailed reply in this thread..

Rgds

N95 - plus sign in international calls

by Hans Gunnarsson on Wednesday 12 of March, 2008 [16:06:10 UTC]
I have a Nokia N95, and it works really good with asterisk when I follow these instructions. <br><br>

However, many of my phone numbers in the address book starts with a plus sign followed with the<br>
international code for my country and then the telephone number. <br>
Asterisk doesn't seem to like this. <br><br>

Anyone found a workaround?

N95 - settings?

by Phil Reynolds on Tuesday 04 of March, 2008 [11:49:22 UTC]
I have my N95 working fine when it is in range of my wireless network (and, strangely, also my sister's!).

However, I have now fetched the full settings tool from Nokia and am wondering if there is any way I can set it up to work over WCDMA and possibly on other wireless networks if a STUN server will get round it - I am aware that will not always do it but it may help.

I am not sure why, but nothing happens at the Asterisk end when I try over WCDMA.

N95 - settings?

by Phil Reynolds on Tuesday 04 of March, 2008 [09:58:40 UTC]
I have my N95 working fine when it is in range of my wireless network (and, strangely, also my sister's!).

However, I have now fetched the full settings tool from Nokia and am wondering if there is any way I can set it up to work over WCDMA and possibly on other wireless networks if a STUN server will get round it - I am aware that will not always do it but it may help.

I am not sure why, but nothing happens at the Asterisk end when I try over WCDMA.

Nokia E51 (even through NAT)

by Lucius on Thursday 03 of January, 2008 [00:57:12 UTC]
Nokia E51 also works with Asterisk.
I tested it over LAN and WAN connections and I can report that E51 works well even through NAT.
Btw, if you have a dynamic WAN IP address (like I have) make sure you add an "externhost" directive in your sip.conf. After some playing around I got this solution:

In sip.conf I added the following:

\general\
externhost=yourhost.dyndns.org
externrefresh=120
localnet=192.168.1.0/255.255.255.0

"externhost" and "externrefresh" work on Asterisk 1.2.x. "externrefresh" tells asterisk how often (in seconds) it will resolve the "externhost". "localnet" is used to define your LAN IP addresses (and/or other addresses that do not need NAT).

The only annoyance I found on E51 is that I have to "force connect" wireless before I try the SIP connection. I have to "Start web browsing" on a wireless connection, open some web page (to force the device to connect to wireless), then exit using the home button (without closing the browser) if I want to make a SIP connection. Otherwise my conenction to Asterisk always fails. I guess it has to have a wireless connetion already established prior to conencting via SIP. I don't know if this is by design or not, but I found no other way to get around it. If anyone knows how to establish a wireless connection on E51 without having to open the broswer, please tell.

VoIP Security Solutions

by jenniferhan on Thursday 27 of December, 2007 [07:00:49 UTC]
SpeedVoIP is a professional VoIP Security and VoIP anti blocking solutions provider.
The core solution for VoIP Security and VoIP anti-blocking is VGCP (VoiceGuard Control Protocol).
It can work with any 3rd-party Softphone / ATA / Gateway / IP Phone / IADs and SIP proxy or server.
It can work in the way similar to that of SOHO router, but it only encrypts and decrypts SIP and RTP packets on link layer, not to handup these packets to IP stack for forwarding while bypassing other data packets originating from SIP terminals. In this scenario, peak throughput and minimal CPU overhead can be easily achieved.

VoiceGuard can real-time incorporate light-weight traffic for puzzling and bypassing VoIP blocking system without consuming more bandwidth and compromising voice quality. Even in some circumstance, VoiceGuard can simulate traffic behavior of universal data networking protocol such as OICQ, MSN and so on.

For more information, please refer to: http://www.speed-voip.com/index-36.html

Andy
xd.wong@speed-voip.com
andywong-01@hotmail.com

N95 and asterisk problems

by Rodrigo Rocha on Thursday 04 of October, 2007 [07:23:42 UTC]
In my case I have a N95 register in my asterisk box. The connection it's fine and work. But I get this message on console every time I connect the N95 on asterisk.

Got SIP response 400 "Bad Request" back from 192.168.5.10

Where 192.168.5.10 is my N95.

If a call from another extension to my N95 this ring normally but if I try to call from my N95 I get that message.

Any one have any idea ?

Please update this page with new information, just login and click on the "Edit" or "Add Comment" button above. Get a free login here: Register Thanks! - support@voip-info.org

Page Changes | Comments

Sponsored by:
Terms of Service Privacy Policy
© 2003-2008 VOIP-Info.org LLC

Powered by bitweaver