Hi,
I've no idea about the leagal issues but I'd be careful if you where
able to create that dictionary by
Using Ericsson internal dockumentation or dockuments that may have been
given to you under nondisclosure terms.
Regards
Anders
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Abhik Sarkar
Sent: den 14 november 2008 11:18
To: Developer support list for Wireshark
Subject: [Wireshark-dev] Ericsson SCAP Diameter
Hello All,
I am currently deploying/integrating a system which interfaces with
Ericsson charging systems using Diameter SCAP. During the integration, I
found that Wireshark is not able to decode some SCAP AVPs and was able
to modify the Wireshark Diameter Ericsson dictionary to decode all the
SCAP AVPs.
I would like to find out if there are any reasons (technical or legal)
which would prevent us from including this updated dictionary into the
standard distribution. I noticed that some of the command codes overlap
with other dictionaries, but I think the application_id's are different.
I also noticed a comment somewhere that the dissector currently
doesn't/can't distinguish between command codes based on application id.
I don't know if this is still the case.
If there are no issues, then I'll submit a patch for the updated
dictionary.
Thanks,
Abhik.
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev
