×

Discussion Board

Results 1 to 15 of 20

Hybrid View

  1. #1
    Registered User
    Join Date
    Jun 2008
    Posts
    19

    Exclamation Problems with incoming VoIP 3.x calls

    Hi fellows,

    there is a very annoying problems with all VoIP Release 3.x phones – I've tried with E52, E55, E72, E75, N97, N97 mini.

    If you register to ITSP normally everything is OK – you can make both outgoing and incoming VoIP calls.

    The situation is different when you register a Nokia VoIP 3.x phone to an IP PBX, i.e. Siemens, Aastra, Panasonic, Asterisk and probably other SIP servers. You can make outgoing calls, but you an not receive any incoming call – you get either busy or other error.

    If you look on the SIP messages you will see that the phone returns SIP error 407: Not found. Trying to debug with Wireshark you see that in some cases the SIP invite message is sent to another port (not 5060) for some reason.

    This happens anywhere – in any 'test' lab, GPRS, etc., so it is not a problem of a specific LAN (router, DHCP) or IP PBX. It seems like the VoIP settings are fake.

    Does anybody met the same problem or have any idea how to overcome it?

    Best regards,
    Edi.

  2. #2
    Registered User
    Join Date
    Oct 2008
    Posts
    1

    Re: Problems with incoming VoIP 3.x calls

    I have the same problem.

    Can I help me?

    Thanks

  3. #3
    Registered User
    Join Date
    Jul 2009
    Posts
    1

    Re: Problems with incoming VoIP 3.x calls

    I have the same problem...

  4. #4
    Registered User
    Join Date
    Feb 2010
    Posts
    5

    Re: Problems with incoming VoIP 3.x calls

    I have the same problem, already posted a new thread.

    Which INVITE do you mean, is sent to another port, not 5060? The one to the Nokia? This one is not supposed to go to 5060 but to the contact port(as the Nokia is the client, which might, no... WILL be behind a PAT)

  5. #5
    Registered User
    Join Date
    Jun 2008
    Posts
    19

    Re: Problems with incoming VoIP 3.x calls

    Hi,

    this is a wireshark dump of N958GB and E52 in a same conditions. Both phones can make outgoing VoIP calls, but only N95 can receive VoIP calls. The problem is not related to PAT (I've tried wothout PAT).

    If you register to ITSP – I've tried several – normally everything is OK – you can make both outgoing and incoming VoIP calls.

    The situation is different when you register a Nokia VoIP 3.x phone to an IP PBX, i.e. Siemens, Aastra, Panasonic, Asterisk and probably some other SIP servers. You can make outgoing calls, but you an not receive any incoming call – you get either busy or other error.

    If you look on the SIP messages you will see that the phone returns SIP error 404: Not found. Trying to debug with Wireshark (please see attached file and note below) you can see that in some cases the SIP invite message is sent to another port (not 5060) for some reason. There is no such problem on Nokia VoIP 2.x phones – like E51, E65, E66, E71, N95, etc.

    This happens anywhere – in any 'test lab', GPRS, etc., so it is not a problem of a specific LAN (router, DHCP) or IP PBX. It seems like the VoIP settings are fake.

    Please send me an e-mail address to edikojsi@yahoo.com to post you a wireshark capture or download it from:

    http://4storing.com/0tpmu4/8105692ce...0fd73bf1b.html

    Note that sip user '11' is the E52, '77' is the N95, '63' is another proprietary phone (Panasonic).
    The invite message to E52 is sent to port 5060, while to N95 is sent to port 55002, which is working.

    Kind regards,
    Edi.

  6. #6
    Registered User
    Join Date
    Feb 2010
    Posts
    5

    Re: Problems with incoming VoIP 3.x calls

    I think I found the problem!

    When VoIP3.x registers a user, it writes a hash in the contact URI, i.e. "aweofj293j2c0239jdwiofje0@mydomain.org"
    To invite a user, the server has to put this hash in the request-URI.

    Asterisk seems to do so, iptel.org doesn't, neither does miniSipServer. I've put a proxy between the server and a client that remembers this hash for every user and copies this hash into the request-uri at every outgoing INVITE from the server, and now it works.

    I don't know who is breaking the standard, but at the moment, there just seem to be servers that don't like Nokia Feature pack 2.

    Greets
    Simon

  7. #7
    Registered User
    Join Date
    Mar 2010
    Posts
    12

    Question Re: Problems with incoming VoIP 3.x calls

    Quote Originally Posted by Huwylersimon View Post
    I think I found the problem!

    When VoIP3.x registers a user, it writes a hash in the contact URI, i.e. "aweofj293j2c0239jdwiofje0@mydomain.org"
    To invite a user, the server has to put this hash in the request-URI.

    Asterisk seems to do so, iptel.org doesn't, neither does miniSipServer. I've put a proxy between the server and a client that remembers this hash for every user and copies this hash into the request-uri at every outgoing INVITE from the server, and now it works.

    I don't know who is breaking the standard, but at the moment, there just seem to be servers that don't like Nokia Feature pack 2.

    Greets
    Simon
    Good find.

    Is there anywhere some official information by Nokia on this?

    I'd like to contact a SIP provider to ask if they could fix the problem from their side.

    Edit: Nokia VoIP Release 3.0 FAQ

    1.32 Why does the Nokia S60 VoIP Release 3.0 product fail registration after receiving a ‘200 OK’ response from the registrar?
    The Nokia S60 VoIP Release 3.0 product uses the pseudo-random username of the Contact URI for matching the sent and received contact(s). If the username part of the URI is changed or removed, the SIP registration of the Nokia S60 VoIP Release 3.0 product fails after the ‘200 OK’ response.
    According to Nokia’s interpretation of the SIP RFC 3261, the registrar shall not modify the Contact URI sent in the response to the register request. When forwarding a request, for example, INVITE, some SIP servers write their own address to the Contact URI, instead of correctly inserting a Record-Route header. This also works with the Nokia S60 VoIP Release 3.0 product, but as for the REGISTER request the Contact has a different meaning and should not be touched.
    Why do you like to break things for your customers, Nokia? :-(
    Last edited by rjschenk; 2010-05-05 at 23:47.

  8. #8
    Nokia Developer Champion
    Join Date
    Mar 2003
    Posts
    4,104
    rjschenk, does this help?

  9. #9
    Registered User
    Join Date
    Sep 2007
    Posts
    2

    Re: Problems with incoming VoIP 3.x calls

    Has anyone found a solution to this?
    It is obviously ridiculous to ask large providers such as BroadVoice to change their servers when thousands of customers already use them without problems. I have tried BroadVoice with a N95 8GB. It works. With my brand new N8, it doesn't work. What am I supposed to think? At least when you break compatibility like that, you are required to be polite and provide a configuration setting to turn on backward compatibility. At the very least...
    Now what am I supposed to do? I need it working. I don't care about a detail of an RFC. I want INTEROPERABILITY. Is that clear, Nokia?

    Sorry for the rant.
    Thanks,
    Douglas

  10. #10
    Registered User
    Join Date
    May 2011
    Posts
    1

    Re: Problems with incoming VoIP 3.x calls

    I have the same problem, and it's incredible that nokia doesn't fix the voip setting 3.x

Similar Threads

  1. Replies: 0
    Last Post: 2009-05-13, 08:45
  2. Replies: 0
    Last Post: 2008-04-08, 19:33
  3. SIP crashing in 2 VoIP Calls
    By raj_rr7 in forum Symbian Networking & Messaging (Closed)
    Replies: 10
    Last Post: 2008-01-10, 13:37
  4. Regarding Incoming Calls
    By tpsriram in forum Mobile Java General
    Replies: 1
    Last Post: 2004-07-28, 23:48

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •