Re: How to identify which TCAP user a PDU belongs to

--===============0561275121961207455==
Content-Type: multipart/alternative; boundary="94eb2c09b3b61cc4d2054fb5daec"

--94eb2c09b3b61cc4d2054fb5daec
Content-Type: text/plain; charset="UTF-8"

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 <[email protected]>
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:[email protected]] On Behalf Of Vance Shipley
> Sent: Wednesday, May 17, 2017 3:40 PM
> To: prabath weerasinghe <[email protected]>
> Cc: [email protected]
> Subject: Re: [Sigtran] How to identify which TCAP user a PDU belongs to
>
> On Wed, May 17, 2017 at 11:17 AM, prabath weerasinghe <[email protected]>
> 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
> [email protected]
> 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.

--94eb2c09b3b61cc4d2054fb5daec
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Deepak and Vance,=C2=A0<div><br></div><div>What if the =
SSN doesn&#39;t indicate CAMEL or INAP like with the pcap found here ?</div=
><div><a href=3D"https://www.cloudshark.org/captures/028324459536?filter=3D=
inap">INAP-pcap</a><br></div><div><br></div><div>As Vance mentioned, the ap=
plication context implies of a INAP PDU though.=C2=A0</div><div><br></div><=
div>Is there a proper procedure to follow when identifying the correct TCAP=
 user ?=C2=A0</div><div>I mean like first checking the SSN, then checking t=
he application context.</div><div><br></div><div>Thanks and Regards,</div><=
div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Wed, May 17, 2017 at 3:47 PM, Deepak Gunjal <span dir=3D"ltr">&lt;<a =
href=3D"mailto:[email protected]" target=3D"_blank">deepak.gunjal@a=
ricent.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But I th=
ink the dialog portion is not mandatory in different protocols but yes if p=
resent in can be more contextual.<br>
<br>
-Deepak<br>
<div><div class=3D"h5">-----Original Message-----<br>
From: Sigtran [mailto:<a href=3D"mailto:[email protected]">sigtran-b=
ounces@ietf.<wbr>org</a>] On Behalf Of Vance Shipley<br>
Sent: Wednesday, May 17, 2017 3:40 PM<br>
To: prabath weerasinghe &lt;<a href=3D"mailto:[email protected]">psaw.mor=
[email protected]</a>&gt;<br>
Cc: <a href=3D"mailto:[email protected]">[email protected]</a><br>
Subject: Re: [Sigtran] How to identify which TCAP user a PDU belongs to<br>
<br>
On Wed, May 17, 2017 at 11:17 AM, prabath weerasinghe &lt;<a href=3D"mailto=
:[email protected]">[email protected]</a>&gt; wrote:<br>
&gt; If we have a SCP which supports both INAP and CAMEL, is SSN the only<b=
r>
&gt; way to distinguish INAP and CAMEL calls in the TCAP layer ?<br>
<br>
The application context in the dialogue portion provides more &quot;context=
&quot;. :)<br>
<br>
<br>
<br>
--<br>
=C2=A0 =C2=A0 =C2=A0-Vance<br>
<br>
</div></div>______________________________<wbr>_________________<br>
Sigtran mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sigtran" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/sigtran</a><=
br>
<div class=3D"HOEnZb"><div class=3D"h5">&quot;DISCLAIMER: This message is p=
roprietary to Aricent and is intended solely for the use of the individual =
to whom it is addressed. It may contain privileged or confidential informat=
ion and should not be circulated or used for any purpose other than for wha=
t 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, o=
r disclosing the contents of this message. Aricent accepts no responsibilit=
y for loss or damage arising from the use of the information transmitted by=
 this email including damage from virus.&quot;<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div><fon=
t color=3D"#666666">Prabath Weerasinghe</font></div><div><font color=3D"#66=
6666">Department of Electrical=C2=A0Engineering</font></div><div><font colo=
r=3D"#666666">University of Moratuwa</font></div><div><font color=3D"#66666=
6">Blog-<span style=3D"font-family:arial,sans-serif;line-height:15px"><a hr=
ef=3D"http://psawtechtalks.blogspot.com/" target=3D"_blank"><b>psawtech</b>=
talks.blogspot.com</a><br><br>_____________________________________________=
____________________________________<br></span></font><font color=3D"Gray" =
face=3D"Verdana">Confidentiality and Disclaimer<br>
<br>
This email and any attachments are intended only for the person or=20
entity to whom it is addressed. Its contents may be privileged,=20
confidential or otherwise protected from disclosure. If you are not the=20
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.</font><br></div></div>
</div>

--94eb2c09b3b61cc4d2054fb5daec--


--===============0561275121961207455==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sigtran mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sigtran

--===============0561275121961207455==--