[SIPForum-discussion] 488 Not Acceptable Here

Mon Jun 8 09:11:45 UTC 2009

I'd check first if point A can support receipt of a multi-part MIME message body in the INVITE from point B.

Stew

-----Original Message-----
From: discussion-bounces at sipforum.org
[mailto:discussion-bounces at sipforum.org]On Behalf Of Rico S. Salgado
Sent: 05 June 2009 06:53
To: discussion at sipforum.org
Subject: Re: [SIPForum-discussion] 488 Not Acceptable Here

Hello Guys,

Just like to ask your assistance in analyzing an issue we're encountering.
We are receiving a 488 error when making a call from point B to point A.
However calls from point A to point B are working.  

I read it maybe about the supported codec but I'm not sure how to verify
this.  Below is a sample logs trace:

--------------------------------------------------------------------------

     INVITE sip:<USER1>@<POINT.A.IP>:5060 SIP/2.0 
     Via: SIP/2.0/UDP
<POINT.B.IP>:5060;rport;branch=z9hG4bK-10e8-1244098095-4944-202 
     Call-ID: 62f2-437-54200964815-aicent1-0-<POINT.B.IP>
     CSeq: 1 INVITE 
     Max-Forwards: 70 
     To: <sip:<USER1>@<POINT.A.IP>:5060> 
     From:
"emma"<sip:<USER2>@<POINT.B.IP>>;tag=95ffcd055e0f78f7d5d397020e89288d5d1a25a
8 
     User-Agent: Dialogic-SIP/X.X.X.X aicent1 0 
     Contact: <sip:<USER2>@<POINT.B.IP>:5060> 
     Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBS CRIBE, NOTIFY,
INFO, REFER, UPDATE 
     Supported: path, replaces, timer, tdialog 
     Session-Expires: 1800 
     Expires: 300 
     Organization: Dialogic 
     Content-Length: 467 
     Content-Type: multipart/mixed;boundary=ub-dialogic-sw-1
     MIME-Version: 1.0 

          --ub-dialogic-sw-1 
          Content-Type: application/sdp 

          v=0 
          o=Dialogic_SDP 0 0 IN IP4 <POINT.B.IP> 
          s=Dialogic-SIP 
          c=IN IP4 X.X.X.X 
          t=0 0 
          m=audio 8220 RTP/AVP 18 0 8 
          a=rtpmap:0 PCMU/8000 
          a=rtpmap:8 PCMA/8000 
          a=rtpmap:18 G729/8000 
          a=fmtp:18 annexb=no 
          a=silenceSupp:off - - - - 

          --ub-dialogic-sw-1 
          Content-Type: application/ISUP; version=ITU-93 
          Content-Disposition: signal;handling=optional 

          01 00 08 00 0a 02 02 09 07 03 10 19 99 01 10 43 0a 09 83
          10 68 31 19 32 54 76 08 00  

          --ub-dialogic-sw-1-- 

---> [<POINT.A.IP>, 5060 -> <POINT.B.IP>, 5060]
      SIP/2.0 100 Trying 
      From: "emma"<sip:<USER2>@<POINT.B.IP>>;tag=95f
      fcd055e0f78f7d5d397020e89288d5d1a25a8 
      To: <sip:<USER1>@<POINT.A.IP>:5060>;tag=f0442598156200964144815 
      Call-ID: 62f2-437-54200964815-aicent1-0-<POINT.B.IP>
      CSeq: 1 INVITE 
      Allow: ACK,BYE,CANCEL,INVITE,OPTIONS,INFO,SUBSCRIBE,REFER,NOTIFY,PRACK

      Via: SIP/2.0/UDP <POINT.B.IP>:5060;rport=5060;branch=
z9hG4bK-10e8-1244098095-4944-202 
      Contact: <sip:<POINT.A.IP>> 
      Content-Length: 0 

---> [<POINT.A.IP>, 5060 -> <POINT.B.IP>, 5060]
      SIP/2.0 488 Not Acceptable Here 
      From:
"emma"<sip:<USER2>@<POINT.B.IP>>;tag=95ffcd055e0f78f7d5d397020e89288d5d1a25a
8 
      To: <sip:<USER1>@<POINT.A.IP>:5060>;tag=f0442598156200964144815 
      Call-ID: 62f2-437-54200964815-aicent1-0-<POINT.B.IP>
      CSeq: 1 INVITE 
      Server: CS2000_NGSS/9.0 
      Supported: 100rel 
      Allow: ACK,BYE,CANCEL,INVITE,OPTIONS,INFO,SUBSCRIBE,REFER,NOTIFY,PRACK

      Via: SIP/2.0/UDP
<POINT.B.IP>:5060;rport=5060;branch=z9hG4bK-10e8-1244098095-4944-202 
      Content-Length: 0

---------------------------------------------------------------------------

Any idea you could share would be highly appreciated.  Thanks.

Regards,
Rico

_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org

NOTICE & DISCLAIMER 
This email including attachments (this "Document") is confidential and may contain legally privileged information.  If you have received this Document in error please notify the sender immediately and delete this Document from your system without using, copying, disclosing or disseminating it or placing any reliance upon its contents.  We cannot accept liability for any breaches of confidence arising through use of this Document.

The information contained in this Document is provided solely for information purposes on an "as is" basis without warranty of any kind, either express or implied, including without limitation any implied warranty of satisfactory or merchantable quality, fitness for a particular purpose or freedom from error or infringement.  The user relies on the information contained herein, and its accuracy or otherwise, entirely at their own risk.

Any opinions expressed in this Document are those of the author and do not necessarily reflect the opinions of Telsis.  We will not accept responsibility for any commitments made by our employees outside the scope of our business.