idnits 2.17.1 draft-guy-iaxiana-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.2b on line 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 936. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 947. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 954. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 960. -- The document has an RFC 3978 Section 5.2(b) Derivative Works Limitation clause. If this document is intended for submission to the IESG for publication, this constitutes an error. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 5, 2008) is 5680 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 E. Guy, Ed. 3 Internet-Draft TruPhone 4 Intended status: Informational October 5, 2008 5 Expires: April 8, 2009 7 IANA Considerations for IAX: Inter-Asterisk eXchange Version 2 8 draft-guy-iaxiana-00 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 This document may not be modified, and derivative works of it may not 17 be created. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on April 8, 2009. 37 Abstract 39 This document establishes the IANA registries for IAX, the Inter- 40 Asterisk eXchange protocol, an application-layer control and media 41 protocol for creating, modifying, and terminating multimedia sessions 42 over Internet Protocol (IP) networks. IAX was developed by the open 43 source community for the Asterisk PBX and is targeted primarily at 44 Voice over Internet Protocol (VoIP) call control, but it can be used 45 with streaming video or any other type of multimedia. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 51 2.1. Meta Command . . . . . . . . . . . . . . . . . . . . . . . 4 52 2.2. Frame Types . . . . . . . . . . . . . . . . . . . . . . . 4 53 2.3. Control Frame Subclass . . . . . . . . . . . . . . . . . . 5 54 2.4. IAX Control Frames . . . . . . . . . . . . . . . . . . . . 7 55 2.5. HTML Command Subclasses . . . . . . . . . . . . . . . . . 9 56 2.6. Information Elements . . . . . . . . . . . . . . . . . . . 9 57 2.7. Authentication Methods . . . . . . . . . . . . . . . . . . 12 58 2.8. Dialplan Status Flags . . . . . . . . . . . . . . . . . . 13 59 2.9. Calling Presentation . . . . . . . . . . . . . . . . . . . 13 60 2.10. Calling Type of Number (CALLINGTON) . . . . . . . . . . . 14 61 2.11. IAX Transit Network Identification . . . . . . . . . . . . 15 62 2.12. IAX Type of Network . . . . . . . . . . . . . . . . . . . 16 63 2.13. Cause Codes . . . . . . . . . . . . . . . . . . . . . . . 16 64 2.14. Encryption Methods . . . . . . . . . . . . . . . . . . . . 19 65 2.15. Media Formats . . . . . . . . . . . . . . . . . . . . . . 20 66 3. Security Considerations . . . . . . . . . . . . . . . . . . . 22 67 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 68 5. Normative References . . . . . . . . . . . . . . . . . . . . . 24 69 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 25 70 Intellectual Property and Copyright Statements . . . . . . . . . . 26 72 1. Introduction 74 IAX (Inter-Asterisk eXchange) is an "all in one" protocol for 75 handling multimedia in IP networks. It combines both control and 76 media services in the same protocol. In addition, IAX uses a single 77 UDP data stream on a static port greatly simplifying Network Address 78 Translation (NAT) gateway traversal, eliminating the need for other 79 protocols to work around NAT, and simplifying network and firewall 80 management. IAX employs a compact encoding which decreases bandwidth 81 usage and is well suited for Internet telephony service. In 82 addition, its open nature permits new payload types additions needed 83 to support additional services. 85 This document specifies and provides the initial values for the 86 creation of the IAX-related IANA registries as per [RFC5226]. 88 2. IANA Considerations 90 The IAX protocol, as defined in [IAX], defines 15 namespaces that 91 require registration. These namespaces are described below. 93 Each of these namespaces utilize an 'Expert Review' for extension. 94 Documentation of new values is not mandated as RFCs. The expert 95 review should be guided by a few common sense considerations. For 96 example, new values should not be specific to a country, region, 97 organization, or company; they should be well- defined and widely 98 recognized. 100 2.1. Meta Command 102 Registry Name: IAX Meta Commands 104 Required Information for New Values: Name, description, and relevant 105 security considerations, if any. 107 Description: See Section 8.1.3.2 of [IAX]. 109 Valid Range: 0x01-x7F. 111 Display format: hex. 113 The following table specifies the Initial Assignments of Meta Command 114 values: 116 +------+-----------------+------------------------------------------+ 117 | TYPE | Name | Description | 118 +------+-----------------+------------------------------------------+ 119 | 0x01 | Trunk Meta | Indicates that frame is a trunk meta | 120 | | Frame | frame. | 121 +------+-----------------+------------------------------------------+ 123 2.2. Frame Types 125 Registry Name: IAX Frame Types 127 Required Information for New Values: Name, description, and relevant 128 security considerations, if any. In addition, the definition and 129 description of subclasses. 131 Description: See Section 8.2 of [IAX]. 133 Valid Range: 0x01-xFF. 135 Display format: hex. 137 The following table specifies the Initial Assignments of Frame Type 138 Values: 140 +------+-------------+--------------------------+-------------------+ 141 | TYPE | Description | Subclass Description | Data Description | 142 +------+-------------+--------------------------+-------------------+ 143 | 0x01 | DTMF | 0-9, A-D, *, # | Undefined | 144 | | | | | 145 | 0x02 | Voice | Audio Compression Format | Data | 146 | | | | | 147 | 0x03 | Video | Video Compression Format | Data | 148 | | | | | 149 | 0x04 | Control | See Control Frame | Varies with | 150 | | | Subclass | subclass | 151 | | | | | 152 | 0x05 | Null | Undefined | Undefined | 153 | | | | | 154 | 0x06 | IAX Control | See IAX Protocol | Information | 155 | | | Messages | Elements | 156 | | | | | 157 | 0x07 | Text | Always 0 | Raw Text | 158 | | | | | 159 | 0x08 | Image | Image Compression Format | Raw image | 160 | | | | | 161 | 0x09 | HTML | See HTML Frame Types | Message Specific | 162 | | | | | 163 | 0x0A | Comfort | Level in -dBov of | None | 164 | | Noise | comfort noise | | 165 +------+-------------+--------------------------+-------------------+ 167 2.3. Control Frame Subclass 169 Registry Name: IAX Control Frame Subclass 171 Required Information for New Values: Name, description, and relevant 172 security considerations, if any. 174 Description: See Section 8.3 of [IAX]. 176 Valid Range: 0x00-x7F. 178 Display format: hex. 180 The following table specifies the Initial Assignments of Control 181 Frame Subclasses: 183 +-------------+---------------+-------------------------------------+ 184 | VALUE | Name | Description | 185 +-------------+---------------+-------------------------------------+ 186 | 0x01 | Hangup | The call has been hungup at the | 187 | | | remote end. | 188 | | | | 189 | 0x02 | Reserved | Reserved for future use | 190 | | | | 191 | 0x03 | Ringing | Remote end is ringing (ringback) | 192 | | | | 193 | 0x04 | Answer | Remote end has answered | 194 | | | | 195 | 0x05 | Busy | Remote end is busy | 196 | | | | 197 | 0x06 | Reserved | Reserved for future use | 198 | | | | 199 | 0x07 | Reserved | Reserved for future use | 200 | | | | 201 | 0x08 | Congestion | The call is congested. | 202 | | | | 203 | 0x09 | Flash Hook | Flash hook | 204 | | | | 205 | 0x0a | Reserved | Reserved for future use | 206 | | | | 207 | 0x0b | Option | Device-specific options are being | 208 | | | transmitted | 209 | | | | 210 | 0x0c | Key Radio | Key Radio | 211 | | | | 212 | 0x0d | Unkey Radio | Unkey Radio | 213 | | | | 214 | 0x0e | Call Progress | Call is in progress | 215 | | | | 216 | 0x0f | Call | Call is proceeding | 217 | | Proceeding | | 218 | | | | 219 | 0x10 | Hold | Call is placed on hold | 220 | | | | 221 | 0x11 | Unhold | Call is taken off hold | 222 +-------------+---------------+-------------------------------------+ 224 2.4. IAX Control Frames 226 Registry Name: IAX Control Frame Subclass 228 Required Information for New Values: Name, description, and relevant 229 security considerations, if any. 231 Description: See Section 8.4 of [IAX]. 233 Valid Range: 0x01-x7F. 235 Display format: hex. 237 The following table specifies the Initial Assignments of IAX Control 238 Frame values: 240 +------+-----------+-----------------------------------------+ 241 | Hex | Name | Description | 242 +------+-----------+-----------------------------------------+ 243 | 0x01 | NEW | Initiate a new call | 244 | | | | 245 | 0x02 | PING | Ping request | 246 | | | | 247 | 0x03 | PONG | Ping or poke reply | 248 | | | | 249 | 0x04 | ACK | Explicit acknowledgment | 250 | | | | 251 | 0x05 | HANGUP | Initiate call tear-down | 252 | | | | 253 | 0x06 | REJECT | Reject a call | 254 | | | | 255 | 0x07 | ACCEPT | Accept a call | 256 | | | | 257 | 0x08 | AUTHREQ | Authentication request | 258 | | | | 259 | 0x09 | AUTHREP | Authentication reply | 260 | | | | 261 | 0x0a | INVAL | Invalid message | 262 | | | | 263 | 0x0b | LAGRQ | Lag request | 264 | | | | 265 | 0x0c | LAGRP | Lag reply | 266 | | | | 267 | 0x0d | REGREQ | Registration request | 268 | | | | 269 | 0x0e | REGAUTH | Registration authentication | 270 | | | | 271 | 0x0f | REGACK | Registration acknowledgement | 272 | 0x10 | REGREJ | Registration reject | 273 | | | | 274 | 0x11 | REGREL | Registration release | 275 | | | | 276 | 0x12 | VNAK | Video/Voice retransmit request | 277 | | | | 278 | 0x13 | DPREQ | Dialplan request | 279 | | | | 280 | 0x14 | DPREP | Dialplan reply | 281 | | | | 282 | 0x15 | DIAL | Dial | 283 | | | | 284 | 0x16 | TXREQ | Transfer request | 285 | | | | 286 | 0x17 | TXCNT | Transfer connect | 287 | | | | 288 | 0x18 | TXACC | Transfer accept | 289 | | | | 290 | 0x19 | TXREADY | Transfer ready | 291 | | | | 292 | 0x1a | TXREL | Transfer release | 293 | | | | 294 | 0x1b | TXREJ | Transfer reject | 295 | | | | 296 | 0x1c | QUELCH | Halt audio/video [media] transmission | 297 | | | | 298 | 0x1d | UNQUELCH | Resume audio/video [media] transmission | 299 | | | | 300 | 0x1e | POKE | Poke request | 301 | | | | 302 | 0x1f | Reserved | Reserved for future use | 303 | | | | 304 | 0x20 | MWI | Message waiting indication | 305 | | | | 306 | 0x21 | UNSUPPORT | Unsupported message | 307 | | | | 308 | 0x22 | TRANSFER | Remote transfer request | 309 | | | | 310 | 0x23 | Reserved | Reserved for future use | 311 | | | | 312 | 0x24 | Reserved | Reserved for future use | 313 | | | | 314 | 0x25 | Reserved | Reserved for future use | 315 +------+-----------+-----------------------------------------+ 317 2.5. HTML Command Subclasses 319 Registry Name: IAX HTML Command Subclasses 321 Required Information for New Values: Name, description, and relevant 322 security considerations, if any. 324 Description: See Section 8.2 of [IAX]. 326 Valid Range: 0x01-x7F. 328 Display format: hex. 330 The following table specifies the Initial Assignments of IAX HTML 331 Command Subclasses: 333 +--------+----------------------------+ 334 | NUMBER | DESCRIPTION | 335 +--------+----------------------------+ 336 | 0x01 | Sending a URL | 337 | | | 338 | 0x02 | Data frame | 339 | | | 340 | 0x04 | Beginning frame | 341 | | | 342 | 0x08 | End frame | 343 | | | 344 | 0x10 | Load is complete | 345 | | | 346 | 0x11 | Peer does not support HTML | 347 | | | 348 | 0x12 | Link URL | 349 | | | 350 | 0x13 | Unlink URL | 351 | | | 352 | 0x14 | Reject Link URL | 353 +--------+----------------------------+ 355 2.6. Information Elements 357 Registry Name: IAX Information Elements 359 Required Information for New Values: Name, description, and relevant 360 security considerations, if any. 362 Description: See Section 8.6 of [IAX]. 364 Valid Range: 0x01-xFF. 366 Display format: hex. 368 The following table specifies the Initial Assignments of Information 369 Element Definitions 371 +------+----------------+-------------------------------------------+ 372 | HEX | NAME | DESCRIPTION | 373 +------+----------------+-------------------------------------------+ 374 | HEX | NAME | DESCRIPTION | 375 | | | | 376 | 0x01 | CALLED NUMBER | Number/extension being called | 377 | | | | 378 | 0x02 | CALLING NUMBER | Calling number | 379 | | | | 380 | 0x03 | CALLING ANI | Calling number ANI for billing | 381 | | | | 382 | 0x04 | CALLING NAME | Name of caller | 383 | | | | 384 | 0x05 | CALLED CONTEXT | Context for number | 385 | | | | 386 | 0x06 | USERNAME | Username (peer or user) for | 387 | | | authentication | 388 | | | | 389 | 0x07 | PASSWORD | Password for authentication | 390 | | | | 391 | 0x08 | CAPABILITY | Actual CODEC capability | 392 | | | | 393 | 0x09 | FORMAT | Desired CODEC format | 394 | | | | 395 | 0x0a | LANGUAGE | Desired language | 396 | | | | 397 | 0x0b | VERSION | Protocol version | 398 | | | | 399 | 0x0c | ADSICPE | CPE ADSI capability | 400 | | | | 401 | 0x0d | DNID | Originally dialed DNID | 402 | | | | 403 | 0x0e | AUTHMETHODS | Authentication method(s) | 404 | | | | 405 | 0x0f | CHALLENGE | Challenge data for MD5/RSA | 406 | | | | 407 | 0x10 | MD5 RESULT | MD5 challenge result | 408 | | | | 409 | 0x11 | RSA RESULT | RSA challenge result | 410 | | | | 411 | 0x12 | APPARENT ADDR | Apparent address of peer | 412 | | | | 413 | 0x13 | REFRESH | When to refresh registration | 414 | 0x14 | DPSTATUS | Dialplan status | 415 | | | | 416 | 0x15 | CALLNO | Call number of peer | 417 | | | | 418 | 0x16 | CAUSE | Cause | 419 | | | | 420 | 0x17 | IAX UNKNOWN | Unknown IAX command | 421 | | | | 422 | 0x18 | MSGCOUNT | How many messages waiting | 423 | | | | 424 | 0x19 | AUTOANSWER | Request auto-answering | 425 | | | | 426 | 0x1a | MUSICONHOLD | Request musiconhold with QUELCH | 427 | | | | 428 | 0x1b | TRANSFERID | Transfer Request Identifier | 429 | | | | 430 | 0x1c | RDNIS | Referring DNIS | 431 | | | | 432 | 0x1d | Reserved | Reserved for future use | 433 | | | | 434 | 0x1e | Reserved | Reserved for future use | 435 | | | | 436 | 0x1f | DATETIME | Date/Time | 437 | | | | 438 | 0x20 | Reserved | Reserved for future use | 439 | | | | 440 | 0x21 | Reserved | Reserved for future use | 441 | | | | 442 | 0x22 | Reserved | Reserved for future use | 443 | | | | 444 | 0x23 | Reserved | Reserved for future use | 445 | | | | 446 | 0x24 | Reserved | Reserved for future use | 447 | | | | 448 | 0x25 | Reserved | Reserved for future use | 449 | | | | 450 | 0x26 | CALLINGPRES | Calling presentation | 451 | | | | 452 | 0x27 | CALLINGTON | Calling type of number | 453 | | | | 454 | 0x28 | CALLINGTNS | Calling transit network select | 455 | | | | 456 | 0x29 | SAMPLINGRATE | Supported sampling rates | 457 | | | | 458 | 0x2a | CAUSECODE | Hangup cause | 459 | | | | 460 | 0x2b | ENCRYPTION | Encryption format | 461 | | | | 462 | 0x2c | ENCKEY | Reserved for future Use | 463 | | | | 464 | 0x2d | CODEC PREFS | CODEC Negotiation | 465 | | | | 466 | 0x2e | RR JITTER | Received jitter, as in rfc3550 | 467 | | | | 468 | 0x2f | RR LOSS | Received loss, as in rfc3550 | 469 | | | | 470 | 0x30 | RR PKTS | Received frames | 471 | | | | 472 | 0x31 | RR DELAY | Max playout delay for received frames in | 473 | | | ms | 474 | | | | 475 | 0x32 | RR DROPPED | Dropped frames (presumably by jitter | 476 | | | buffer) | 477 | | | | 478 | 0x33 | RR OOO | Frames received Out of Order | 479 | | | | 480 | 0x34 | OSPTOKEN | OSP Token Block | 481 +------+----------------+-------------------------------------------+ 483 Table 1: Information Element Definitions 485 2.7. Authentication Methods 487 Registry Name: IAX Authentication Methods 489 Required Information for New Values: Name, description, and relevant 490 security considerations, if any. 492 Description: See Section 8.6.13 of [IAX]. 494 Valid Range: 0x0001-xFFFF. 496 Display format: hex. 498 The following table specifies the initial assignments of IAX 499 Authentication Methods: 501 +--------+--------------------------+ 502 | METHOD | DESCRIPTION | 503 +--------+--------------------------+ 504 | 0x0001 | Reserved (was Plaintext) | 505 | | | 506 | 0x0002 | MD5 | 507 | | | 508 | 0x0004 | RSA | 509 +--------+--------------------------+ 511 2.8. Dialplan Status Flags 513 Registry Name: IAX Dialplan Status Flags 515 Required Information for New Values: Name, description, and relevant 516 security considerations, if any. 518 Description: See Section 8.6.19 of [IAX]. 520 Valid Range: 0x0001-xFFFF. 522 Display format: hex. 524 The following table specifies the initial assignments of IAX dialplan 525 status flags: 527 +--------+------------------------------+ 528 | FLAG | DESCRIPTION | 529 +--------+------------------------------+ 530 | 0x0001 | Exists | 531 | | | 532 | 0x0002 | Can exist | 533 | | | 534 | 0x0004 | Non-existent | 535 | | | 536 | 0x4000 | Retain dialtone (ignorepat) | 537 | | | 538 | 0x8000 | More digits may match number | 539 +--------+------------------------------+ 541 2.9. Calling Presentation 543 Registry Name: IAX Calling Presentation 545 Required Information for New Values: Name, description, and relevant 546 security considerations, if any. 548 Description: See Section 8.6.29 of [IAX]. 550 Valid Range: 0x00-xFF. 552 Display format: hex. 554 The following table specifies the initial assignments of calling 555 presentation values: 557 +------+--------------------------------------+ 558 | FLAG | PRESENTATION | 559 +------+--------------------------------------+ 560 | 0x00 | Allowed user/number not screened | 561 | | | 562 | 0x01 | Allowed user/number passed screen | 563 | | | 564 | 0x02 | Allowed user/number failed screen | 565 | | | 566 | 0x03 | Allowed network number | 567 | | | 568 | 0x20 | Prohibited user/number not screened | 569 | | | 570 | 0x21 | Prohibited user/number passed screen | 571 | | | 572 | 0x22 | Prohibited user/number failed screen | 573 | | | 574 | 0x23 | Prohibited network number | 575 | | | 576 | 0x43 | Number not available | 577 +------+--------------------------------------+ 579 NOTE: The values in this table are derived from Q.931, however, 580 future values may be from other sources. 582 2.10. Calling Type of Number (CALLINGTON) 584 Registry Name: IAX Calling Type of Number 586 Required Information for New Values: Name, description, and relevant 587 security considerations, if any. 589 Description: See Section 8.6.30 of [IAX]. 591 Valid Range: 0x00-xFF. 593 Display format: hex. 595 The following table specifies the initial assignments of valid 596 calling type of number values: 598 +-------+-------------------------+ 599 | VALUE | DESCRIPTION | 600 +-------+-------------------------+ 601 | 0x00 | Unknown | 602 | | | 603 | 0x10 | International Number | 604 | | | 605 | 0x20 | National Number | 606 | | | 607 | 0x30 | Network Specific Number | 608 | | | 609 | 0x40 | Subscriber Number | 610 | | | 611 | 0x60 | Abbreviated Number | 612 | | | 613 | 0x70 | Reserved for extension | 614 +-------+-------------------------+ 616 NOTE: The values in this table are derived from Q.931, however, 617 future values may be from other sources. 619 2.11. IAX Transit Network Identification 621 Registry Name: IAX Transit Network Identification Plan 623 Required Information for New Values: Name, description, and relevant 624 security considerations, if any. 626 Description: See Section 8.6.31 of [IAX]. 628 Valid Range: 0000-1111 (four bits). 630 Display format: binary. 632 The following table specifies the initial assignments of IAX Calling 633 Type of Number values: 635 +------+----------------------------------+ 636 | BITS | DESCRIPTION | 637 +------+----------------------------------+ 638 | 0000 | Unknown | 639 | | | 640 | 0001 | Caller Identification Code | 641 | | | 642 | 0011 | Data Network Identification Code | 643 +------+----------------------------------+ 645 NOTE: The values in this table are derived from Q.931, however, 646 future values may be from other sources. 648 2.12. IAX Type of Network 650 Registry Name: IAX Type of Network 652 Required Information for New Values: Name, description, and relevant 653 security considerations, if any. 655 Description: See Section 8.6.30 of [IAX]. 657 Valid Range: 000-111 (three bits). 659 Display format: binary. 661 The following table specifies the initial assignments of IAX Calling 662 Type of Network values: 664 +------+--------------------------------------+ 665 | BITS | DESCRIPTION | 666 +------+--------------------------------------+ 667 | 000 | User Specified | 668 | | | 669 | 010 | National Network Identification | 670 | | | 671 | 011 | International Network Identification | 672 +------+--------------------------------------+ 674 NOTE: The values in this table are derived from Q.931, however, 675 future values may be from other sources. 677 2.13. Cause Codes 679 Registry Name: IAX Cause Codes 681 Required Information for New Values: Name, description, and relevant 682 security considerations, if any. 684 Description: See Section 8.6.30 of [IAX]. 686 Valid Range: 1-255. 688 Display format: decimal. 690 The following table specifies the initial assignments of IAX Cause 691 Code values: 693 +--------+----------------------------------------------------------+ 694 | NUMBER | CAUSE | 695 +--------+----------------------------------------------------------+ 696 | 1 | Unassigned/unallocated number | 697 | | | 698 | 2 | No route to specified transit network | 699 | | | 700 | 3 | No route to destination | 701 | | | 702 | 6 | Channel unacceptable | 703 | | | 704 | 7 | Call awarded and delivered | 705 | | | 706 | 16 | Normal call clearing | 707 | | | 708 | 17 | User busy | 709 | | | 710 | 18 | No user response | 711 | | | 712 | 19 | No answer | 713 | | | 714 | 21 | Call rejected | 715 | | | 716 | 22 | Number changed | 717 | | | 718 | 27 | Destination out of order | 719 | | | 720 | 28 | Invalid number format/incomplete number | 721 | | | 722 | 29 | Facility rejected | 723 | | | 724 | 30 | Response to status enquiry | 725 | | | 726 | 31 | Normal, unspecified | 727 | | | 728 | 34 | No circuit/channel available | 729 | | | 730 | 38 | Network out of order | 731 | | | 732 | 41 | Temporary failure | 733 | | | 734 | 42 | Switch congestion | 735 | | | 736 | 43 | Access information discarded | 737 | | | 738 | 44 | Requested channel not available | 739 | | | 740 | 45 | Pre-empted (causes.h only) | 741 | | | 742 | 47 | Resource unavailable, unspecified (Q.931 only) | 743 | | | 744 | 50 | Facility not subscribed (causes.h only) | 745 | | | 746 | 52 | Outgoing call barred (causes.h only) | 747 | | | 748 | 54 | Incoming call barred (causes.h only) | 749 | | | 750 | 57 | Bearer capability not authorized | 751 | | | 752 | 58 | Bearer capability not available | 753 | | | 754 | 63 | Service or option not available (Q.931 only) | 755 | | | 756 | 65 | Bearer capability not implemented | 757 | | | 758 | 66 | Channel type not implemented | 759 | | | 760 | 69 | Facility not implemented | 761 | | | 762 | 70 | Only restricted digital information bearer capability is | 763 | | available (Q.931 only) | 764 | | | 765 | 79 | Service or option not available (Q.931 only) | 766 | | | 767 | 81 | Invalid call reference | 768 | | | 769 | 82 | Identified channel does not exist (Q.931 only) | 770 | | | 771 | 83 | A suspended call exists, but this call identity does not | 772 | | (Q.931 only) | 773 | | | 774 | 84 | Call identity in use (Q.931 only) | 775 | | | 776 | 85 | No call suspended (Q.931 only) | 777 | | | 778 | 86 | Call has been cleared (Q.931 only) | 779 | | | 780 | 88 | Incompatible destination | 781 | | | 782 | 91 | Invalid transit network selection (Q.931 only) | 783 | | | 784 | 95 | Invalid message, unspecified | 785 | | | 786 | 96 | Mandatory information element missing (Q.931 only) | 787 | | | 788 | 97 | Message type nonexistent/not implemented | 789 | | | 790 | 98 | Message not compatible with call state | 791 | | | 792 | 99 | Information element nonexistent | 793 | | | 794 | 100 | Invalid information element contents | 795 | | | 796 | 101 | Message not compatible with call state | 797 | | | 798 | 102 | Recovery on timer expiration | 799 | | | 800 | 103 | Mandatory information element length error (causes.h | 801 | | only) | 802 | | | 803 | 111 | Protocol error, unspecified | 804 | | | 805 | 127 | Internetworking, unspecified | 806 +--------+----------------------------------------------------------+ 808 2.14. Encryption Methods 810 Registry Name: IAX Encryption Methods 812 Required Information for New Values: Name, description, and relevant 813 security considerations, if any. 815 Description: See Section 8.6.34 of [IAX]. 817 Valid Range: 0x0001-x8000 Bitmask, values must be power of two. 819 Display format: hex. 821 The following table specifies the initial assignments of IAX 822 encryption methods: 824 +--------+-------------+ 825 | METHOD | DESCRIPTION | 826 +--------+-------------+ 827 | 0x0001 | AES-128 | 828 +--------+-------------+ 830 2.15. Media Formats 832 Registry Name: IAX Media Formats 834 Required Information for New Values: Name, description, and relevant 835 security considerations, if any. 837 Description: See Section 8.7 of [IAX]. 839 Valid Range: 0x0001-x8000 Bitmask, values must be power of two. 841 Display format: hex. 843 The following table specifies the initial assignments of IAX Media 844 Format Values 846 +------------+-----------------------------+ 847 | SUBCLASS | DESCRIPTION | 848 +------------+-----------------------------+ 849 | 0x00000001 | G.723.1 | 850 | | | 851 | 0x00000002 | GSM Full Rate | 852 | | | 853 | 0x00000004 | G.711 mu-law | 854 | | | 855 | 0x00000008 | G.711 a-law | 856 | | | 857 | 0x00000010 | G.726 | 858 | | | 859 | 0x00000020 | IMA ADPCM | 860 | | | 861 | 0x00000040 | 16-bit linear little-endian | 862 | | | 863 | 0x00000080 | LPC10 | 864 | | | 865 | 0x00000100 | G.729 | 866 | | | 867 | 0x00000200 | Speex | 868 | | | 869 | 0x00000400 | ILBC | 870 | | | 871 | 0x00000800 | G.726 AAL2 | 872 | | | 873 | 0x00001000 | G.722 | 874 | | | 875 | 0x00002000 | AMR | 876 | | | 877 | 0x00010000 | JPEG | 878 | | | 879 | 0x00020000 | PNG | 880 | | | 881 | 0x00040000 | H.261 | 882 | | | 883 | 0x00080000 | H.263 | 884 | | | 885 | 0x00100000 | H.263p | 886 | | | 887 | 0x00200000 | H.264 | 888 +------------+-----------------------------+ 890 3. Security Considerations 892 This document defines IAX registries and as such does not raise 893 security issues beyond those discussed in [IAX]. 895 4. Acknowledgments 897 The author would like to thank Marc Blanchet and Michelle Cotten for 898 their support and suggestions. 900 5. Normative References 902 [IAX] Spencer, M., Shumard, K., Capouch, B., and E. Guy, "IAX: 903 Inter-Asterisk eXchange Version 2", draft-guy-iax-05 Work 904 In Progress, October 2008. 906 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 907 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 908 May 2008. 910 Author's Address 912 Ed Guy (editor) 913 TruPhone 914 235 Main Street, STE 253 915 Madison, NJ 07940 916 US 918 Phone: +1 973 437 4519 919 Email: edguy@emcsw.com 920 URI: http://www.TruPhone.com/ 922 Full Copyright Statement 924 Copyright (C) The IETF Trust (2008). 926 This document is subject to the rights, licenses and restrictions 927 contained in BCP 78, and except as set forth therein, the authors 928 retain all their rights. 930 This document and the information contained herein are provided on an 931 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 932 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 933 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 934 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 935 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 936 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 938 Intellectual Property 940 The IETF takes no position regarding the validity or scope of any 941 Intellectual Property Rights or other rights that might be claimed to 942 pertain to the implementation or use of the technology described in 943 this document or the extent to which any license under such rights 944 might or might not be available; nor does it represent that it has 945 made any independent effort to identify any such rights. Information 946 on the procedures with respect to rights in RFC documents can be 947 found in BCP 78 and BCP 79. 949 Copies of IPR disclosures made to the IETF Secretariat and any 950 assurances of licenses to be made available, or the result of an 951 attempt made to obtain a general license or permission for the use of 952 such proprietary rights by implementers or users of this 953 specification can be obtained from the IETF on-line IPR repository at 954 http://www.ietf.org/ipr. 956 The IETF invites any interested party to bring to its attention any 957 copyrights, patents or patent applications, or other proprietary 958 rights that may cover technology that may be required to implement 959 this standard. Please address the information to the IETF at 960 ietf-ipr@ietf.org.