Re: [Sigtran] Sigtran interworking issue between multivendor node

Pradeep4 Kumar <pradeep4.kumar@aricent.com> Tue, 26 July 2016 04:50 UTC

Return-Path: <pradeep4.kumar@aricent.com>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2266612D0DA for <sigtran@ietfa.amsl.com>; Mon, 25 Jul 2016 21:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.152
X-Spam-Level:
X-Spam-Status: No, score=-1.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_WEB=0.77, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aricent.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uomv9SzKYoBz for <sigtran@ietfa.amsl.com>; Mon, 25 Jul 2016 21:50:56 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-pu1apc01on0061.outbound.protection.outlook.com [104.47.126.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF57C12B010 for <sigtran@ietf.org>; Mon, 25 Jul 2016 21:50:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aricent.onmicrosoft.com; s=selector1-Aricent-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=w71UcDSizzoAfteNuAJEG/kjjDT/YMJb0BGlnNqEayA=; b=IZKJ6I32FvyoD9eY9skDvQxYzF4aGsj4bKXJWRns4zcJEQ+PkR9LyLIOkVZC0zivUcv8+/zlzj5YyBtfZVSk1qLgmr+ervPtYFMd6YJcwcjyd/fe/F7yqX+xxPB8bbD+m/J8tv4+IooUAEgXKKwEqtN4h7thC1mi15AhwfUcNcM=
Received: from PS1PR04MB1722.apcprd04.prod.outlook.com (10.167.52.16) by PS1PR04MB1721.apcprd04.prod.outlook.com (10.167.52.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.544.10; Tue, 26 Jul 2016 04:50:51 +0000
Received: from PS1PR04MB1722.apcprd04.prod.outlook.com ([10.167.52.16]) by PS1PR04MB1722.apcprd04.prod.outlook.com ([10.167.52.16]) with mapi id 15.01.0544.019; Tue, 26 Jul 2016 04:50:50 +0000
From: Pradeep4 Kumar <pradeep4.kumar@aricent.com>
To: gitam changkakoti <gitam.changkakoti@live.in>, "sigtran@ietf.org" <sigtran@ietf.org>
Thread-Topic: [Sigtran] Sigtran interworking issue between multivendor node
Thread-Index: AQHR5qbIs3mnXGaKp02GmI580oNzsqAqIrdQ
Date: Tue, 26 Jul 2016 04:50:50 +0000
Message-ID: <PS1PR04MB172222E2068B38CFD9626102DE0E0@PS1PR04MB1722.apcprd04.prod.outlook.com>
References: <PS1PR0301MB212239D13AA549F53900907BED0D0@PS1PR0301MB2122.apcprd03.prod.outlook.com> <SG2PR0301MB2127866D25F2B3D92AA1CF35ED0D0@SG2PR0301MB2127.apcprd03.prod.outlook.com>
In-Reply-To: <SG2PR0301MB2127866D25F2B3D92AA1CF35ED0D0@SG2PR0301MB2127.apcprd03.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pradeep4.kumar@aricent.com;
x-originating-ip: [165.225.104.84]
x-ms-office365-filtering-correlation-id: 7d7ff247-7624-4565-7836-08d3b5106ae6
x-microsoft-exchange-diagnostics: 1; PS1PR04MB1721; 6:eLTc4uO5LsM/3zssm3ubXo8waKzWg8sXTp9REy1Xw28S0HHeXhSyz9iwH/Ujismga0da/pfdGn3cw6hBSradXH9N2Y0geLB5gsohTGOs3JdoKc5UaUdhaysyHuuKUYLsq01dgzwtHT75v4QcHTbFaCDHCPe83/6GmPwN/iaIVhHi+gDvaGhQGF5S/EOzgUdohV4MYH+a1R7Cj5lAtNBHrI2ldNB/thydvkgRqNJrORmMVTOWbBRm0miYx2IG6UkpGAusW1ZRUCLMMNd/SVthQVLlkK0AJBTgyTuVx07xFUwGqQPh0v27Wq6jO739Pw7BbycyfjyypUF0uH27OOILzQ==; 5:Ws33o72aCCmZhzZ1pAkAntdJFIf1w4xMkikDfbzyDzET3sbFleccelRptwEaLLrYIJAVQwlhUjdjM4qf5xsOQ84goyGvbp5LmnL2QGaujCmOHtb6y7scd+d9SbONrvW17+JDMeYTMGCaYDJr/R0EQQ==; 24:YXq5idFWENhvp4piKCKAHjwzRQC+HAwH4I4a/MMoUIblvnHZkRIjnQMp+jLh+qIW3MRsbB4QKunnF1Ko1M1gML3r8K46O1d3btpvhWs/zTo=; 7:Sfjxv4fyhjWT+r+dsflK1QuTGBLp6jB1SZdKniTCoHUlxtrSp/lYKImTeIym0xZUtESe4wqleK8fA0ca3pkT9/3iWyTV+rFvmIEum+zuZuWvbhGrcLPA/SgXw2f81jSlz87zzQezDFO8ltqWq4SnSr2pr3d8xR+q6tx0HMz7R6E0lx1NtVwXryOZmZvEiaamKsrk4j8v4v+4QGSeef4FnbuKt5EiIKTn8D2xh3r7XXpxnCGMQ5uMtCj30ak+QUoT
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:PS1PR04MB1721;
x-microsoft-antispam-prvs: <PS1PR04MB1721E7E8FBC01E1CEAE98633DE0E0@PS1PR04MB1721.apcprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21532816269658);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026); SRVR:PS1PR04MB1721; BCL:0; PCL:0; RULEID:; SRVR:PS1PR04MB1721;
x-forefront-prvs: 00159D1518
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(377454003)(189002)(13464003)(38564003)(199003)(54356999)(7846002)(76176999)(8936002)(81166006)(81156014)(2501003)(97736004)(50986999)(66066001)(101416001)(3660700001)(5001770100001)(8676002)(76576001)(5003630100001)(6116002)(102836003)(189998001)(3280700002)(107886002)(3846002)(586003)(106356001)(106116001)(2900100001)(305945005)(2950100001)(86362001)(122556002)(87936001)(105586002)(10400500002)(19580405001)(19580395003)(68736007)(7696003)(5003600100003)(9686002)(92566002)(5002640100001)(7736002)(77096005)(74316002)(2906002)(33656002)(552674004); DIR:OUT; SFP:1101; SCL:1; SRVR:PS1PR04MB1721; H:PS1PR04MB1722.apcprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: aricent.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Aricent.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2016 04:50:50.5263 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: dbb4cbbe-57c5-469d-b342-a9814e1d2382
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PS1PR04MB1721
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/cHAJrXsVG-5TFoSmRy3Q8nrLMAo>
Subject: Re: [Sigtran] Sigtran interworking issue between multivendor node
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sigtran/>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2016 04:50:58 -0000

