On 3/28/06, Anders Broman (AL/EAB) <anders.broman@xxxxxxxxxxxx> wrote:
> Hi,
> It looks to be:
> 1.2.826.0.1249.51
> {iso(1) member-body(2) uk(826) national(0) ericsson(1249) inDomain(51)}
> Intelligent Network (IN) Domain
>
> Or is thats just wrongly decoded?
I've seen this OID already... It was inside MAP messages. AFAIK It
makes little or no sense to have IN info in BSSAP. So I'll guess we
are dealing either with MAP or INAP instead of BSSAP.
Luis.
>
> Brg
> Anders
>
> -----Original Message-----
> From: ethereal-users-bounces@xxxxxxxxxxxx [mailto:ethereal-users-bounces@xxxxxxxxxxxx] On Behalf Of Roger Mahler
> Sent: den 27 mars 2006 17:49
> To: ethereal-users@xxxxxxxxxxxx
> Subject: [Ethereal-users] Forcing BSSAP over SCCP
>
> Hello
>
> in the attached capture I have 2 segmented XUDT frames that get nicely reassembled.
>
> The SSN are encoded as:
>
> - MSC (BSSAP-LE) (251)
> - IOS or SMLC (BSSAP-LE) (252)
>
> but I don't know if the layer above SCCP really is BSSAP.
>
> How can I force Ethereal to decode the Reassembled Message using BSSAP dissector in order to see if it really _is_ BSSAP?
> Or does anyone know what should be the right layer?
>
> /Roger
>
> --
> Echte DSL-Flatrate dauerhaft für 0,- Euro*!
> "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-users
>
--
oggi banane domani mortadella