Re: Help decoding parameter Diagnostic Information

Michael Tuexen <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <[email protected]>
On Jan 18, 2007, at 6:35 PM, Fernandes, António Carlos, VF-PT wrote:

> Hello Michael,
> Thx for the tip!
> I manage to dissect part of the message.
> The SG basically sends in the diagnostic information filed some  
> sort of header followed by the exact message that cause the ERR (a  
> copy of the DAUD message received by the SG in my case).
> The only thing I could not decode was the header:
>
> 00001F3500000000
That is implementation dependent. You have to ask your vendor...
If he provides that information, I might be able to integrate that
into Wireshark...
>
> Best regards,
> António
>
> -----Original Message-----
> From: Michael Tuexen [mailto:[email protected]]
> Sent: quinta-feira, 18 de Janeiro de 2007 16:45
> To: Fernandes, António Carlos, VF-PT
> Cc: [email protected]
> Subject: Re: [Sigtran] Help decoding parameter Diagnostic Information
>
> Hi,
>
> the M3UA RFC says:
>
>     Diagnostic Information: variable length
>
>        When included, the optional Diagnostic information can be any
>        information germane to the error condition, to assist in
>        identification of the error condition. The Diagnostic  
> information
>        SHOULD contain the offending message.
>
> This means that the format is not specified in a way that you can
> dissect
> it. Wireshark, for example, shows this field simply a byte vector.
>
> What you can do is to try to guess what is in there. I would expect
> something at the beginning followed by a M3UA message. You should
> try to figure out where this message begins and dissect it by hand.
>
> Best regards
> Michael
>
> On Jan 18, 2007, at 4:52 PM, Fernandes, António Carlos, VF-PT wrote:
>
>> Hello everyone,
>> i'm trying to interconnect two different vendors over M3UA and
>> during the process of ASP activation my SG is responding to some
>> incoming messages (DAUD) with "Unexpected Message" which I think is
>> due to the fact that the ASP is still marked as inactive from the
>> SG side and no ASPActivate message has been received yet.
>> In the error message sent by the SG there is an optional parameter
>> "Diagnostic Information" which is not decoded by my protocol  
>> analyzer.
>> I have searched the RFCs for the format of this message but could
>> not find any relevant information.
>> Can someone help me on how to decode this information?
>>
>> Best Regards
>> António Fernandes
>>
>> --------------------------------------------------------------------- 
>> -
>> ----------------------
>>
>> This message may contain confidential information or privileged
>> material, and is intended only for the individual(s) named. If you
>> are not in the named addressee you should not disseminate,
>> distribute or copy this e-mail.
>>
>> Please notify the sender immediately by e-mail if you have received
>> this e-mail by mistake and delete this e-mail from your system.
>>
>>
>> E-mail transmission cannot be guaranteed to be secure or error-free
>> as information could be intercepted, corrupted, lost, destroyed,
>> arrive late or incomplete, or contain viruses. The sender therefore
>> does not accept liability for any errors or omissions in the
>> contents of this message which arise as a result of e-mail
>> transmission. If verification is required please request a hard-
>> copy version.
>>
>>
>> Vodafone (Portugal)
>>
>> _______________________________________________
>> Sigtran mailing list
>> [email protected]
>> https://www1.ietf.org/mailman/listinfo/sigtran
>
>
>
> ---------------------------------------------------------------------- 
> -----
> This message may contain confidential information or privileged  
> material, and is intended only for the individual(s) named. If you  
> are not in the named addressee you should not disseminate,  
> distribute or copy this e-mail.
> Please notify the sender immediately by e-mail if you have received  
> this e-mail by mistake and delete this e-mail from your system.
> E-mail transmission cannot be guaranteed to be secure or error-free  
> as information could be intercepted, corrupted, lost, destroyed,  
> arrive late or incomplete, or contain viruses. The sender therefore  
> does not accept liability for any errors or omissions in the  
> contents of this message which arise as a result of e-mail  
> transmission. If verification is required please request a hard- 
> copy version.
>
> Vodafone (Portugal)
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.