Hi Gitam,

I am assuming that the open MGW and AOIP BSC are connection over the IPSP communication type. Correct if I am wrong?

IPSP is point to point communication so DAUD is not expected message on IPSP communication mode.

So the receiving end point must drop the DAUD message and also this end point can optionally send back Management Error  message with error as "Unexpected Message".

Same can be inferred from section "3.8.1" from rfc4666 as below:

Off course the more experienced experts can comment and put more light on this topic and correct me if needed.


+++++++++++++++++++++++++++++++++++
The "Unexpected Message" error MAY be sent if a defined and
   recognized message is received that is not expected in the current
   state (in some cases, the ASP may optionally silently discard the
   message and not send an Error message).
+++++++++++++++++++++++++++++++++++++++++++

Best Regards,
Pradeep Kumar
 "The world needs HQ (Humanity quotient) more than IQ."


-----Original Message-----
From: gitam changkakoti [mailto:gitam.changkakoti@live.in]
Sent: Monday, July 25, 2016 10:28 PM
To: sigtran@ietf.org
Subject: [Sigtran] Sigtran interworking issue between multivendor node


>
> Dear All,
>
> Greetings .... This mail is intended to seek suggestion on Sigtran connectivity between multivendor node.
>
> We are trying to connect open MGW to an AOIP BSC. Both belongs to different vendors. Fluctuation of M3Ua SUA observed at BSC end post   Connectivity.
>
> As per MGW vendor BSC is not supposed to send SUA management messages to MGW( DAUD) which is causing MGW to send DUNA to BSC inturn causing fluctuations @ BSc end for mgw cluster SPC.
>
> Please be informed, there is no fluctuation @ association level. Kindly suggest and share the actual guidelines . What should happen as per Rfc.
>
> Regards
> Gitam
> +919706818836
>
>
>
> Sent from my iPhone


"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."