As far as I know IUA, as defined in RFC 3057 is transported over
SCTP only (at least this is recommended). Also IUA is not an
Ethereal name for Q921. From RFC 3057:
****** ISDN ****** IP *******
* EP *---------------* SG *--------------* MGC *
****** ****** *******
+-----+ +-----+
|Q.931| (NIF) |Q.931|
+-----+ +----------+ +-----+
| | | | IUA| | IUA |
| | | +----+ +-----+
|Q.921| |Q.921|SCTP| |SCTP |
| | | +----+ +-----+
| | | | IP | | IP |
+-----+ +-----+----+ +-----+
Best regards
Michael
On Mar 21, 2005, at 20:55 Uhr, LEGO wrote:
UIA is not currently supported as an rtp payload type.
Anyway, adding support for iua over rtp should not be that much work.
If you can send in some of those packets we might be able to add uia
as an rtp payload type.
On Mon, 21 Mar 2005 10:27:47 -0500, Max Magliaro
<mmagliaro@xxxxxxxxxxxxxxxx> wrote:
I have captured some packets from an H.323 videoconference.
They are RTP (over UDP), carrying H.224 far end camera control
messages.
They are really encoded as Q.921 at the lowest level
I click on the packet, tell it to decode it as RTP, and it correctly
decodes
the RTP portion (the header, timestamp, etc).
But it doesn't know what to do with the actual buffer bytes.
If I right click on the buffer inside the packet and say "Decode As",
I cannot see Q.921, or IUA (which I think is Ethereal's name for this)
in the list.
How can I force it to decode the buffer as Q.921?
Thank you,
Max Magliaro
Broadband Networks, Inc
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
--
This information is top security. When you have read it, destroy
yourself.
-- Marshall McLuhan
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
