Topic: Remote Nokia N95

[Graham]

I'm trying to use the internet phone built into the Nokia N95 to connect to our VOIP server, I’ve can use X-Lite from a remote PC with no issues but when using the N95 it fails to connect.

Has anymore tried this before and got it working.

Regards,
Graham Spratt

[Graham]

Forgot to say I can get the Nokia N95 to connect directly to a sipgate account.

[SARK devs]

yes it works.  Trouble is I can't find my notes on how to do it.  The Asterisk side is dead easy - just set it up as general sip and set it as "remote". 

The Nokia side is quite tricky if I remeber correctly, I'll see if I can find those notes...

Best

S

[SARK devs]

here you go.  This looks about right...

Profile Name: Asterisk SARK[or whatever you want]
Service profile: IETF
Default access point: [set up and put your Home access point here]
Public user name: sip:222@asterisk.server.com ["222"=your extension, + your ast server]
Use compression: No
Registration: When needed
Use security: No
Proxy server: [click]
Proxy server address: sip:asterisk.server.com [again your asterisk server]
Realm: asterisk [this stumped me for awhile - this is default, unless you've changed this]
User name: 222 [ie. your extension, same as above]
Password: 999 [your "secret" code defined from your extensions]
Allow loose routing: Yes
Transport type: UDP
Port: 5060
Registrar server: [click]
Registrar serv. addr: sip:Asterisk
Realm: None
User name: None
Password: None
Transport type: UDP
Port: 5060

[Graham]

Can't seem to get it working:

What is Realm and where would it be set.

[SARK devs]

realm is the SIP realm (asterisk uses "asterisk").

It should be one of the fields you fill out in the phone when you set up the SIP  stack.

 

[Graham]

Still can't get it work, below is my config

Profile Name: Asterisk
Service profile: IETF
Default access point: Network Name
Public user name: sip:4000@server.com
Use compression: No
Registration: When needed
Use security: No

Proxy server: [click]
Proxy server address: sip:server.com
Realm: asterisk
User name: 4000
Password:*******
Allow loose routing: Yes
Transport type: UDP
Port: 5060

Registrar server: [click]
Registrar serv. addr: sip:Asterisk
Realm: None
User name: None
Password: None
Transport type: UDP
Port: 5060

type=friend
username=4000
secret=********
mailbox=4000
host=dynamic
qualify=3000
canreinvite=no
context=internal
callerid="4000" <4000>
pickupgroup=1
callgroup=1
disallow=all
allow=alaw
allow=ulaw

[SARK devs]

the proxy server address looks wrong.  It should be your external domain name (if you have one) or your external IP address.  Also I think your registrar server should be set the same.  Finally, I think on our test phone (which I don't have here) we also set the registrar user and password to the extension and secret (same as for the proxy).

You appear not to have set the extension as external (looking at the sip.conf settings).  You will need to set this for remote operations.

Kind Regards

[SARK devs]

found the original post with our settings in...

http://forums.contribs.org/index.php?topic=38735.msg176265#msg176265

[Graham]

Tried that also still not connecting, new settings below:

Profile Name: Asterisk
Service profile: IETF
Default access point: Network Name
Public user name: sip:4000@server.goes.here
Use compression: No
Registration: When needed
Use security: No

Proxy server: [click]
Proxy server address: sip:server.goes.here
Realm: asterisk
User name: 4000
Password:*******
Allow loose routing: Yes
Transport type: UDP
Port: 5060

Registrar server: [click]
Registrar serv. addr: sip:server.goes.here
Realm: asterisk
User name: 4000
Password:*******
Transport type: UDP
Port: 5060

asterisk settings

type=friend
username=4000
secret=****************
mailbox=4000
host=dynamic
qualify=3000
canreinvite=no
context=internal
callerid="4000" <4000>
pickupgroup=1
callgroup=1
disallow=all
allow=g729
nat=yes

[SARK devs]

well at least it looks liike ours now.

What do you see at the asterisk console when you attempt to register the phone?

also, you can try running a packet trace on your asterisk box to see if the phone is attempting to communicate...

Code: [Select]

yum install wireshark
tethereal -R sip -i {eth0/eth1} -f "host {ip address of the phone}"

[groutley]

Hi,
 not sure if this is related to sprattgrahams issue..
I have a Nokia E65 and I assume the SIP phone works the same as a N95.
My E65 has been working happily, right up to this evening when I upgraded SAIL to 2.2.1-651
previously I was running -640

after the upgrade to -651 the phone will not connect, and I see the following on the asterisk console as it attempts

Code: [Select]

[Jul 22 19:42:36] WARNING[6869]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol  } ¡6 } ¡½
[Jul 22 19:42:39] WARNING[6869]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol  } ¡6 } ¡½
[Jul 22 19:42:45] WARNING[6869]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol  } ¡6 } ¡½
[Jul 22 19:42:57] WARNING[6869]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol  } ¡6 } ¡½
[Jul 22 19:43:13] WARNING[6869]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol  } ¡6 } ¡½
[Jul 22 19:43:29] WARNING[6869]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol  } ¡6 } ¡½


[SARK devs]

I haven't seen these messages before but Digium Bug tracker suggests it may have been a bug in Asterisk 1.4.19.
Which release of asterisk do you have?

[groutley]

Code: [Select]

[root@l1nuxsvr ~]# rpm -q asterisk
warning: only V3 signatures can be verified, skipping V4 signature
asterisk-1.4.18.1-59.el4

Just updated to asterisk-1.4.21.1-64.el4

but still have the same errors on asterisk console and the Nokia SIP phone is "Unable to connect"

[groutley]

A wireshark trace gives the following....

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 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
  3.066796 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
  9.138037 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
 21.195069 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
 37.274363 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
 53.351243 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
 69.414820 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
 85.471164 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
101.544919 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
117.604870 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
133.669569 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
149.714726 192.168.37.29 -> 192.168.37.251 SIGCOMP/SIP Request: REGISTER sip:l1nuxsvr.routley.homeip.net;transport=UDP
12 packets captured