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

[Deepak Gunjal <[e-mail]>]

That seems to be custom solution if something of this sort happens. The standards provide these mechanisms to enable interoperability between different implementation but if that is not followed then it falls to private agreement between different partners on how these kind of scenarios shall be handled.

From: prabath weerasinghe [mailto:[e-mail]]
Sent: Wednesday, May 17, 2017 4:06 PM
To: Deepak Gunjal <[e-mail]>
Cc: Vance Shipley <[e-mail]>; [e-mail]
Subject: Re: [Sigtran] How to identify which TCAP user a PDU belongs to

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

On Wed, May 17, 2017 at 11:17 AM, prabath weerasinghe <[e-mail]<mailto:[e-mail]>> 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
[e-mail]<mailto:[e-mail]>
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-psawtechtalks.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.
"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."