[Asterisk-Dev] IAX Spec online

[Tilghman Lesher]

On Wednesday 27 April 2005 09:59, Kenny Shumard wrote:
> > You may want to notate somewhere in this document that the protocol
> > that you have labelled IAX is actually commonly known as IAX2.
> > Otherwise, this is likely to be a source of confusion.
>
> I think the idea is to *not* label the protocol as IAX2 after this. I
> haven't heard a valid argument yet that it should still be called
> IAX2 when it is the only existing (?) IAX version.

Because it's confusing otherwise, when the common usage is to use
IAX2.  I note that the channel module is chan_iax2.so, the channel
technology is "IAX2", and the library implementation is libiax2, so if
you call the specification "IAX", that's going to be confusing.  If you
want to call it IAXtoo, for sake of not having the numbering, that might
be acceptable, but calling it IAX when everything out there has the
label IAX2 is going to guarantee the number one FAQ is going to be "I
can find the original IAX spec, but where is the IAX2 spec?"

<snip>

> > Also, I believe that CAUSECODE _should_ be sent with any frame
> > containing a CAUSE IE.  The CAUSE IE is good for spitting out error
> > messages on the console and into logs, but CAUSECODE is far more
> > useful programatically, considering it has a limited number of
> > values, each of which are well-defined (and can be subsequently
> > passed to other types of channels without translation).
>
> Mark's general philosophy is not to require anything unless the
> absence of it will break something else. Because these IEs are
> strictly informational, they're completely optional. We could require
> CAUSECODE to be sent with CAUSE, but it doesn't break anything not to
> so I didn't write it like that.
You're welcome to go out and try to eliminate all occurrences of the
original libiax on the Internet, but I don't think you'll succeed.


That's why I used the word _should_, not _must_.  In other words, it is
a recommended, but not required action.  Given that we pass that
causecode everywhere, without translation, and it's Asterisk's internal
method of storing causes, we might go so far as to _deprecate_ the usage
of IE CAUSE in favor of IE CAUSECODE.

-- 
Tilghman