IETF Logo Mail Archive

Re: [Sigtran] How to identify which TCAP user a PDU belongs to

Deepak Gunjal <deepak.gunjal@aricent.com> Wed, 17 May 2017 10:08 UTC

Return-Path: <deepak.gunjal@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 7742B129BF7 for <sigtran@ietfa.amsl.com>; Wed, 17 May 2017 03:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 2dZDrLUqOKEW for <sigtran@ietfa.amsl.com>; Wed, 17 May 2017 03:08:34 -0700 (PDT)
Received: from IND01-MA1-obe.outbound.protection.outlook.com (mail-ma1ind01on0063.outbound.protection.outlook.com [104.47.100.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 741CC128D3E for <sigtran@ietf.org>; Wed, 17 May 2017 03:02:38 -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=tuelwEKjHRJty8jbow5CM75k6z0EcuuK9f0hiuRHIu8=; b=qutK+Rk9AYD+k1SHsluH5b1iHg9ElR3qv8L8zb3kftxbziwchlppFrivcQ75mh9ySUmwMNPHhdjjxiYj/e3F1XcjGcbrbP9bBkYGZlbXLPEAiiCIENqUTIU5GnhiiSQM46h2XriFHnovA/+IovxQN2gb2JHmHBs1MyeRu6jQALs=
Received: from PN1PR01MB0829.INDPRD01.PROD.OUTLOOK.COM (10.174.146.139) by PN1PR01MB0830.INDPRD01.PROD.OUTLOOK.COM (10.174.146.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16; Wed, 17 May 2017 10:02:34 +0000
Received: from PN1PR01MB0829.INDPRD01.PROD.OUTLOOK.COM ([10.174.146.139]) by PN1PR01MB0829.INDPRD01.PROD.OUTLOOK.COM ([10.174.146.139]) with mapi id 15.01.1084.030; Wed, 17 May 2017 10:02:34 +0000
From: Deepak Gunjal <deepak.gunjal@aricent.com>
To: prabath weerasinghe <psaw.mora@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
Thread-Topic: [Sigtran] How to identify which TCAP user a PDU belongs to
Thread-Index: AQHSzu7vnqhGZdeyrUq7miofwO0HV6H4Sdyg
Date: Wed, 17 May 2017 10:02:34 +0000
Message-ID: <PN1PR01MB08294AADD032F0AC678A4D5EF8E70@PN1PR01MB0829.INDPRD01.PROD.OUTLOOK.COM>
References: <CADgPoooBXSmA8H7m2kdsfTYtBssFEgnYumf_aC=gbrJg4q5qgw@mail.gmail.com>
In-Reply-To: <CADgPoooBXSmA8H7m2kdsfTYtBssFEgnYumf_aC=gbrJg4q5qgw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=aricent.com;
x-originating-ip: [121.241.96.35]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; PN1PR01MB0830; 7:Gi8axOB5x5QoBF5ieSuqR66ebR0i70AQoHV5vc34QpWfAH3JkRpn+zsFJka00s3x9mdg7vvNIwXrfsYzAq4EZQWvudMoPk6mXQSRa4JR22OXBw0moCcn5p91Wvy0zcoLyxs5sN9KT0Xak+Dnm9FMTg20frCUWEQ5LvLK6gVBue4KKVDKk6w8hWbLTNny8HsiWzWp5OysNNa8J+ide5iADPdFXOi95UsCI8PA9O3FXO/bejj8o8BZxBIzXmePyhl0LC+DFbPkjGP1Sy+4hE/CxxfWaTEfcGNP+Gl1s7kg0FUHoHyQEVQy4NLIOSI2gX6NumU8VrSe68V2TlgAVRgWxA==
x-ms-office365-filtering-correlation-id: 9ac07e27-988e-4483-6765-08d49d0bd71b
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:PN1PR01MB0830;
x-microsoft-antispam-prvs: <PN1PR01MB0830A5C5285CD329EF2BFB5AF8E70@PN1PR01MB0830.INDPRD01.PROD.OUTLOOK.COM>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(6055026)(6041248)(20161123564025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(20161123555025)(6072148); SRVR:PN1PR01MB0830; BCL:0; PCL:0; RULEID:; SRVR:PN1PR01MB0830;
x-forefront-prvs: 0310C78181
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39410400002)(39850400002)(39840400002)(39450400003)(39400400002)(39860400002)(377454003)(38564003)(53754006)(2950100002)(81166006)(8676002)(2501003)(5890100001)(54896002)(7696004)(2900100001)(66066001)(25786009)(6306002)(6436002)(53546009)(55016002)(9686003)(6506006)(8936002)(77096006)(50986999)(229853002)(189998001)(76176999)(5660300001)(54356999)(3660700001)(7736002)(53936002)(3280700002)(33656002)(6246003)(74316002)(478600001)(790700001)(122556002)(2906002)(39060400002)(6116002)(3846002)(38730400002)(86362001)(102836003); DIR:OUT; SFP:1101; SCL:1; SRVR:PN1PR01MB0830; H:PN1PR01MB0829.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_PN1PR01MB08294AADD032F0AC678A4D5EF8E70PN1PR01MB0829INDP_"
MIME-Version: 1.0
X-OriginatorOrg: Aricent.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 May 2017 10:02:34.2068 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: dbb4cbbe-57c5-469d-b342-a9814e1d2382
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PN1PR01MB0830
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/ijRaY8o7mueoH3J70ZXEMtWyeR4>
Subject: Re: [Sigtran] How to identify which TCAP user a PDU belongs to
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 17 May 2017 10:08:37 -0000

The SSN does indicate which functionality to be invoked at receiver but it should not be the only source to decide this. TCAP in my opinion should not have notion of INAP or CAMEL call but based on the SSN received in Called Party Address, it will forward the message to right stack layer which has registered with TCAP for desired SSN handling it can process. The message decoding can fail if the message is sent at wrong layer.

Regards
Deepak
From: Sigtran [mailto:sigtran-bounces@ietf.org] On Behalf Of prabath weerasinghe
Sent: Wednesday, May 17, 2017 2:47 PM
To: sigtran@ietf.org
Subject: [Sigtran] How to identify which TCAP user a PDU belongs to

Hi All,

This is regarding SCCP subsystem number and TCAP users.

If we have a SCP which supports both INAP and CAMEL, is SSN the only way to distinguish INAP and CAMEL calls in the TCAP layer ?



Thanks and Regards,

--
Prabath Weerasinghe
_________________________________________________________________________________
Confidentiality and Disclaimer

This email and any attachments are intended only for the person or entity to whom it is addressed. Its contents may be privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, please do not read, disclose, distribute or copy this email or use the information therein or act or omit to act in reliance thereof. Please also inform the sender of erroneous receipt and delete the material from your system.
"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."

v2.23.0 | Report a Bug | By Email