Re: [Sigtran] Sigtran interworking issue between multivendor node
David Laight <David.Laight@ACULAB.COM> Tue, 26 July 2016 10:41 UTC
Return-Path: <David.Laight@ACULAB.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 5DFFB12D1C0 for <sigtran@ietfa.amsl.com>; Tue, 26 Jul 2016 03:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.955
X-Spam-Level:
X-Spam-Status: No, score=-1.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 9GJ7S98UbkpA for <sigtran@ietfa.amsl.com>; Tue, 26 Jul 2016 03:41:34 -0700 (PDT)
Received: from smtp-out6.electric.net (smtp-out6.electric.net [192.162.217.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69D9512D1B9 for <sigtran@ietf.org>; Tue, 26 Jul 2016 03:41:34 -0700 (PDT)
Received: from 1bRzno-0007fQ-Tq by out6d.electric.net with emc1-ok (Exim 4.87) (envelope-from <David.Laight@ACULAB.COM>) id 1bRzno-0007lZ-VT; Tue, 26 Jul 2016 03:41:32 -0700
Received: by emcmailer; Tue, 26 Jul 2016 03:41:32 -0700
Received: from [213.249.233.130] (helo=AcuExch.aculab.com) by out6d.electric.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.87) (envelope-from <David.Laight@ACULAB.COM>) id 1bRzno-0007fQ-Tq; Tue, 26 Jul 2016 03:41:32 -0700
Received: from ACUEXCH.Aculab.com ([::1]) by AcuExch.aculab.com ([::1]) with mapi id 14.03.0123.003; Tue, 26 Jul 2016 11:39:29 +0100
From: David Laight <David.Laight@ACULAB.COM>
To: 'Pradeep4 Kumar' <pradeep4.kumar@aricent.com>, gitam changkakoti <gitam.changkakoti@live.in>, "sigtran@ietf.org" <sigtran@ietf.org>
Thread-Topic: [Sigtran] Sigtran interworking issue between multivendor node
Thread-Index: AQHR5qbIs3mnXGaKp02GmI580oNzsqAqIrdQgABNPzCAABN6AIAAAwng
Date: Tue, 26 Jul 2016 10:39:27 +0000
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D5F50306D@AcuExch.aculab.com>
References: <PS1PR0301MB212239D13AA549F53900907BED0D0@PS1PR0301MB2122.apcprd03.prod.outlook.com> <SG2PR0301MB2127866D25F2B3D92AA1CF35ED0D0@SG2PR0301MB2127.apcprd03.prod.outlook.com> <PS1PR04MB172222E2068B38CFD9626102DE0E0@PS1PR04MB1722.apcprd04.prod.outlook.com> <063D6719AE5E284EB5DD2968C1650D6D5F502FB4@AcuExch.aculab.com> <PS1PR04MB17227EFD5CA10CBCB5B0D58ADE0E0@PS1PR04MB1722.apcprd04.prod.outlook.com>
In-Reply-To: <PS1PR04MB17227EFD5CA10CBCB5B0D58ADE0E0@PS1PR04MB1722.apcprd04.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.202.99.200]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-IP: 213.249.233.130
X-Env-From: David.Laight@ACULAB.COM
X-PolicySMART: 3396946, 3397078
X-Virus-Status: Scanned by VirusSMART (c)
X-Virus-Status: Scanned by VirusSMART (s)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/Dtq-irKIXxwcAfOpPcVYozK6D2A>
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 10:41:35 -0000
You need to correctly quote the text - I can't see what you written. > -----Original Message----- > From: Pradeep4 Kumar [mailto:pradeep4.kumar@aricent.com] > Sent: 26 July 2016 11:37 > To: David Laight; gitam changkakoti; sigtran@ietf.org > Subject: RE: [Sigtran] Sigtran interworking issue between multivendor node > > Hi David, > > Thanks for additional info. I had also some more observations as: > > Point 1. > ">>> Although M3UA almost always carries the MTP3 service interface over SCTP at least one major > manufacturer has a configuration option where M3UA IPSP links seems to be used to pass messages > between MTP3 systems. > Configured that way it requires the IPSP system to answer DAUD (for its own pointcode) and to not > error DAVA and DUNA. > " > In standard systems as per RFC4666, ASP end or IPSP end does not expect to receive DUAD messages see > section from RFC as : > > "3.4.3. Destination State Audit (DAUD) > > The DAUD message MAY be sent from the ASP to the SGP to audit the > availability/congestion state of SS7 routes from the SG to one or > more affected destinations > " > > However it is always possible to customize the implementation to provide support of SSNM messages over > IPSP interface. > > 2. > "If you look at section 1.5.3 the M3UA connection appears to be an IPSP one between the ASP on the > right and SCCP in the middle. > However there is also a direct link shown between the MTP3 and M3UA." > > Please let us know which RFC version you are referring in above statement for section 1.5.3. As I > check the RFC4666 section 1.5.3, there is no mention of IPSP there in that model. > > > Best Regards, > Pradeep Kumar > "The world needs HQ (Humanity quotient) more than IQ." > > > -----Original Message----- > From: David Laight [mailto:David.Laight@ACULAB.COM] > Sent: Tuesday, July 26, 2016 3:06 PM > To: Pradeep4 Kumar <pradeep4.kumar@aricent.com>; gitam changkakoti <gitam.changkakoti@live.in>; > sigtran@ietf.org > Subject: RE: [Sigtran] Sigtran interworking issue between multivendor node > > From: Pradeep4 Kumar > > 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". > ... > > Although M3UA almost always carries the MTP3 service interface over SCTP at least one major > manufacturer has a configuration option where M3UA IPSP links seems to be used to pass messages > between MTP3 systems. > > Configured that way it requires the IPSP system to answer DAUD (for its own pointcode) and to not > error DAVA and DUNA. > > If you look at section 1.5.3 the M3UA connection appears to be an IPSP one between the ASP on the > right and SCCP in the middle. > However there is also a direct link shown between the MTP3 and M3UA. > It isn't clear to me which messages would use that link, but it might be the justification (or > documentation!) of this unusual mode. > > David > > > "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."
- [Sigtran] Sigtran interworking issue between mult… gitam changkakoti
- [Sigtran] Sigtran interworking issue between mult… gitam changkakoti
- Re: [Sigtran] Sigtran interworking issue between … David Laight
- Re: [Sigtran] Sigtran interworking issue between … Pradeep4 Kumar
- Re: [Sigtran] Sigtran interworking issue between … David Laight
- Re: [Sigtran] Sigtran interworking issue between … gitam changkakoti
- Re: [Sigtran] Sigtran interworking issue between … Pradeep4 Kumar