[asterisk-dev] IAX hardphone

Kevin P. Fleming kpfleming at digium.com
Sat Feb 12 08:23:27 CST 2011

On 02/11/2011 03:47 PM, David Vossel wrote:
> ----- Original Message -----
>> From: "Bill Shaw"<b.shaw at comcast.net>
>> To: asterisk-dev at lists.digium.com
>> Sent: Friday, February 11, 2011 3:35:28 PM
>> Subject: Re: [asterisk-dev] IAX hardphone
>> I'm seeing some information elements in my data that are not defined
>> in
>> the RFC and Wireshark doesn't know - 0x37&  0x38. Is there an updated
>> list of ies available somewhere?
>> Also, I'm wondering if my 'accept' issue is because I'm not
>> authenticating first. I should be able to just 'accept' the 'new'
>> without authenticating, shouldn't I?
>> Thanks again,
>> Bill
> Look at channels/iax2.h.  Asterisk is the IAX2 specification at this point.  Those new information elements are the new 64bit format fields.

Actually, this is poor practice. Once the IAX2 specification was 
published as an RFC, the valid values for IAX2 commands, IEs, and 
various other components were placed into IANA registries. From this 
point forward, any future additions to these spaces *should* have been 
made by drafting an appropriate document describing them and requesting 
that IANA add them to the appropriate registry (which would result in 
numbers being assigned).

This situation is no different than if Asterisk wanted to start sending 
a new SIP request method without getting it registered (although SIP 
request methods have a much higher burden to meet before they are 
registered by IANA).

Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming at digium.com
Check us out at www.digium.com & www.asterisk.org

More information about the asterisk-dev mailing list