Comment # 2
on bug 9569
from Alex Rodikov
(In reply to comment #1)
Hi Evan, I would agree with you but Audiocodes wants to use "TPNCP" and "tpncp"
names for a off-stream plugin protocol. You know, it's impossible to have two
dissectors with identical protocol name. I agree that non-backward compatible
changes are highly undesirable but take in consideration that is proprietary,
non-standardized protocol used in Audiocodes products only.
To minimize a damage we can add an explanation in some README.txt file (in
TPNCP folder) and direct a user to Audiocodes for details. Something like:
"
TPNCP (stands for TrunkPack Network Control Protocol) is proprietary protocol
of Audiocodes Ltd (www.audiocodes.com).
The TPNCP is not supported by Audiocodes anymore.
If you need TPNCP protocol dissector contact '[email protected]'.
"
AlexR
You are receiving this mail because:
- You are watching all bug changes.
