Re: QSIG Support
"Andrew Halperin (ahalper)" <[email protected]> Fri, 25 Aug 2006 15:22:37 -0700
| Newsgroups | gmane.network.ethereal.devel |
|---|---|
| Message-ID | <1201449A090B0843854022982BB025F9D086C5@xmb-sjc-219.amer.cisco.com> |
This is a multi-part message in MIME format. --===============2018948949== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------- The Ethereal project is being continued at a new site. Please go to http://www.wireshark.org and subscribe to [email protected]. Don't forget to unsubscribe from this list at http://www.ethereal.com/mailman/listinfo/ethereal-dev ------------------- --===============2018948949== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6C894.F8CFEDC6" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6C894.F8CFEDC6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable This would be very useful to A LOT of folks around here as well. Any plans to support Q.SIG? =20 -Andrew =20 Ref: John Neiberger wrote:=20 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. =09 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.=20 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 =09 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=20 =20 ------_=_NextPart_001_01C6C894.F8CFEDC6 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2900.2964" name=3DGENERATOR></HEAD> <BODY> <DIV><FONT face=3D"Courier New" size=3D2><SPAN = class=3D754312122-25082006>This would=20 be very useful to A LOT of folks around here as well. Any plans to = support=20 Q.SIG?</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN=20 class=3D754312122-25082006></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN=20 class=3D754312122-25082006>-Andrew</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN=20 class=3D754312122-25082006></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN=20 class=3D754312122-25082006>Ref:</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN = class=3D754312122-25082006><!--StartFragment --><FONT size=3D3><FONT=20 face=3D"Times New Roman"> </FONT><TT>John Neiberger wrote: = </TT></FONT> <BLOCKQUOTE=20 style=3D"PADDING-LEFT: 0.85em; MARGIN: 0em; BORDER-LEFT: rgb(85,85,238) = 0.2em solid"><PRE style=3D"MARGIN: 0em">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.</PRE><BR><TT></TT></BLOCKQUOTE><TT>Congratulation!=20 You're the first one I know that actually follow the "official" process=20 :-)</TT><BR><BR><PRE style=3D"MARGIN: 0em">This is just to prevent = invalid and/or duplicate entries.</PRE><BR><TT>I=20 don't know anything about Q.SIG, you may just add it to the WishList. = </TT> <BLOCKQUOTE=20 style=3D"PADDING-LEFT: 0.85em; MARGIN: 0em; BORDER-LEFT: rgb(85,85,238) = 0.2em solid"><PRE style=3D"MARGIN: 0em">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 </PRE></BLOCKQUOTE><TT>You may start a new Wiki page about this protocol = and=20 include a trace file and the protocol specs, making it much more likely = that it=20 will be implemented.</TT><BR><BR><TT>However, there are no guarantees = that it=20 actually will be implemented at all, until you do the job yourself or = find=20 someone to do it.</TT><BR><BR><TT>Regards, ULFL</TT> = </SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" = size=3D2></FONT> </DIV></BODY></HTML> ------_=_NextPart_001_01C6C894.F8CFEDC6-- --===============2018948949== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ethereal-dev mailing list [email protected] http://www.ethereal.com/mailman/listinfo/ethereal-dev --===============2018948949==--