E65 SIP connection problem

[Razzle]

I'm trying to connect my E65 to the sipgate.de VoIP service using the built-in client, however it seems to be unable to establish a connection. I started investigating the issue a bit myself and while I couldn't pin down the cause of the problem due to lack of access to a tcpdump-style application for S60 to confirm that UDP packages don't get lost anywhere after passing the WLAN-router, I do think that the problem is to be looked for on the device itself.
I captured packages on the router's WLAN device in order to take a look at the communication between phone and sipgate.de and the results show that a packages sent by the E65 do indeed reach the sipgate server, however the response is either not or incorrectly processed by the SIP implementation on the phone.
To initiate a connection, a REGISTER request is sent to the server but apparently the response, a "401 Unauthorized", is not processed but instead the REGISTER request is repeated in increasing intervals (3s, 6s, 12s,..). According the the RFC, the device should resend the request with credentials added and CSeq increased, however nothing inside the request gets changed for the next send.
The response packages are sent to the phone over the WLAN device on the router so I assume the problem doesn't lie here.

I'm a bit out of ideas of how to fix this issue without debugging access to the SIP application on the E65 but maybe there's something I'm missing and someone here has a solution for the problem.
Would be great since VoIP was one of the main reasons for me to buy this phone

Part of the capture:

No.     Time        Source                Destination           Protocol Info
      1 0.000000    84.191.201.140        217.10.79.9           SIP      Request: REGISTER sip:sipgate.de;transport=UDP

Frame 1 (470 bytes on wire, 470 bytes captured)
Linux cooked capture
Internet Protocol, Src: 84.191.201.140 (84.191.201.140), Dst: 217.10.79.9 (217.10.79.9)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
    Request-Line: REGISTER sip:sipgate.de;transport=UDP SIP/2.0
    Message Header
        Via: SIP/2.0/UDP 84.191.201.140:5060;branch=z9hG4bKetou3ao40lhc6glt0g5ga31;rport
        From: <sip:[removed]@sipgate.de>;tag=4vce3auojphc7aka0g5g
        To: <sip:[removed]@sipgate.de>
        Contact: <sip:[removed]@84.191.201.140:5060;transport=UDP>;expires=3600
        CSeq: 867 REGISTER
        Call-ID: 9LXxGX1PoIcsLwgb1pDkI13Q3z94AA
        User-Agent: Nokia RM-208 1.0633.18.01
        Max-Forwards: 70
        Content-Length: 0

No.     Time        Source                Destination           Protocol Info
      2 0.072174    217.10.79.9           84.191.201.140        SIP      Status: 401 Unauthorized    (0 bindings)

Frame 2 (463 bytes on wire, 463 bytes captured)
Linux cooked capture
Internet Protocol, Src: 217.10.79.9 (217.10.79.9), Dst: 84.191.201.140 (84.191.201.140)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
    Status-Line: SIP/2.0 401 Unauthorized
    Message Header
        Via: SIP/2.0/UDP 84.191.201.140:5060;branch=z9hG4bKetou3ao40lhc6glt0g5ga31;rport=5060
        From: <sip:[removed]@sipgate.de>;tag=4vce3auojphc7aka0g5g
        To: <sip:[removed]@sipgate.de>;tag=b11cb9bb270104b49a99a995b8c68544.f30e
        CSeq: 867 REGISTER
        Call-ID: 9LXxGX1PoIcsLwgb1pDkI13Q3z94AA
        WWW-Authenticate: Digest realm="sipgate.de", nonce="45e5e7ebf6d3cc7e078e8295ba71a9092ea68bc7"
        Content-Length: 0

No.     Time        Source                Destination           Protocol Info
      3 3.016895    84.191.201.140        217.10.79.9           SIP      Request: REGISTER sip:sipgate.de;transport=UDP

Frame 3 (470 bytes on wire, 470 bytes captured)
Linux cooked capture
Internet Protocol, Src: 84.191.201.140 (84.191.201.140), Dst: 217.10.79.9 (217.10.79.9)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
    Request-Line: REGISTER sip:sipgate.de;transport=UDP SIP/2.0
    Message Header
        Via: SIP/2.0/UDP 84.191.201.140:5060;branch=z9hG4bKetou3ao40lhc6glt0g5ga31;rport
        From: <sip:[removed]@sipgate.de>;tag=4vce3auojphc7aka0g5g
        To: <sip:[removed]@sipgate.de>
        Contact: <sip:[removed]@84.191.201.140:5060;transport=UDP>;expires=3600
        CSeq: 867 REGISTER
        Call-ID: 9LXxGX1PoIcsLwgb1pDkI13Q3z94AA
        User-Agent: Nokia RM-208 1.0633.18.01
        Max-Forwards: 70
        Content-Length: 0

