For Class 2 we actually need to use the SLR/DLRs.
For example:
PC = Point Code
SLR = Source Local Reference
DLR = Destination Local Reference
SSN = Subsystem Number
CREQ = Connection Request
CREF = Connection Refused
CC = Connection Confirmed
DT1 = Dataform 1
Note some of the PC/SSN values are taken from the MTP3 protocol.
--> SCCP CREQ [Calling PC=X, Calling SSN=254, SLR=1, Called PC=Y, Called
SSN=254]
<-- SCCP CC [Called PC=X, Called SSN=254, DLR=1, Calling PC=Y, Calling
SSN=254, SLR=5]
--> SCCP DT1 [Calling PC=X, Calling SSN=254, Called PC=Y, Called SSN=254,
DLR=5]
<-- SCCP RLSD [Called PC=X, Called SSN=254, DLR=1, Calling PC=Y, Calling
SSN=254, SLR=5]
--> SCCP RLC [Calling PC=X, Calling SSN=254, SLR=1, Called PC=Y, Called
SSN=254, DLR=5]
Now the above is a very simple "conversation" I would like to be linked
together.
I have code that is using PC as 'address' and SLR/DLR' as 'port'.
Some problems I can think of are:
1. After the connection is released the local references become 'frozen'
for a short
period. So it is possible shortly after to see the "same" SCCP
CREQ. How
would one keep these as separate conversations? Combine packet
number?
> -----Original Message-----
> From: ethereal-dev-bounces@xxxxxxxxxxxx
> [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Morriss
> Sent: Monday, April 05, 2004 12:14 PM
> To: Ethereal development
> Subject: Re: [Ethereal-dev] Purpose of conversations ?
>
>
>
> Michael Lum wrote:
> > OK maybe I have misunderstood the purpose of conversations.
> >
> > I would like to string together packets containing SCCP Class 2
> > (connection
> > oriented)
> > messages.
> >
> >>From the display I would like to highlight a packet and then find
> > all of the associated packets automatically.
> >
> > Is this what conversations are for?
>
> My understanding is that conversations are used to store some data
> associated with a "conversation" so that subsequent messages in that
> conversation have that data associated with them.
>
> For example, in SCCP Class 2 only the first couple of messages have
> Called and Calling party addresses. Subsequent DATA messages
> only have
> SLR/DLR so using a display filter of "sccp.called.ssn == N"
> won't match
> them (the DATA messages). If, however, those DATA mesages
> were part of
> a conversation _and_ the data stored for that conversation
> contained the
> Called party SSN then the above filter would work.
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ether> eal-dev
>
