N95 and SIP

Forums › Legacy mobile platforms (Windows Mobile, Palm OS, Web OS, Symbian, Meego, Blackberry) › N95 and SIP

1 | 2

bigal_nz

635 posts

Ultimate Geek
Inactive user

#104090 10-Jan-2008 21:13

I got the built in SIP working with the N95, but incoming calls dont work with 2talk.

Talking to the 2talk people its possible because of a routing issue with Vodafone? For the incoming calls 2talk report seeing the packets go off to Vodafone, but nothing coming back....

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#104098 10-Jan-2008 21:42

What Vodafone APN are you using - a NAT one or non NAT?

SIP and NAT just don't get along very well sometimes.

bigal_nz

635 posts

Ultimate Geek
Inactive user

#104106 10-Jan-2008 21:54

VF NZ Internet is what I used - is that NAT'ed?

bigal_nz

635 posts

Ultimate Geek
Inactive user

#104436 12-Jan-2008 21:24

I changed my AP name to Internet which allows incoming connections but it still doesnt work.

The 2talk guys traced a inbound call and they could see a "TRYING" reply from the phone, but it never got further than that and my phone never rang.

They could also ping my phone, so it was clearly capable of accepting incoming initated sessions.

I even tried in on a wireless AP at home, and still no inbound calls, so it would appear to be a issue with the SIP on N95 :-(

alas....

-Al

paradoxsm

3000 posts

Uber Geek

Trusted

#104457 12-Jan-2008 23:59

You need to set up an additional profile for incoming calls to work, it should be on the 2talk forums.

I was hoping to stick up a quick list here but my hard drive (and entire old computer) has just failed and while i'd backed up my important stuff, It'd put the N95 stuff as lower priority and it got trashed :-(

peejayw

1841 posts

Uber Geek

#104465 13-Jan-2008 07:06

bigal_nz: VF NZ Internet is what I used - is that NAT'ed?

I am using VF NZ Internet as well and this works when in a 3g area but fails when outside 3g.
I cant see anyhere on the phone to edit thes settings, I have
VF NZ Internet
VF NZ Gateway
VF NZ Pxt
Connection
and my WiFi AP

Anyone know which is the correct (non-NAT?) one to use?

I'm supposed to respect my elders, but it's getting harder and harder for me to find one now.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#104469 13-Jan-2008 08:36

bigal_nz: I changed my AP name to Internet which allows incoming connections but it still doesnt work.

The 2talk guys traced a inbound call and they could see a "TRYING" reply from the phone, but it never got further than that and my phone never rang.

They could also ping my phone, so it was clearly capable of accepting incoming initated sessions.

I even tried in on a wireless AP at home, and still no inbound calls, so it would appear to be a issue with the SIP on N95 :-(

alas....

-Al

Actually based on this , it actually looks more like a phone setup issue, as you said the the "Trying" came back from the phone so it can't be a routing issue as if it was you would not have got the "Trying " at all as well as the fact the device has actually registered. A Ping dosn't check the SIP connection so is a bit of a red heering.

For a SIP call the "Invite" is sent to the phone a "Trying" will automatically be sent if there is a SIP agent at the device able to respond, by the looks of this the device is responding but cant locate the device to ring it with a 183 "Ringing"

This is an example of a Call Setup, what you should note is that the Trying is sent within .003 of a second of receiving a Invite, this means that the device has seen the sip message and now needs to alert the phone to ring, in this case it occurs after 1.78 seconds the phone is now ringing, if your device is sending the trying but not the ringing it is most probably your setup I'm afraid,

To find out what is actaully wrong I would need to see the registration trace and the inbound call trace to tell you what is exactly wrong.

Call Flow

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

Tradepub

Free professional, reference and technical white papers (affiliate link).

bigal_nz

635 posts

Ultimate Geek
Inactive user

#104470 13-Jan-2008 08:43

paradoxm:

If you got into VZ NZ Internet, you will see access point name: vodafone.net.nz - change this to "Internet" it should be about the 3rd settign down.

Its Under Settings->Connections->Access Points
Also change it under Settings->Cnnections->Packet Data

You shoudl then be able to ping (incomig conection) your phone from your PC.

-Al

freitasm

BDFL - Memuneh
79268 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#104471 13-Jan-2008 08:48

Here is a sticky post with a list of Vodafone APNs including restrictions and private addressing.

bigal_nz

635 posts

Ultimate Geek
Inactive user

#104491 13-Jan-2008 10:54

Well it maybe a incorrect setting on the phone. Heres my settings FWIW:

Profile Name: 2Talk
Service Profile: IETF
Default Access Point: VF NZ Internet
Public User name : sip:0997492xx@2talk.co.nz
Use Compression: No
Registration: When Needed
Use Security: No

PROXY SERVER
Proxy Server Address: sip:2talk.co.nz
Realm: 2talk.co.nz
User Name: 0997492xx
Password: xxxxxx
Allow Loose Routing: Yes
Transport Type: Auto
Port: 5060

REGISTRAR SERVER
Same as Above

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#104512 13-Jan-2008 13:07

Try changing the transport type to UDP and see if that does anything.

bigal_nz

635 posts

Ultimate Geek
Inactive user

#104524 13-Jan-2008 15:54

Tried both TCP and UDP - could only login with UDP, and still no incoming calls :-(

bigal_nz

635 posts

Ultimate Geek
Inactive user

#107753 31-Jan-2008 12:03

Does this trace help anyone with why my phone is not accepting incoming calls?

No.	Time	Source	Destination	Protocol	Info
1	0	192.168.1.142	202.180.76.161	SIP	Status: 100 Trying
2	0.727412	192.168.1.100	213.8.162.208	SSL	Continuation Data
3	1.370106	192.168.1.100	213.8.162.208	TCP	donnyworld > https [ACK] Seq=97 Ack=71 Win=65255 Len=0
4	1.912734	202.180.76.161	192.168.1.142	SIP	Request: OPTIONS sip:099749271@192.168.252.1:5060
5	2.063326	192.168.1.142	202.180.76.161	SIP	Status: 200 OK
6	6.84286	192.168.1.100	147.8.27.216	TCP	proshare-mc-1 > 22985 [PSH, ACK] Seq=1 Ack=1 Win=64216 Len=4
7	16.35091	202.180.76.161	192.168.1.142	SIP	Request: CANCEL sip:099749271@192.168.252.1:5060
8	16.38392	192.168.1.142	202.180.76.161	SIP	Status: 200 OK
9	16.40539	192.168.1.142	202.180.76.161	SIP	Status: 487 Request Terminated
10	16.44084	202.180.76.161	192.168.1.142	SIP	Request: ACK sip:099749271@192.168.252.1:5060
11	21.74735	192.168.1.100	207.46.110.84	MSNMS	PNG
12	22.09193	192.168.1.100	207.46.110.84	TCP	vaultbase > msnp [ACK] Seq=6 Ack=9 Win=64392 Len=0
13	22.87604	192.168.1.110	66.186.59.50	IRC	Request
14	22.87616	192.168.1.110	66.186.59.50	TCP	entp > 6667 [FIN, ACK] Seq=8 Ack=1 Win=17164 Len=0
15	23.07051	66.186.59.50	192.168.1.110	TCP	6667 > entp [FIN, ACK] Seq=1 Ack=8 Win=2920 Len=0
16	23.07055	192.168.1.110	66.186.59.50	TCP	entp > 6667 [ACK] Seq=9 Ack=2 Win=17164 Len=0
17	24.60672	192.168.1.110	66.186.59.50	TCP	entp > 6667 [FIN, ACK] Seq=8 Ack=2 Win=17164 Len=0
18	24.74717	66.186.59.50	192.168.1.110	TCP	6667 > entp [ACK] Seq=2 Ack=9 Win=2919 Len=0

1 | 2