[...]

[Razzle]

Update:
The same behaviour can be seen when trying to connect to internetcalls.com
While testing this additional VoIP service, I encountered another weird issue:
when there is more than one SIP profile defined, only the 1st one comes as far as described above, any other profile added at a later point doesn't even send any of the UDP messages but simply returns with "unable to connect to the connection network".

[madusa]

Update:
The same behaviour can be seen when trying to connect to internetcalls.com
While testing this additional VoIP service, I encountered another weird issue:
when there is more than one SIP profile defined, only the 1st one comes as far as described above, any other profile added at a later point doesn't even send any of the UDP messages but simply returns with "unable to connect to the connection network".

Razzle, I'm facing the same problem. I'm able to do VoIP over EGPRS but as soon as I try and do it over my Netgear WGT624 router I only get "unable to connect to the connection network" the biggest reason for me to buy the phone was to be able to use VoIP over my WiFi connection , now I'm not sure what to do ? Have tried all types of setting with UPnP on my router, Port Forwarding to 5060 abd all combinations of SIP setups but still what I get is "unable to connect to the connection network" !

In case you come across a solution for this problem, do help out a fellow user. This phone was just launched in 'India and I was probably the 1st few to buy one, my E65's Firmware version is 1.0633.18.01 dated 11/01/07 RM-208; is a new firmware out may be that has addressed this issue ?

Lets keep posted !

Adios !

[Los_Angeles]

My friends Razzle and madusa, i have the E65 and it's great, there is nothing wrong with your phone, i just solve the "unable to connect to the connection network" problem. All you have to do is fill ALL the fields in the profile in the sip setting section, my problem was that i did'nt fill the REGISTRAR SERVER information, but when i use the same server name that the proxy server and fill all the fields info it works, i use it to register to SIPPHONE.COM and it works great.

I hope this can help you.

[madusa]

My friends Razzle and madusa, i have the E65 and it's great, there is nothing wrong with your phone, i just solve the "unable to connect to the connection network" problem. All you have to do is fill ALL the fields in the profile in the sip setting section, my problem was that i did'nt fill the REGISTRAR SERVER information, but when i use the same server name that the proxy server and fill all the fields info it works, i use it to register to SIPPHONE.COM and it works great.

I hope this can help you.

Thanx for th input LA ! I've tried that as well, the only way the router is letting a SIP connection form my phone is by shutting off the SPI firewall (not recommended) on the router, till now thats the only way my phone's SIP connection goes through and connects via my Netgear router. Will upgrade the firmware and c how it goes.

[Razzle]

My E65 is currently being repaired (faulty display) so I don't really have any big updates but I'm pretty sure I had filled in all details and it still didn't work.
In fact, I had set up an asterisk server in the local network and tried to make it connect to that to rule out the router firewall as a possible issue but I encountered exactly the same problem there.

I suspect that it might be the firmware which is branded by my network provider, I will try and see if I can get an unbranded version once I have my phone back.

[nly]

Excellent error report, thank you. In many cases the SIP signaling logs of this kind are the best way to find the reason (but unfortunately not in this case).

Due there is re-transmissions of the initial REGISTER request the client's SIP stack does not get the 401 response (or does not accept it).

Most likely reasons are that there is a SIP-ALG (Application level gateway) inside the WLAN access router and it

a) somehow corrupts the response so that it's not seen being related to the REGISTER request by E65

b) sends the response to wrong address or port.

If there is no NAT on the route, just WLAN access point, then the above does not apply.

Due there is 401 response (and it looks fine), the SIP settings in the client are most likely correct.

