×

Discussion Board

Results 1 to 7 of 7
  1. #1
    Registered User
    Join Date
    Jun 2004
    Posts
    8

    SIP/2.0 488 Not Acceptable Here

    Hi All,

    I'm trying to receive an INVITE sip message with my example application. So, my application registers on NOKIA SIP Server emulator and then waits for a request.
    An UA sip client sends an INVITE message to my application, the INVITE message is the following:

    ---
    INVITE sip:player1@192.168.177.64;comp=sigcomp SIP/2.0
    Via: SIP/2.0/UDP 192.168.177.67;branch=z9hG4bK3102e5e904c3310f1036aae8409ab01d
    Call-ID: -755507071-547161049@192.168.177.117
    Content-Length: 127
    Content-Type: application/sdp
    To: <sip:player1@domain2.com>
    From: <sip:useragent3@domain2.com>;tag=-102512309
    Contact: <sip:useragent3@192.168.177.117:5060>
    CSeq: 1 INVITE
    Via: SIP/2.0/UDP 192.168.177.117:5060;branch=C0A8B17513C4000000FDC7FAED92-11*0
    v=0
    o=- 1089985722678 1089985722678 IN IP4 192.168.177.117
    s=-
    c=IN IP4 192.168.177.117
    t=0 0
    m=audio 5006 RTP/AVP 3 0 8
    ---

    the invitation is delivered (by the proxy server) to my application but my application reject the invite with the message:

    ---
    SIP/2.0 488 Not Acceptable Here
    Via: SIP/2.0/UDP 192.168.177.67;branch=z9hG4bK3102e5e904c3310f1036aae8409ab01d,SIP/2.0/UDP 192.168.177.117:5060;branch=C0A8B17513C4000000FDC7FAED92-11*0
    To: sip:player1@domain2.com;tag=RCG5du8LO1
    From: sip:useragent3@domain2.com;tag=-102512309
    Call-ID: -755507071-547161049@192.168.177.117
    CSeq: 1 INVITE
    Content-Length: 0
    ---

    I've tryed to edit the file SipApplicationCapabilities.xml and then install it (running the command the epoc32\release\wins\udeb\SIPCLIENTINSTALLER.EXE), but it doesn't work.
    My SipApplicationCapabilities.xml was:

    ---
    <SIP_APPLICATION UID="10005B91" ALLOW_STARTING="YES">
    <SIP_HEADERS>
    <ACCEPT value="application/sdp"/>
    <ACCEPT value="text/plain"/>
    </SIP_HEADERS>
    <SDP_LINES>
    <LINE name="m" value="application 49154 udp SIPTest"/>
    <LINE name="m" value="audio 5006 RTP/AVP 3 0 8"/>
    </SDP_LINES>
    </SIP_APPLICATION>
    ---

    I think the problem was in the SipApplicationCapabilities.xml file, please, can anyone give me a suggestion?

    Thanks in advance

    Mario.

  2. #2
    Registered User
    Join Date
    Jun 2004
    Posts
    8
    Hi,

    Did anyone have a similar experience?

    thank you.

    Mario

  3. #3
    Regular Contributor
    Join Date
    Nov 2004
    Location
    Mumbai - India
    Posts
    155
    mario

    I'm facing same problem. Did u got solution ?



    Suraab

  4. #4
    Registered User
    Join Date
    Mar 2003
    Location
    Leh, Ladhak.
    Posts
    41

    NOT ACCEPTED HERE

    you are doing the right thing, I got it running exactly the same way.

  5. #5
    Regular Contributor
    Join Date
    Oct 2004
    Location
    India
    Posts
    138
    Hey one small doubt, think it may throw some light on your problem,

    ->can we have 2 entries for the "m" field, in the SDP lines category.

    regards
    chaitu

  6. #6
    Registered User
    Join Date
    Jan 2005
    Posts
    15

    SIP/2.0 488 Not Acceptable Here

    Yes, you can have 2 'm' fields. audio and video would be an example of why you would need 2.

    The .xml file announces your capabilities to the world. You're announcing that you support 3 audio codecs (3, 0, and 8). I think you have to have an 'a' line for each number in the 'm' line.

    Read the SDP Codec spec for more information.

    I think you need to add are some attribute fields such as: <LINE name="a" value="rtpmap:3 GSM/8000"/>
    The '3' corresponds to the '3' in the media field. You need one for the 0, and 8 also(but I don't know what codecs correspond to those).



    Are you actually supporting 3 different codecs? If so, I may have a few questions for you...

    -Ron

  7. #7
    Registered User
    Join Date
    Nov 2004
    Posts
    26

    Re: SIP/2.0 488 Not Acceptable Here

    Originally posted by ronflor
    The .xml file announces your capabilities to the world. You're announcing that you support 3 audio codecs (3, 0, and 8). I think you have to have an 'a' line for each number in the 'm' line.

    Read the SDP Codec spec for more information.
    That's required only if in the media field "m" formats with a dynamic payload type (referenced with a number above 95) are used

    For example, if we use:
    m=audio 49230 RTP/AVP 96 0

    we should define the attributes for a 96 format with
    a=rtpmap:96 L8/8000 (it just an example)
    but the attributes for 0 format are already defined (it is a static payload type), so an "a" field shouldn't be required....

    And I say SHOULDN'T.
    Last edited by cryptor; 2005-04-28 at 17:20.

Posting Permissions

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