Q.SIG is just a variant of Q.931 and thus might be covered in that
already.
The question is what does Q.SIG run on top of?
Usualy Q.SIG is on top of Q.921 on top of ISDN BRI or ISDN PRI
physical interfaces.
Q.SIG over some IP carrier might simply be some really "vendor
specific" way of doing it. Maybe this is more a problem to tell
ethereal that a specific TCP port or whatever is used is in fact
Q.SIG than the protocol dissector itself.
On 26.08.2006, at 10:33, Anders Broman wrote:
Hi,
I don't know of any one having any plans of implementing Q.SIG but as
Already noted an entry on http://wiki.wireshark.org/ProtocolReference
With a sample trace might catch some ones interest...
Best regards
Anders
This would be very useful to A LOT of folks around here as well.
Any plans
to support Q.SIG?
-Andrew
Ref:
John Neiberger wrote:
I would really love to see support for Q.SIG in Ethereal and I didn't
see it on the current wish list. The Wiki page said to check here
before adding anything to the wish list, so I'm checking.
Congratulation! You're the first one I know that actually follow the
"official" process :-)
This is just to prevent invalid and/or duplicate entries.
I don't know anything about Q.SIG, you may just add it to the
WishList.
As an FYI, my company is about to roll out a fairly large IP telephony
project that will involve a lot of Q.SIG interaction. It would be
extremely helpful to be able to span that traffic over to Ethereal for
analysis
You may start a new Wiki page about this protocol and include a
trace file
and the protocol specs, making it much more likely that it will be
implemented.
However, there are no guarantees that it actually will be
implemented at
all, until you do the job yourself or find someone to do it.
Regards, ULFL
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
