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

prabath weerasinghe <psaw.mora@gmail.com> Wed, 17 May 2017 10:40 UTC

Return-Path: <psaw.mora@gmail.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 B87A6129B41 for <sigtran@ietfa.amsl.com>; Wed, 17 May 2017 03:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fYRl914yEwoJ for <sigtran@ietfa.amsl.com>; Wed, 17 May 2017 03:40:28 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32ED5129477 for <sigtran@ietf.org>; Wed, 17 May 2017 03:35:51 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id b204so9631999oii.1 for <sigtran@ietf.org>; Wed, 17 May 2017 03:35:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0FrPTw3T4+qatAiw7T1GrzenhwvIYNmLurI/F+49+2Y=; b=F+TNYfNz8MFfAaLjU7QMGbJFKIH4hiksW3vy28TwLUvm9KT5UnC9pKp4yApJUDp/YG q0uEDSteU4DrPojKvjPJDK2dta56sFo20exUw3p/YqxlkJQW/DTztFDTTaoTX2d+Gn7h N+SFNRjWFuEIbR99cM+mpu47Lu7rFF0buQKG24FdVYdMCyn5DirO5ElNV+HwJdKcFfrK ZrL94mVOdjpeVkVUy3cQoKfUnx1DRx5Acu+Ga8sp3b2fEcKXIw1iDunkMuaCZXkcr4jk tciPlf7ihEC4ve9yu9894pUfN3WwAIsFgC+UcIRlHB9jKmh+gQx45K1iRwViOujqUDhS jS/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0FrPTw3T4+qatAiw7T1GrzenhwvIYNmLurI/F+49+2Y=; b=fL4J2uwg1pxK4p2We4GsdAjElq/TlNoTKQPdZHLNIWu4eleN7lLtsL0atUm1ac1qkB oQ0tfjzLjJ38IWpom43FsbU0JH9LhO2ZFMP4jgWs+JO8N4YH9D/CizwXDLDo0dP5yyzq N+MqgjzmRo1BUl9dtu/GKq+YEjzIH1x6Y+kugYMP6vGjbyi215NYG1ss+Zv7x3YeZRM6 kKfbU8a3E2g3BaEzB6jK1oR39YyqxAmghzKntL20uE70p5qT70E4nzQvZ85BKMdoNCzu cu2080Fjq6bMd94HkH0aCrkBn4PCr+e0akdlhVmwLLEw3uT9YsdgDZMtCgpL3lcRCI0I YUiA==
X-Gm-Message-State: AODbwcB4S28d7rWFt3fPaI0JiCF1XrbCO2LSgwkspuYz9QpKg05GYGLb GmvyS3Q7zhXOJEm6u8IKgmjfPVSGeQ==
X-Received: by 10.157.25.170 with SMTP id k39mr1574598otk.96.1495017350544; Wed, 17 May 2017 03:35:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.32.51 with HTTP; Wed, 17 May 2017 03:35:50 -0700 (PDT)
In-Reply-To: <PN1PR01MB08295B2A19A39A4AA7E8196BF8E70@PN1PR01MB0829.INDPRD01.PROD.OUTLOOK.COM>
References: <CADgPoooBXSmA8H7m2kdsfTYtBssFEgnYumf_aC=gbrJg4q5qgw@mail.gmail.com> <CAMoa0NLh-6z6OSaDNQR6iuPBa9F4pHPEi4DASdYH_z-dzeF3Mg@mail.gmail.com> <PN1PR01MB08295B2A19A39A4AA7E8196BF8E70@PN1PR01MB0829.INDPRD01.PROD.OUTLOOK.COM>
From: prabath weerasinghe <psaw.mora@gmail.com>
Date: Wed, 17 May 2017 16:05:50 +0530
Message-ID: <CADgPoor+F5pmMv==wmF130K6Syrtb+jXoqwhprQxW0GMJh2L9Q@mail.gmail.com>
To: Deepak Gunjal <deepak.gunjal@aricent.com>
Cc: Vance Shipley <vances@motivity.ca>, "sigtran@ietf.org" <sigtran@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c09b3b61cc4d2054fb5daec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/VKFs9Uh4y2SwiUJNXL_lMh6i-uQ>
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:40:31 -0000

Hi Deepak and Vance,

What if the SSN doesn't indicate CAMEL or INAP like with the pcap found
here ?
INAP-pcap <https://www.cloudshark.org/captures/028324459536?filter=inap>

As Vance mentioned, the application context implies of a INAP PDU though.

Is there a proper procedure to follow when identifying the correct TCAP
user ?
I mean like first checking the SSN, then checking the application context.

Thanks and Regards,


On Wed, May 17, 2017 at 3:47 PM, Deepak Gunjal <deepak.gunjal@aricent.com>
wrote:

> But I think the dialog portion is not mandatory in different protocols but
> yes if present in can be more contextual.
>
> -Deepak
> -----Original Message-----
> From: Sigtran [mailto:sigtran-bounces@ietf.org] On Behalf Of Vance Shipley
> Sent: Wednesday, May 17, 2017 3:40 PM
> To: prabath weerasinghe <psaw.mora@gmail.com>
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] How to identify which TCAP user a PDU belongs to
>
> On Wed, May 17, 2017 at 11:17 AM, prabath weerasinghe <psaw.mora@gmail.com>
> wrote:
> > 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 ?
>
> The application context in the dialogue portion provides more "context". :)
>
>
>
> --
>      -Vance
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www.ietf.org/mailman/listinfo/sigtran
> "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."
>



-- 
Prabath Weerasinghe
Department of Electrical Engineering
University of Moratuwa
Blog-*psawtech*talks.blogspot.com <http://psawtechtalks.blogspot.com/>

_________________________________________________________________________________
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.