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

Vance Shipley <vances@motivity.ca> Wed, 17 May 2017 10:15 UTC

Return-Path: <vances@motivity.ca>
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 1712E12940E for <sigtran@ietfa.amsl.com>; Wed, 17 May 2017 03:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=motivity-ca.20150623.gappssmtp.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 yR_43-sV27WE for <sigtran@ietfa.amsl.com>; Wed, 17 May 2017 03:15:21 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 05DA0126C0F for <sigtran@ietf.org>; Wed, 17 May 2017 03:09:54 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id f102so6107110ioi.2 for <sigtran@ietf.org>; Wed, 17 May 2017 03:09:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=motivity-ca.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CB9bIuJVvnjfxYHO439o/fPYuWHZrWT3KxklQ7akhqI=; b=sGlQXoJ4UATunzst78XjrJCEXy4cMtZAWK11JVSb14vRYXPHEF+0vSzOp7Fc4xj+lt 3p0mQwovnmWvKEJBmM8yh+lG8+gcXcAM8uP6iXTHKMd9GpZi0y2MMgq8PuClyUQ3FyM8 LSAwoI83Ek2v+o/XbDTCq9zXz5LBeYe/IsoV3fFJqYitrfl3VPVgdhe4wHHsClK0Lupj 74eJ9G+xVomV+FUkIiMsJEGGTjJ86eD0SteftpD2RX0MP1PvWrtYqZxoOqcEi4VO2rez W4AghAY7UXa8hs8syFi1/T7tQ419+qXGo4HP8Gye+6Rv9dvE9Jp+Un0hQEFQCXxWp6Q/ 6ZKg==
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=CB9bIuJVvnjfxYHO439o/fPYuWHZrWT3KxklQ7akhqI=; b=uLbUAO5/7tzKZ7MtAL0UG4KbdP9bzrqEazBSagpJrhJFztfp7i2UnIOaY5zKUWnnNH oMJFbdeim0s7SKP3ZhOvPPNJsE14G8oUdzXiZ10dE5fP6P3/pNY+dWn/hBB56huAOBIc kYbtCAyicWfgB06uHBbbhDAtiLtvTNmbI2t8H+FXxGRzyX63ABFZMCDYGoEXuRrMbIQA 8RUQsQpq1FZTCbh5yzfMaDiGyoFf1VXMxR3NDND6va+m05nh3D6eCW5Nr+7q3uU6EBcG OmIUsdqSqSgBCovxJnyXwKullPG8PUVPVmSnOKpBCoPhBi+ucBI+AcotATDYuPD0p2FQ qL3w==
X-Gm-Message-State: AODbwcBMVnm4oV4cgN8SmRPA3hVfKXH0mo8AHm+hwUCBNAWaG0Pao/Jx B9UqrfXr0SL3mPBJW167eH/B5JIZctViFbg4WA==
X-Received: by 10.107.36.9 with SMTP id k9mr2535576iok.130.1495015794341; Wed, 17 May 2017 03:09:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.16.74 with HTTP; Wed, 17 May 2017 03:09:53 -0700 (PDT)
In-Reply-To: <CADgPoooBXSmA8H7m2kdsfTYtBssFEgnYumf_aC=gbrJg4q5qgw@mail.gmail.com>
References: <CADgPoooBXSmA8H7m2kdsfTYtBssFEgnYumf_aC=gbrJg4q5qgw@mail.gmail.com>
From: Vance Shipley <vances@motivity.ca>
Date: Wed, 17 May 2017 12:09:53 +0200
Message-ID: <CAMoa0NLh-6z6OSaDNQR6iuPBa9F4pHPEi4DASdYH_z-dzeF3Mg@mail.gmail.com>
To: prabath weerasinghe <psaw.mora@gmail.com>
Cc: sigtran@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/8UBD9YcUU22nXoCjasDirpNvpOQ>
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:15:23 -0000

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