Topic: Remote Nokia N95

[SARK devs]

Then I'm afraid I don't know.  We don't have the issue here so I guess you will have to do a bit of detective work to find out what is causing the problem.  You can back sail off to an earlier release (just remove the existing version with "rpm-e sail")  or attempt to track which phone is causing the problem (we are only guessing it is the Nokia at this point).  If you turn the Nokia off does the problem go away?  Have you changed anything else?.  Standard debugging I guess.

Kind Regards

[groutley]

Hi Jeff,
  in this case it is my bad !! (sorry to have wasted your time)
I looked at this thread yesterday and wondered if I could help, as my phone was working fine.
While looking at my phone settings, Thought (my 1st mistake) what happens if I turn compression on.
Hmm I guess I know now..  Yes setting compression to 'no' again sorted it.

Although..  I do get an error when it does register, and have always got this error..

Code: [Select]

Extension Changed 5019[extensions] new state Unavailable for Notify User Glen
    -- Registered SIP '5019' at 192.168.37.29 port 5060 expires 180
    -- Saved useragent "Nokia RM-208 2.0633.65.01" for peer 5019
 Extension Changed 5019[extensions] new state Idle for Notify User Glen
[Jul 22 21:32:28] NOTICE[7343]: chan_sip.c:12669 handle_response_peerpoke: Peer '5019' is now Reachable. (151ms / 2000ms)
    -- Got SIP response 400 "Bad Request" back from 192.168.37.29
So it seems the Nokia sends a Bad request?  or is this request being interpretted wrong due to a SAIL setting for the extn ?

Here is a trace of registration..  don't know if it helps understand the bad request though,

Code: [Select]

[root@l1nuxsvr ~]# tethereal -R sip -i eth0  -f "host 192.168.37.29"
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
  0.000000 192.168.37.29 -> 192.168.37.251 SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
  0.000132 192.168.37.251 -> 192.168.37.29 SIP Status: 100 Trying    (1 bindings)
  0.000166 192.168.37.251 -> 192.168.37.29 SIP Status: 401 Unauthorized    (0 bindings)
  0.177820 192.168.37.29 -> 192.168.37.251 SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
  0.178001 192.168.37.251 -> 192.168.37.29 SIP Status: 100 Trying    (1 bindings)
  0.229222 192.168.37.251 -> 192.168.37.29 SIP Request: OPTIONS sip:5019@192.168.37.29;transport=UDP
  0.229285 192.168.37.251 -> 192.168.37.29 SIP Status: 200 OK    (1 bindings)
  0.229394 192.168.37.251 -> 192.168.37.29 SIP Request: NOTIFY sip:5019@192.168.37.29;transport=UDP
  0.380837 192.168.37.29 -> 192.168.37.251 SIP Status: 200 OK
  0.449795 192.168.37.29 -> 192.168.37.251 SIP Status: 400 Bad Request
10 packets captured
It doesn't cause a problem,  just me not liking messages like that !!

[SARK devs]

Our Siemens units do somethings similar.  The phone is asking for something that asterisk can't/won't provide.  I've never tracked it down completely because I found a report on the Digium site which said it was benign.

Glad you sorted the phoe out tho'

Best

[Gert]

I got my Nokia E90 working perfectly fine through local wifi and through GPRS (3G/HSDPA), but i cannot seem to get it working through another ADSL connection with a sme server acting as gateway. con config on the fhone is as follows:

Code: [Select]

Profile name: Profile
Service profile: IETF
Default access point: {my wifi access point}
Public user name: sip:5000@mydynamichostname
Use compression: no
Registration: When needed
Use security: no

Proxy server
{all settings blank}

Registrar server
---------------
Regstrar server address: sip:mydynamichostname
Realm: asterisk
User name: 5000
Password: {mypassword}
Transport type: Auto
Port: 5060

[arne]

Transportable SIP clients can never be very usable for traveling, using wireless zones, etc because of the nat/router unfriendly design of the SIP protocol.

The protocol that actually does work well for such use is the native Asterisk IAX2 protocol. For traveling I use a small PC with windows XP and Zoiper. My Nokia mobile SIP client works in something like 10 % of the hotspots. My Zoiper IAX2 client works in something like 98 % of all hotspots. (and I use the default IAX2 port and UDP 53 as alternative ports for logon.)

I whish it was a IAX2 client for Nokia, but I don't think there is. I think ther is one for Windows based mobiles, but I have never tried it. The Zoiper client of Slax Linux also works pretty well. I have tested the last one.

[arne]

Here is one of my old treads on this subject:
http://discussion.forum.nokia.com/forum/showthread.php?p=382599

I tested the Fring client at that time, but that version of Fring had terrible performace on my old E61, so it was not really usable.

I just tested Fring today, and it was qute much bether. I could connect to the sip server without a problem, and the sound quality had improved since last time tested. For reasons I don't know it worked quite ok to call out via sip but not to receive via sip.

Actually I think SIP via Fring is not really SIP from end to end, but it is sip to the Fring gateway and from the Fring gateway and to your mobile it is "Fring protocol". But I think the "Fring protocol and comunication concept" has bether performace trough nat routers (and firewalls) than the SIP protocol, so I will give it a try again ..  http://www.fring.com/

By the way, using your sip server with Fring will not require the configuration of the Nokia sip client but a quite more easy to set up "Fring sip client". (Because of reasons that is already mentioned.)