Re: [Sip] Sent 18x with 'require:100rel' but no PRACK recieved

<honsha.narayan@wipro.com> Fri, 19 August 2011 10:16 UTC

Return-Path: <honsha.narayan@wipro.com>
X-Original-To: sip@ietfa.amsl.com
Delivered-To: sip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1171421F8A91 for <sip@ietfa.amsl.com>; Fri, 19 Aug 2011 03:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.19
X-Spam-Level:
X-Spam-Status: No, score=-0.19 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPz7YpQpdpw3 for <sip@ietfa.amsl.com>; Fri, 19 Aug 2011 03:16:19 -0700 (PDT)
Received: from wipro-blr-out01.wipro.com (wipro-blr-out01.wipro.com [203.91.198.74]) by ietfa.amsl.com (Postfix) with ESMTP id 93A6821F8A95 for <sip@ietf.org>; Fri, 19 Aug 2011 03:16:18 -0700 (PDT)
X-AuditID: cb5bdd57-b7b4dae000000e4d-2e-4e4e3826bd50
Received: from blr-ec-aa03.wipro.com ( [10.201.18.42]) by wipro-blr-out01.wipro.com (Symantec Mail Security) with SMTP id E9.34.03661.6283E4E4; Fri, 19 Aug 2011 15:47:10 +0530 (IST)
Received: from blr-ec-bh01.wipro.com ([10.201.50.91]) by blr-ec-aa03.wipro.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 19 Aug 2011 15:47:10 +0530
Received: from BLR-EC-MBX02.wipro.com ([10.201.50.163]) by blr-ec-bh01.wipro.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 19 Aug 2011 15:47:10 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC5E59.27DCEDFF"
Date: Fri, 19 Aug 2011 15:42:42 +0530
Message-ID: <AC327FB104AFED419B885A1B28B448FE04071710@BLR-EC-MBX02.wipro.com>
In-Reply-To: <tencent_1E4799066035BA457D8DBD17@qq.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Sent 18x with 'require:100rel' but no PRACK recieved
Thread-Index: AcxeHsnA8a7ljbYnQB6hJDl2ZlgQmwAOY/8Q
References: <tencent_1E4799066035BA457D8DBD17@qq.com>
From: <honsha.narayan@wipro.com>
To: <etherchen@foxmail.com>, <sip@ietf.org>
X-OriginalArrivalTime: 19 Aug 2011 10:17:10.0216 (UTC) FILETIME=[27F1CC80:01CC5E59]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Sent 18x with 'require:100rel' but no PRACK recieved
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 10:16:20 -0000

Hi ,

 

First of all , please use "sip-implementers
(sip-implementors@cs.columbia.edu)" forum for the answer of this query. 

 

As per SIP RFC3262, you must reject the call in SIP side with 5xx (
provided you had SDP in reliable 18x ). You can reject ISUP side with a
RELEASE message.

 

But if you want to relax your software compliance a bit here , you can
do that,  but remember your early media negotiation may be in trouble.
If you are sure that on ISUP side the call is answered ( ANM is received
) you can proceed for sending 200 to SIP side.

 

Regards

Honsha 

 

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
etherchen
Sent: Friday, August 19, 2011 8:48 AM
To: sip
Subject: [Sip] Sent 18x with 'require:100rel' but no PRACK recieved

 

Hi:

 

  I'm facing a ISUP - SIP interworking issue recently.  

 

 I receive INVITE from remote SIP server and send IAM to ISUP side, ISUP
reply ACM/CPG and then I send 18x with 100rel out, but I did not receive
any PRACK from remote SIP server, and I re-send 18x to them. During this
period, ISUP side send ANM to me. 

 

 If connect the call, but my end haven't receive PRACK yet, it become a
unreliable call.

 If disconnect the call, I should not base on ANM to release a call.

 If continue 18x re-transmission untill time-out, it will have charging
issue. Because ISUP side start billing base on ANM already, but my SIP
side haven't start charging because not answer.

 

 Thanks.