One document matched: draft-guy-iaxiana-00.xml
<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- ENTITY rfc1321 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1321.xml' -->
<!ENTITY rfc4566 PUBLIC '' '../rfcs/reference.RFC.4566.xml'>
<!ENTITY rfc1034 PUBLIC '' '../rfcs/reference.RFC.1034.xml'>
<!ENTITY rfc1321 PUBLIC '' '../rfcs/reference.RFC.1321.xml'>
<!ENTITY rfc1851 PUBLIC '' '../rfcs/reference.RFC.1851.xml'>
<!ENTITY rfc1890 PUBLIC '' '../rfcs/reference.RFC.1890.xml'>
<!ENTITY rfc2026 PUBLIC '' '../rfcs/reference.RFC.2026.xml'>
<!ENTITY rfc2119 PUBLIC '' '../rfcs/reference.RFC.2119.xml'>
<!ENTITY rfc4301 PUBLIC '' '../rfcs/reference.RFC.4301.xml'>
<!ENTITY rfc3447 PUBLIC '' '../rfcs/reference.RFC.3447.xml'>
<!ENTITY rfc2535 PUBLIC '' '../rfcs/reference.RFC.2535.xml'>
<!ENTITY rfc3435 PUBLIC '' '../rfcs/reference.RFC.3435.xml'>
<!ENTITY rfc4733 PUBLIC '' '../rfcs/reference.RFC.4733.xml'>
<!ENTITY rfc4734 PUBLIC '' '../rfcs/reference.RFC.4734.xml'>
<!ENTITY rfc4646 PUBLIC '' '../rfcs/reference.RFC.4646.xml'>
<!ENTITY rfc4647 PUBLIC '' '../rfcs/reference.RFC.4647.xml'>
<!ENTITY rfc3174 PUBLIC '' '../rfcs/reference.RFC.3174.xml'>
<!ENTITY rfc3525 PUBLIC '' '../rfcs/reference.RFC.3525.xml'>
<!ENTITY rfc3261 PUBLIC '' '../rfcs/reference.RFC.3261.xml'>
<!ENTITY rfc3454 PUBLIC '' '../rfcs/reference.RFC.3454.xml'>
<!ENTITY rfc3491 PUBLIC '' '../rfcs/reference.RFC.3491.xml'>
<!ENTITY rfc3550 PUBLIC '' '../rfcs/reference.RFC.3550.xml'>
<!ENTITY rfc3978 PUBLIC '' '../rfcs/reference.RFC.3978.xml'>
<!ENTITY rfc3979 PUBLIC '' '../rfcs/reference.RFC.3979.xml'>
<!ENTITY rfc3761 PUBLIC '' '../rfcs/reference.RFC.3761.xml'>
<!ENTITY rfc3401 PUBLIC '' '../rfcs/reference.RFC.3401.xml'>
<!ENTITY rfc3402 PUBLIC '' '../rfcs/reference.RFC.3402.xml'>
<!ENTITY rfc3403 PUBLIC '' '../rfcs/reference.RFC.3403.xml'>
<!ENTITY rfc3404 PUBLIC '' '../rfcs/reference.RFC.3404.xml'>
<!ENTITY rfc3629 PUBLIC '' '../rfcs/reference.RFC.3629.xml'>
<!ENTITY rfc3986 PUBLIC '' '../rfcs/reference.RFC.3986.xml'>
<!ENTITY rfc4395 PUBLIC '' '../rfcs/reference.RFC.4395.xml'>
<!ENTITY rfc4347 PUBLIC '' '../rfcs/reference.RFC.4347.xml'>
<!ENTITY rfc5226 PUBLIC '' '../rfcs/reference.RFC.5226.xml'>
<!ENTITY html401 PUBLIC '' '../w3c/reference.W3C.REC-html401-19991224.xml'>
]>
<rfc category="info" ipr="noDerivatives3978" docName='draft-guy-iaxiana-00'>
<?xml-stylesheet type='text/xsl' href='./rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc tocdepth="2" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<front>
<title abbrev="IANA IAX Considerations">IANA Considerations for IAX: Inter-Asterisk eXchange Version 2</title>
<author initials="E.T." surname="Guy" fullname="Ed Guy" role="editor"> <organization>TruPhone</organization>
<address>
<postal>
<street>235 Main Street, STE 253</street>
<city>Madison</city> <region>NJ</region> <code>07940</code>
<country>US</country>
</postal>
<phone>+1 973 437 4519</phone>
<email>edguy@emcsw.com</email>
<uri>http://www.TruPhone.com/</uri>
</address>
</author>
<date />
<!-- <area>Transport</area> <workgroup>IP Telephony</workgroup> -->
<area> </area> <workgroup> </workgroup>
<keyword>RFC</keyword>
<keyword>Request for Comments</keyword>
<keyword>VoIP</keyword>
<keyword>Voice over IP</keyword>
<keyword>IAX</keyword>
<keyword>Asterisk</keyword>
<abstract>
<t>This document establishes the IANA registries for IAX, the Inter-Asterisk eXchange protocol, an application-layer control and media protocol for creating, modifying, and terminating multimedia sessions over Internet Protocol (IP) networks. IAX was developed by the open source community for the Asterisk PBX and is targeted primarily at Voice over Internet Protocol (VoIP) call control, but it can be used with streaming video or any other type of multimedia.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t> IAX (Inter-Asterisk eXchange) is an "all in one" protocol for handling multimedia in IP networks. It combines both control and media services in the same protocol.
In addition, IAX uses a single UDP data stream on a static port greatly simplifying Network Address Translation (NAT) gateway traversal,
eliminating the need for other protocols to work around NAT, and simplifying network and firewall
management. IAX employs a compact encoding
which decreases bandwidth usage and is well suited for Internet telephony service. In addition, its open nature permits new payload
types additions needed to support additional services.
<vspace blankLines='1' />
This document specifies and provides the initial values for the creation of the IAX-related IANA registries as per <xref target="RFC5226" />.
</t> </section>
<section title="IANA Considerations">
<t>The IAX protocol, as defined in <xref target="IAX" />, defines 15 namespaces that require registration. These namespaces are
described below.</t>
<t>Each of these namespaces utilize an 'Expert Review' for extension. Documentation of new values is not mandated as RFCs. The expert review should be guided by a few common sense considerations. For example, new values should not be specific to a country, region, organization, or company; they should be well- defined and widely recognized.
</t>
<section title="Meta Command">
<t> Registry Name: IAX Meta Commands </t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.1.3.2 of <xref target="IAX" />. </t>
<t> Valid Range: 0x01-x7F. </t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the Initial Assignments of Meta Command values:</preamble>
<ttcol>TYPE</ttcol><ttcol>Name</ttcol><ttcol>Description</ttcol>
<c>0x01</c> <c>Trunk Meta Frame</c> <c>Indicates that frame is a trunk meta frame.</c>
</texttable>
</section>
<section title="Frame Types" anchor="iax.frametypes">
<t> Registry Name: IAX Frame Types </t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any. In
addition, the definition and description of subclasses.</t>
<t> Description: See Section 8.2 of <xref target="IAX" />. </t>
<t> Valid Range: 0x01-xFF. </t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the Initial Assignments of Frame Type Values:</preamble>
<ttcol>TYPE</ttcol><ttcol>Description</ttcol><ttcol>Subclass Description</ttcol><ttcol>Data Description</ttcol>
<c>0x01</c> <c>DTMF</c> <c>0-9, A-D, *, #</c> <c>Undefined</c>
<c>0x02</c> <c>Voice </c> <c>Audio Compression Format </c> <c>Data</c>
<c>0x03</c> <c>Video </c> <c>Video Compression Format </c> <c>Data</c>
<c>0x04</c> <c>Control </c> <c>See Control Frame Subclass </c> <c>Varies with subclass </c>
<c>0x05</c> <c>Null </c> <c>Undefined </c> <c>Undefined</c>
<c>0x06</c> <c>IAX Control </c><c>See IAX Protocol Messages</c> <c>Information Elements </c>
<c>0x07</c> <c>Text </c> <c>Always 0 </c> <c>Raw Text</c>
<c>0x08</c> <c>Image </c> <c>Image Compression Format</c> <c>Raw image</c>
<c>0x09</c> <c>HTML </c> <c>See HTML Frame Types</c> <c>Message Specific</c>
<c>0x0A</c> <c>Comfort Noise</c><c>Level in -dBov of comfort noise </c> <c>None </c>
</texttable>
</section>
<section title="Control Frame Subclass" anchor="iax.controlframes">
<t> Registry Name: IAX Control Frame Subclass </t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.3 of <xref target="IAX" />. </t>
<t> Valid Range: 0x00-x7F. </t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the Initial Assignments of Control Frame Subclasses:</preamble>
<ttcol width='18%'>VALUE</ttcol><ttcol>Name</ttcol><ttcol>Description</ttcol>
<c> 0x01 </c><c> Hangup </c><c> The call has been hungup at the remote end. </c>
<c> 0x02 </c><c> Reserved </c><c> Reserved for future use</c>
<c> 0x03 </c><c> Ringing </c><c> Remote end is ringing (ringback)</c>
<c> 0x04 </c><c> Answer </c><c> Remote end has answered</c>
<c> 0x05 </c><c> Busy </c><c> Remote end is busy</c>
<c> 0x06 </c><c> Reserved </c><c> Reserved for future use</c>
<c> 0x07 </c><c> Reserved </c><c> Reserved for future use</c>
<c> 0x08 </c><c> Congestion </c><c> The call is congested.</c>
<c> 0x09 </c><c> Flash Hook </c><c> Flash hook</c>
<c> 0x0a </c><c> Reserved </c><c> Reserved for future use</c>
<c> 0x0b </c><c> Option </c><c> Device-specific options are being transmitted </c>
<c> 0x0c </c><c> Key Radio </c><c> Key Radio</c>
<c> 0x0d </c><c> Unkey Radio </c><c> Unkey Radio</c>
<c> 0x0e </c><c> Call Progress </c><c> Call is in progress</c>
<c> 0x0f </c><c> Call Proceeding </c><c> Call is proceeding</c>
<c> 0x10 </c><c> Hold </c><c> Call is placed on hold</c>
<c> 0x11 </c><c> Unhold </c><c> Call is taken off hold</c>
</texttable>
</section>
<section title="IAX Control Frames" anchor="iax.iaxframes">
<t> Registry Name: IAX Control Frame Subclass </t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.4 of <xref target="IAX" />. </t>
<t> Valid Range: 0x01-x7F. </t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the Initial Assignments of IAX Control Frame values:</preamble>
<ttcol>Hex</ttcol ><ttcol > Name </ttcol><ttcol>Description</ttcol>
<c>0x01 </c><c>NEW </c><c> Initiate a new call </c>
<c>0x02 </c><c>PING </c><c> Ping request </c>
<c>0x03 </c><c>PONG </c><c> Ping or poke reply </c>
<c>0x04 </c><c>ACK </c><c> Explicit acknowledgment </c>
<c>0x05 </c><c>HANGUP </c><c> Initiate call tear-down </c>
<c>0x06 </c><c>REJECT </c><c> Reject a call </c>
<c>0x07 </c><c>ACCEPT </c><c> Accept a call </c>
<c>0x08 </c><c>AUTHREQ </c><c> Authentication request </c>
<c>0x09 </c><c>AUTHREP </c><c> Authentication reply </c>
<c>0x0a </c><c>INVAL </c><c> Invalid message </c>
<c>0x0b </c><c>LAGRQ </c><c> Lag request </c>
<c>0x0c </c><c>LAGRP </c><c> Lag reply </c>
<c>0x0d </c><c>REGREQ </c><c> Registration request </c>
<c>0x0e </c><c>REGAUTH </c><c> Registration authentication </c>
<c>0x0f </c><c>REGACK </c><c> Registration acknowledgement </c>
<c>0x10 </c><c>REGREJ </c><c> Registration reject </c>
<c>0x11 </c><c>REGREL </c><c> Registration release </c>
<c>0x12 </c><c>VNAK </c><c> Video/Voice retransmit request </c>
<c>0x13 </c><c>DPREQ </c><c> Dialplan request </c>
<c>0x14 </c><c>DPREP </c><c> Dialplan reply </c>
<c>0x15 </c><c>DIAL </c><c> Dial </c>
<c>0x16 </c><c>TXREQ </c><c> Transfer request </c>
<c>0x17 </c><c>TXCNT </c><c> Transfer connect </c>
<c>0x18 </c><c>TXACC </c><c> Transfer accept </c>
<c>0x19 </c><c>TXREADY </c><c> Transfer ready </c>
<c>0x1a </c><c>TXREL </c><c> Transfer release </c>
<c>0x1b </c><c>TXREJ </c><c> Transfer reject </c>
<c>0x1c </c><c>QUELCH </c><c>Halt audio/video [media] transmission </c>
<c>0x1d </c><c>UNQUELCH </c><c> Resume audio/video [media] transmission </c>
<c>0x1e </c><c>POKE </c><c> Poke request </c>
<c>0x1f </c><c>Reserved </c><c> Reserved for future use </c>
<c>0x20 </c><c>MWI </c><c> Message waiting indication </c>
<c>0x21 </c><c>UNSUPPORT </c><c> Unsupported message </c>
<c>0x22 </c><c>TRANSFER </c><c> Remote transfer request</c>
<c>0x23 </c><c>Reserved </c><c> Reserved for future use</c>
<c>0x24 </c><c>Reserved </c><c> Reserved for future use</c>
<c>0x25 </c><c>Reserved </c><c> Reserved for future use</c>
</texttable>
</section>
<section title="HTML Command Subclasses" anchor="iax.htmlsubclasses">
<!-- Taken from /usr/src/iaxclient/libiax2/src/frame.h -->
<t> Registry Name: IAX HTML Command Subclasses </t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.2 of <xref target="IAX" />. </t>
<t> Valid Range: 0x01-x7F. </t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the Initial Assignments of IAX HTML Command Subclasses:</preamble>
<ttcol> NUMBER </ttcol><ttcol> DESCRIPTION </ttcol>
<c> 0x01 </c><c> Sending a URL </c>
<c> 0x02 </c><c> Data frame </c>
<c> 0x04 </c><c> Beginning frame </c>
<c> 0x08 </c><c> End frame </c>
<c> 0x10 </c><c> Load is complete </c>
<c> 0x11 </c><c> Peer does not support HTML </c>
<c> 0x12 </c><c> Link URL </c>
<c> 0x13 </c><c> Unlink URL </c>
<c> 0x14 </c><c> Reject Link URL </c>
</texttable>
</section>
<section title="Information Elements" anchor="iax.ies">
<t> Registry Name: IAX Information Elements</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.6 of <xref target="IAX" />. </t>
<t> Valid Range: 0x01-xFF. </t>
<t> Display format: hex. </t>
<texttable anchor='tab.iedefs' title='Information Element Definitions'>
<preamble>The following table specifies the Initial Assignments of Information Element Definitions</preamble>
<ttcol>HEX</ttcol>
<ttcol>NAME</ttcol>
<ttcol>DESCRIPTION</ttcol>
<c> HEX </c><c> NAME </c><c> DESCRIPTION </c>
<c> 0x01 </c><c> CALLED NUMBER </c><c> Number/extension being called </c>
<c> 0x02 </c><c> CALLING NUMBER </c><c> Calling number </c>
<c> 0x03 </c><c> CALLING ANI </c><c> Calling number ANI for billing </c>
<c> 0x04 </c><c> CALLING NAME </c><c> Name of caller </c>
<c> 0x05 </c><c> CALLED CONTEXT </c><c> Context for number </c>
<c> 0x06 </c><c> USERNAME </c><c> Username (peer or user) for authentication </c>
<c> 0x07 </c><c> PASSWORD </c><c> Password for authentication </c>
<c> 0x08 </c><c> CAPABILITY </c><c> Actual CODEC capability </c>
<c> 0x09 </c><c> FORMAT </c><c> Desired CODEC format </c>
<c> 0x0a </c><c> LANGUAGE </c><c> Desired language </c>
<c> 0x0b </c><c> VERSION </c><c> Protocol version </c>
<c> 0x0c </c><c> ADSICPE </c><c> CPE ADSI capability </c>
<c> 0x0d </c><c> DNID </c><c> Originally dialed DNID </c>
<c> 0x0e </c><c> AUTHMETHODS </c><c> Authentication method(s) </c>
<c> 0x0f </c><c> CHALLENGE </c><c> Challenge data for MD5/RSA </c>
<c> 0x10 </c><c> MD5 RESULT </c><c> MD5 challenge result </c>
<c> 0x11 </c><c> RSA RESULT </c><c> RSA challenge result </c>
<c> 0x12 </c><c> APPARENT ADDR </c><c> Apparent address of peer </c>
<c> 0x13 </c><c> REFRESH </c><c> When to refresh registration </c>
<c> 0x14 </c><c> DPSTATUS </c><c> Dialplan status </c>
<c> 0x15 </c><c> CALLNO </c><c> Call number of peer </c>
<c> 0x16 </c><c> CAUSE </c><c> Cause </c>
<c> 0x17 </c><c> IAX UNKNOWN </c><c> Unknown IAX command </c>
<c> 0x18 </c><c> MSGCOUNT </c><c> How many messages waiting </c>
<c> 0x19 </c><c> AUTOANSWER </c><c> Request auto-answering </c>
<c> 0x1a </c><c> MUSICONHOLD </c><c> Request musiconhold with QUELCH </c>
<c> 0x1b </c><c> TRANSFERID </c><c> Transfer Request Identifier </c>
<c> 0x1c </c><c> RDNIS </c><c> Referring DNIS </c>
<c> 0x1d </c><c> Reserved </c><c> Reserved for future use</c>
<c> 0x1e </c><c> Reserved </c><c> Reserved for future use</c>
<c> 0x1f </c><c> DATETIME </c><c> Date/Time </c>
<c> 0x20 </c><c> Reserved </c><c> Reserved for future use </c>
<c> 0x21 </c><c> Reserved </c><c> Reserved for future use </c>
<c> 0x22 </c><c> Reserved </c><c> Reserved for future use </c>
<c> 0x23 </c><c> Reserved </c><c> Reserved for future use </c>
<c> 0x24 </c><c> Reserved </c><c> Reserved for future use </c>
<c> 0x25 </c><c> Reserved </c><c> Reserved for future use </c>
<c> 0x26 </c><c> CALLINGPRES </c><c> Calling presentation </c>
<c> 0x27 </c><c> CALLINGTON </c><c> Calling type of number </c>
<c> 0x28 </c><c> CALLINGTNS </c><c> Calling transit network select </c>
<c> 0x29 </c><c> SAMPLINGRATE </c><c> Supported sampling rates </c>
<c> 0x2a </c><c> CAUSECODE </c><c> Hangup cause </c>
<c> 0x2b </c><c> ENCRYPTION </c><c> Encryption format </c>
<c> 0x2c </c><c> ENCKEY </c><c> Reserved for future Use </c>
<c> 0x2d </c><c> CODEC PREFS </c><c> CODEC Negotiation </c>
<c> 0x2e </c><c> RR JITTER </c><c> Received jitter, as in rfc3550 </c>
<c> 0x2f </c><c> RR LOSS </c><c> Received loss, as in rfc3550 </c>
<c> 0x30 </c><c> RR PKTS </c><c> Received frames </c>
<c> 0x31 </c><c> RR DELAY </c><c> Max playout delay for received frames in ms </c>
<c> 0x32 </c><c> RR DROPPED </c><c> Dropped frames (presumably by jitter buffer) </c>
<c> 0x33 </c><c> RR OOO </c><c> Frames received Out of Order </c>
<c> 0x34 </c><c> OSPTOKEN </c><c> OSP Token Block </c>
</texttable>
</section>
<section title='Authentication Methods' anchor='ie.authmethods'>
<t> Registry Name: IAX Authentication Methods</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.6.13 of <xref target="IAX" />. </t>
<t> Valid Range: 0x0001-xFFFF. </t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the initial assignments of
IAX Authentication Methods:</preamble>
<ttcol> METHOD </ttcol><ttcol> DESCRIPTION </ttcol>
<c> 0x0001 </c><c> Reserved (was Plaintext) </c>
<c> 0x0002 </c><c> MD5 </c>
<c> 0x0004 </c><c> RSA </c>
</texttable>
</section>
<section title='Dialplan Status Flags' anchor='ie.dpstatus'>
<t> Registry Name: IAX Dialplan Status Flags</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.6.19 of <xref target="IAX" />. </t>
<t> Valid Range: 0x0001-xFFFF. </t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the initial assignments of IAX dialplan status flags:</preamble>
<ttcol> FLAG </ttcol><ttcol> DESCRIPTION </ttcol>
<c> 0x0001 </c><c> Exists </c>
<c> 0x0002 </c><c> Can exist </c>
<c> 0x0004 </c><c> Non-existent </c>
<c> 0x4000 </c><c> Retain dialtone (ignorepat) </c>
<c> 0x8000 </c><c> More digits may match number </c>
</texttable>
</section>
<section title='Calling Presentation' anchor='ie.callingpres'>
<t> Registry Name: IAX Calling Presentation</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.6.29 of <xref target="IAX" />. </t>
<t> Valid Range: 0x00-xFF. </t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the initial assignments of calling presentation values:</preamble>
<!-- table filled in from callerid.h. Is this the complete set of sane presentations, or should I include the raw defines as well? -->
<ttcol> FLAG </ttcol><ttcol> PRESENTATION </ttcol>
<c> 0x00 </c><c> Allowed user/number not screened </c>
<c> 0x01 </c><c> Allowed user/number passed screen </c>
<c> 0x02 </c><c> Allowed user/number failed screen </c>
<c> 0x03 </c><c> Allowed network number </c>
<c> 0x20 </c><c> Prohibited user/number not screened </c>
<c> 0x21 </c><c> Prohibited user/number passed screen </c>
<c> 0x22 </c><c> Prohibited user/number failed screen </c>
<c> 0x23 </c><c> Prohibited network number </c>
<c> 0x43 </c><c> Number not available </c>
</texttable>
<t>NOTE: The values in this table are derived from Q.931, however, future values may be from other sources.</t>
</section>
<section title='Calling Type of Number (CALLINGTON)' anchor='ie.callington'>
<t> Registry Name: IAX Calling Type of Number</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.6.30 of <xref target="IAX" />. </t>
<t> Valid Range: 0x00-xFF. </t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the initial assignments of valid calling type of number values:</preamble>
<ttcol> VALUE </ttcol><ttcol> DESCRIPTION </ttcol>
<c> 0x00 </c><c> Unknown </c>
<c> 0x10 </c><c> International Number </c>
<c> 0x20 </c><c> National Number </c>
<c> 0x30 </c><c> Network Specific Number </c>
<c> 0x40 </c><c> Subscriber Number </c>
<c> 0x60 </c><c> Abbreviated Number </c>
<c> 0x70 </c><c> Reserved for extension </c>
</texttable>
<t>NOTE: The values in this table are derived from Q.931, however, future values may be from other sources.</t>
<!-- The second octet can only carry one UTF-8 char, is that sufficient? -->
</section>
<section title='IAX Transit Network Identification' anchor='ie.callingtns'>
<t> Registry Name: IAX Transit Network Identification Plan</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.6.31 of <xref target="IAX" />. </t>
<t> Valid Range: 0000-1111 (four bits). </t>
<t> Display format: binary. </t>
<texttable>
<preamble>The following table specifies the initial assignments of IAX Calling Type of Number values:</preamble>
<ttcol> BITS </ttcol><ttcol> DESCRIPTION </ttcol>
<c> 0000 </c><c> Unknown </c>
<c> 0001 </c><c> Caller Identification Code </c>
<c> 0011 </c><c> Data Network Identification Code </c>
</texttable>
<t>NOTE: The values in this table are derived from Q.931, however, future values may be from other sources.</t>
</section>
<section title='IAX Type of Network' anchor='ie.callingtns2'>
<t> Registry Name: IAX Type of Network</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.6.30 of <xref target="IAX" />. </t>
<t> Valid Range: 000-111 (three bits). </t>
<t> Display format: binary. </t>
<texttable>
<preamble>The following table specifies the initial assignments of IAX Calling Type of Network values:</preamble>
<ttcol> BITS </ttcol><ttcol> DESCRIPTION </ttcol>
<c> 000 </c><c> User Specified </c>
<c> 010 </c><c> National Network Identification </c>
<c> 011 </c><c> International Network Identification </c>
</texttable>
<t>NOTE: The values in this table are derived from Q.931, however, future values may be from other sources.</t>
</section>
<section title='Cause Codes' anchor='ie.causecode'>
<t> Registry Name: IAX Cause Codes</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.6.30 of <xref target="IAX" />. </t>
<t> Valid Range: 1-255. </t>
<t> Display format: decimal. </t>
<texttable>
<preamble>The following table specifies the initial assignments of IAX Cause Code values:</preamble>
<ttcol>NUMBER</ttcol><ttcol>CAUSE</ttcol>
<c> 1 </c><c> Unassigned/unallocated number </c>
<c> 2 </c><c> No route to specified transit network </c>
<c> 3 </c><c> No route to destination </c>
<c> 6 </c><c> Channel unacceptable </c>
<c> 7 </c><c> Call awarded and delivered </c>
<c> 16 </c><c> Normal call clearing </c>
<c> 17 </c><c> User busy </c>
<c> 18 </c><c> No user response </c>
<c> 19 </c><c> No answer </c>
<c> 21 </c><c> Call rejected </c>
<c> 22 </c><c> Number changed </c>
<c> 27 </c><c> Destination out of order </c>
<c> 28 </c><c> Invalid number format/incomplete number </c>
<c> 29 </c><c> Facility rejected </c>
<c> 30 </c><c> Response to status enquiry </c>
<c> 31 </c><c> Normal, unspecified </c>
<c> 34 </c><c> No circuit/channel available </c>
<c> 38 </c><c> Network out of order </c>
<c> 41 </c><c> Temporary failure </c>
<c> 42 </c><c> Switch congestion </c>
<c> 43 </c><c> Access information discarded </c>
<c> 44 </c><c> Requested channel not available </c>
<c> 45 </c><c> Pre-empted (causes.h only)</c>
<c> 47 </c><c> Resource unavailable, unspecified (Q.931 only)</c>
<c> 50 </c><c> Facility not subscribed (causes.h only)</c>
<c> 52 </c><c> Outgoing call barred (causes.h only)</c>
<c> 54 </c><c> Incoming call barred (causes.h only)</c>
<c> 57 </c><c> Bearer capability not authorized </c>
<c> 58 </c><c> Bearer capability not available </c>
<c> 63 </c><c> Service or option not available (Q.931 only)</c>
<c> 65 </c><c> Bearer capability not implemented </c>
<c> 66 </c><c> Channel type not implemented </c>
<c> 69 </c><c> Facility not implemented </c>
<c> 70 </c><c> Only restricted digital information bearer capability is available (Q.931 only)</c>
<c> 79 </c><c> Service or option not available (Q.931 only)</c>
<c> 81 </c><c> Invalid call reference </c>
<c> 82 </c><c> Identified channel does not exist (Q.931 only)</c>
<c> 83 </c><c> A suspended call exists, but this call identity does not (Q.931 only)</c>
<c> 84 </c><c> Call identity in use (Q.931 only)</c>
<c> 85 </c><c> No call suspended (Q.931 only)</c>
<c> 86 </c><c> Call has been cleared (Q.931 only)</c>
<c> 88 </c><c> Incompatible destination </c>
<c> 91 </c><c> Invalid transit network selection (Q.931 only)</c>
<c> 95 </c><c> Invalid message, unspecified </c>
<c> 96 </c><c> Mandatory information element missing (Q.931 only)</c>
<c> 97 </c><c> Message type nonexistent/not implemented </c>
<c> 98 </c><c> Message not compatible with call state </c>
<c> 99 </c><c> Information element nonexistent </c>
<c> 100 </c><c> Invalid information element contents </c>
<c> 101 </c><c> Message not compatible with call state </c>
<c> 102 </c><c> Recovery on timer expiration </c>
<c> 103 </c><c> Mandatory information element length error (causes.h only)</c>
<c> 111 </c><c> Protocol error, unspecified </c>
<c> 127 </c><c> Internetworking, unspecified </c>
</texttable>
</section>
<section title='Encryption Methods' anchor="ie.encrypt">
<t> Registry Name: IAX Encryption Methods</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.6.34 of <xref target="IAX" />. </t>
<t> Valid Range: 0x0001-x8000 Bitmask, values must be power of two.</t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the initial assignments of IAX encryption methods:</preamble>
<ttcol> METHOD </ttcol><ttcol> DESCRIPTION </ttcol>
<c> 0x0001 </c><c> AES-128 </c>
</texttable>
</section>
<section title="Media Formats" anchor="iax.mediaformats">
<t> Registry Name: IAX Media Formats</t>
<t> Required Information for New Values: Name, description, and relevant security considerations, if any.</t>
<t> Description: See Section 8.7 of <xref target="IAX" />. </t>
<t> Valid Range: 0x0001-x8000 Bitmask, values must be power of two.</t>
<t> Display format: hex. </t>
<texttable>
<preamble>The following table specifies the initial assignments of IAX Media Format Values</preamble>
<ttcol> SUBCLASS </ttcol><ttcol> DESCRIPTION </ttcol>
<c> 0x00000001 </c><c> G.723.1 </c>
<c> 0x00000002 </c><c> GSM Full Rate </c>
<c> 0x00000004 </c><c> G.711 mu-law </c>
<c> 0x00000008 </c><c> G.711 a-law </c>
<c> 0x00000010 </c><c> G.726 </c>
<c> 0x00000020 </c><c> IMA ADPCM </c>
<c> 0x00000040 </c><c> 16-bit linear little-endian </c>
<c> 0x00000080 </c><c> LPC10 </c>
<c> 0x00000100 </c><c> G.729 </c>
<c> 0x00000200 </c><c> Speex </c>
<c> 0x00000400 </c><c> ILBC </c>
<c> 0x00000800 </c><c> G.726 AAL2 </c>
<c> 0x00001000 </c><c> G.722 </c>
<c> 0x00002000 </c><c> AMR </c>
<c> 0x00010000 </c><c> JPEG </c>
<c> 0x00020000 </c><c> PNG </c>
<c> 0x00040000 </c><c> H.261 </c>
<c> 0x00080000 </c><c> H.263 </c>
<c> 0x00100000 </c><c> H.263p </c>
<c> 0x00200000 </c><c> H.264 </c>
</texttable>
</section>
</section>
<section title="Security Considerations" anchor="Security">
<t>This document defines IAX registries and as such does not raise security issues
beyond those discussed in <xref target="IAX" />.
</t>
</section>
<section title="Acknowledgments"> <t>
The author would like to thank
Marc Blanchet and Michelle Cotten
for their support and suggestions.
</t>
</section>
</middle>
<back>
<references title="Normative References">
&rfc5226;
<reference anchor="IAX">
<front>
<title abbrev="IAX Protocol">IAX: Inter-Asterisk eXchange Version 2</title>
<author initials="M." surname="Spencer" fullname="Mark Spencer"> <organization>Digium</organization></author>
<author initials="K." surname="Shumard" fullname="Kenneth Shumard"> <organization>Digium</organization></author>
<author initials="B." surname="Capouch" fullname="Brian Capouch"> <organization>Saint Joseph's College</organization></author>
<author initials="E.T." surname="Guy" fullname="Ed Guy"> <organization>TruPhone</organization></author>
<date year="2008" day="6" month="October"/>
</front>
<seriesInfo name="draft-guy-iax-05" value="Work In Progress"/>
</reference>
</references>
<!-- <references title="Informative References">
</references>
-->
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 06:49:00 |