<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1578" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi All,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>We want to write a proposal for extending IAX2
IE types to carry info undefined in the protocol. We have two
questions.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>1. What is the IE identification number we should
propose? </FONT><FONT face=Arial size=2>IAX2 has used 0x01 to 0x33.
Corydon76 had posted a patch on bugs.digium.com that used 0x32. We wonder if
there is any suggestion for how to use this identification number
resource.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>2. Our info data will be more than 256 bytes, but
less than normal MTU of UDP. As we know that one IE block can only carry 256 or
less bytes data. The "Date Length" is a byte. If we use multiple IE blocks,
there are two solutions, one is using multiple IE types. Another is using one IE
type, but adding a sequence number in DATA. The first one will consume more the
identification number resource. The second one will bring some other issues. We
want to know if this issue had been discussed.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Thanks,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Di-Shi Sun.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>