Could you try it under some other WLAN access router (to figure if it's the reason)? Some access routers also have a possibility to disable the SIP-ALG functionality in their settings and it might help - depends on the SIP server's capabilities for NAT traversal, disabling ALG may also cause the 401 response to be totally lost.

Upgrading the access router's firmware may also help, couple of clear malfunctions have been reported, but they have typically been fixed in later releases.

[madusa]

Ok, finally found a workable solution to Netgear WGT624 v3 router and Nokia E65 "Connection error" issue, if I disable the SPI Firewall (not recommended) on the router, my SIP connection goes through and works perfectly alright, but I don't want to disable to SPI, tried setting the phone's IP as DMZ server, but that too did not resolve teh issue, only scenario that works for me is disabling the SPI firewall.

Any work around ? Will try the firmware upgrade as suggested by nly, thanx man !

[Razzle]

My E65 is finally back from repairs and I managed to get hold of a different router (Fritzbox, can't remember model name right now, will update later) which allows me to connect and use the VOIP services without problems or special settings. I will try and see if I can find the reason within my Linksys WRT54G router and will post updates here.

[cmreddy]

My friends Razzle and madusa, i have the E65 and it's great, there is nothing wrong with your phone, i just solve the "unable to connect to the connection network" problem. All you have to do is fill ALL the fields in the profile in the sip setting section, my problem was that i did'nt fill the REGISTRAR SERVER information, but when i use the same server name that the proxy server and fill all the fields info it works, i use it to register to SIPPHONE.COM and it works great.

I hope this can help you.

Hi LA,

I got my E65 couple of days ago.. I am trying to connect to Sipphone.com desperately. I have a SPA 3000 connected to Sipphone.com since 3 yrs. But with E65, i am having quite some difficulty.. Could you plz put in here the parameters.. I am finding it difficult with the "REALM". I dont know what to put in here for Proxy settings and Registrar settings.. Any help is greatly appreciated..
regards,
Cmreddy

[Los_Angeles]

Hi Cmreddy, i have a SPA 3102 it's a great device.

In the E65 in the menu > tools > setting > connection > SIPsetting
- create a new profile and give it a name (like sipphone)
-service profile is IETF
- define the default access point
- in the public user name write somethink like sip:1747xxxxxx@proxy01.sipphone.com where 1747xxxxxx is your number
-use compression No
-Registration: When needed
- Use security: No

-Proxy server
Proxy server address sip: proxy01.sipphone.com
Realm proxy01.sipphone.com
user name: Your phone number (like 1747xxxxxx)
password: your account password
allow loose routing No
Transport type UDP
Port: 5060

- Registrar Server
Proxy server address sip: proxy01.sipphone.com
Realm proxy01.sipphone.com
user name: Your phone number (like 1747xxxxxx)
password: your account password
allow loose routing No
Transport type UDP
Port: 5060

I hope this can help you, those are the setting in my E65 but be careful because this phone won't connect to the SIP service on any access point, mine just work in my home (Dlink Dl-524), there is something in the firewall that block the registration process,

good luck

[alexmob]

Hello.

I'm fighting with my new E65 to let voip calls go!
nothing to do: even using the suggested parameters registration does not work and does not arrive to the sip server also.

I have a linksys router+dlink access point. no firewall is configured and voip services with other devices work fine.

any help?

regards

[Los_Angeles]

I've try so many things to get the e65 working with any Access point that i decide to try FRING, (download via SMS from www.fring.com) and it finally works, now i'm able to register at my account in sipphone.com and simultaneously to my account in skype, MSN and Google talk are avalaible too, the most important thing is that i can connect to any access point and register to my SIP account when using FRING.

I think that Fring does'nt use the SIP stack in the symbian, i think that it use some trick and it register in a remote server, it does'nt use any sip protocol in the e65.

It is'nt all that i expect but it work's.

And Fring will work with many symbian S60 phones, WIFI enabled or via 3G

I hope this can help

[alexmob]

Thanks a lot. Fring was my first alternative to the built-in sip client.
Anyway tonight I was able to let the built-in client work, at least in my environment.
There was a problem with my router, since I have a Linksys sip phone up and running that listens on port 5060. The built-in client wants to do the same, and the router does not remap the inside port properly. I changed sip port on the linksys (where it's possible to do it) and let the E65 goes over 5060.
Some other tips about the sip configuration and everything started working fine!!

bye

[cmreddy]

Hi Cmreddy, i have a SPA 3102 it's a great device.

I hope this can help you, those are the setting in my E65 but be careful because this phone won't connect to the SIP service on any access point, mine just work in my home (Dlink Dl-524), there is something in the firewall that block the registration process,

good luck

Hi LA,

thank you very much for the info.. Surprisingly i tried all possible variations of the settings mentioned by you before.. But it didnt connect.. But tell you what.. it connected in a snap.. i am still not able to hear any voice and stuff like that.. but i think i will manage it.. thank you very much..
regards,
Cmreddy.

Now i need to find a way to make my SPA 3000 and E65 work together.. lets see..