[LEGO <luis.ontanon@xxxxxxxxx>]

the only dtap-only traces I've found so far are text dumps generated
by a program attached to a mobile with a "debug" firmware. I haven't
yet seen any other types of dtap-only traces (I'll have a chat with a
friend of mine that actually tests the mobile phones, he'll ceratinly
know better than me)

dtap is used to have the mobile to "talk" to the MSC (to the SGSN
too?) and is normally encapsulated inside NBAP, RANAP, BSSAP in its
way to the Mobile or MSC.
  
On 8/3/05, Guy Harris <gharris@xxxxxxxxx> wrote:
> LEGO wrote:
> 
> > If the case is the second you should:
> > +  generate a pcap file containing the payload and use one of the user
> > DLTs (147->162).
> >        text2pcap -l 147 input.txt output.pcap
> >
> > + configure ethereal to decode as TCAP that DLT.
> >     preferences->protocols->DLT User [ABCD]
> >     DLT: the one choosen
> >     payload: gsm_dtap
> 
> Are DTAP traces sufficiently common that it'd be useful to add a
> WTAP_ENCAP_GSM_DTAP - and possibly reserve a DLT_ value for it?  (I
> don't know what binary trace formats from various GSM-tracing equipment
> exist, or whether they're either documented or reverse-engineerable; if
> any are, the ability to read them might be useful.)
> 


-- 
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan