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

prabath weerasinghe <psaw.mora@gmail.com> Wed, 17 May 2017 09:21 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 944D512946E for <sigtran@ietfa.amsl.com>; Wed, 17 May 2017 02:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level:
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 3I9H62Ht7BGA for <sigtran@ietfa.amsl.com>; Wed, 17 May 2017 02:21:03 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 E9B5412E036 for <sigtran@ietf.org>; Wed, 17 May 2017 02:17:03 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id w10so7693933oif.0 for <sigtran@ietf.org>; Wed, 17 May 2017 02:17:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=8xKyPuJIBKLVHt7vQIvqo4ODNtwkE4PSQF9oFpTUysU=; b=nAKEVkewm/Wa1/+beJlpukgQw7bLoTFAogJLcvJ6621iGNCLX35k70UI/27yeYVajG ZMZyqLbu5uxme62wGK3U4ws9VsBFtUvErsdt3GIdv33Bj+vezK2pmmtj05dVYuJiFB8B 76it0d/IZbHtSIjlclOroYsE3L6USEcrofW45tDirRZeQAQT60jCeYaOnB4zWGeMBQYA 9GBhPew45BMRiMKDnwjArbXVFsUIk8GlA2qhNZyTWW23LaTPi6M4BXylZyCknKdBoAqe AiUq+bPc8ZaqKmIqxL5dTa3f074YGKCEx6inO3YByz1zsG0p/mu7uQ3z8gKI0zLGveFS 5euA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=8xKyPuJIBKLVHt7vQIvqo4ODNtwkE4PSQF9oFpTUysU=; b=B9cxDGQ1tKFuR7kEAzi+iGx1+LUyC0tHNGEooF+1UGPqOkY42tKyXarzlNbx2KlLQb UBDtCwXMyrYZ/bYr4do66Go/f2/PTJKS4D8nqwVwO5g4WZ5sfyLaQraeR/i1sAUXY7NT inH24PHK+Ru7YpWVtOg+zPaW4UnXsDcCepRmJN1FO71xqD1JnMO1UXBaiTmoCvwB1oPP WOcU7lgzA8OLEp4y39Wr1sEUWt5sn/+WmXc0uQIyDCkNy8YCPT9hEBWVxQ82NwFWO+/K Poyz0noSiLQ3CRKbN/YcFuGottC/asvYg+L15SG8gS/uLcwnYeyftjyeGe2vQ/9svgYv Eu3A==
X-Gm-Message-State: AODbwcCFSwbHwWNJEm8AwxWnQrAQQUcL3UHnQmxKzJUdJ5NNoXp694/a j6SVWnJyaP5IA7jcSmi+KuS+lV+bqg==
X-Received: by 10.157.1.166 with SMTP id e35mr1154872ote.58.1495012623183; Wed, 17 May 2017 02:17:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.32.51 with HTTP; Wed, 17 May 2017 02:17:02 -0700 (PDT)
From: prabath weerasinghe <psaw.mora@gmail.com>
Date: Wed, 17 May 2017 14:47:02 +0530
Message-ID: <CADgPoooBXSmA8H7m2kdsfTYtBssFEgnYumf_aC=gbrJg4q5qgw@mail.gmail.com>
To: sigtran@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c09d71256f4f9054fb4c0bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/ONpJLfAon2OiG57-mD62HVb6JZY>
Subject: [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 09:21:05 -0000

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.