Discussion Board

Results 1 to 6 of 6
  1. #1
    Registered User jjschwarz's Avatar
    Join Date
    Jun 2007
    Location
    North Carolina, USA
    Posts
    5
    My Nokia N95 seems to register just fine with our Avaya SES server, and I can make outbound calls properly. The phone shows registered with the server on the server side as well. Unfortunately when I receive an incoming call the phone ends up replying with a "480 Temporarily Not Available".

    Has anybody seen this behavior before? I have setup the phone to register both by IP and by domain name, both with the same effect.

  2. #2
    Regular Contributor vvsnaresh's Avatar
    Join Date
    Aug 2004
    Location
    Hyderabad-India
    Posts
    159
    Hi,

    Did u update the firmware ?
    Because, I was able to make and receive calls properly on N95 with the
    new firmware.

    Is the "480 Temporarily Not Available" status after answering the incoming call
    or during the "call ringing" time ? But, if it is even before "call ringing status"
    there may be a problem with your server.
    regards,
    VVS.Naresh
    --

  3. #3
    Registered User jjschwarz's Avatar
    Join Date
    Jun 2007
    Location
    North Carolina, USA
    Posts
    5
    I have updated the phone to the latest firmware (v11 series) that the updater will allow.

    I get the INVITE then the phone reply "100 Trying" and
    then the phone replies "480 Temporarily Not Available",
    then the server replies "ACK".

    The phone itself never rings. I am actively using the server
    with several other SIP devices which are working fine.

    I have a tcpdump of the messages if that will help.

  4. #4
    Nokia Developer Expert nly's Avatar
    Join Date
    Dec 2006
    Location
    Mountain View, CA
    Posts
    197
    The 480 response is due to the
    Accept-Contact: *;+avaya-cm-line=1
    in the request.

    At the moment it's not known if this can be fixed in the VoIP application of the Nseries products, and if yes, when. If it could be possible to remove the header from the Avaya side, it would fix this problem.

    This issue had nothing to do with overwriting the contact.

  5. #5
    Registered User jjschwarz's Avatar
    Join Date
    Jun 2007
    Location
    North Carolina, USA
    Posts
    5
    Odd that is causing the problem, as it only seems to affect my Nokia devices, which are listed as being compatible with the Avaya SES per Avaya. Do I need to filter the entire Accept-Contact line, or just the avaya-cm portion of the line.

  6. #6
    Registered User jjschwarz's Avatar
    Join Date
    Jun 2007
    Location
    North Carolina, USA
    Posts
    5
    Just went over the ieft draft on the Accept-Contact rule,
    and it appears the structure of the line:
    Accept-Contact: *;+avaya-cm-line=1

    is valid. Is this just a bug in the N95, or something that would
    affect all Nokia products running the SIP software?

Similar Threads

  1. Nokia PC Connectivity能否链接到cdma手机上发送短信和其他操作?
    By bborn in forum Web Technologies and Multimedia Content- Web 技术和多媒体内容
    Replies: 2
    Last Post: 2004-05-04, 11:06

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Nokia Developer aims to help you create apps and publish them so you can connect with users around the world.

京ICP备05048969号  © Copyright Nokia 2013 All rights reserved