Megaco/H.248 Packages per [RFC 3015] -Packages -Error Codes -ServiceChange Reasons The IANA will assign a serial number to each package meeting the conditions of registration (except for an update of an existing package, which retains the serial number of the package it is updating), in consecutive order of registration. The serial number will be used to identify the package in the binary-coded version of the Megaco/H.248 protocol. Serial number 0 is reserved, and the initial tabulation of public packages is given below. Public packages MUST be given serial numbers in the range 0x0001 to 0x7fff. Private packages MUST be given serial numbers in the range 0x8000 to 0xffff. IANA will maintain the currency and public availability of the tabulation of public and private packages. Packages will be listed in increasing order of serial number. Updates to packages will be listed in increasing order of version number. Tabulation Of Public Packages Serial Text Name Ver Extends Status* Reference/Contact ------ --------- --- ----------- ------ ----------------- Ser Ver ------ --- 0x0001 g 1 - - Final Annex E of [RFC3015] or ITU-T Rec. H.248 ITU TSB Place des Nations CH-1211 Geneva 20 tsbmail@itu.int 0x0002 root 1 - - Final ditto 0x0003 tonegen 1 - - Final ditto 0x0004 tonedet 1 - - Final ditto 0x0005 dg 1 0x0003 1 Final ditto 0x0006 dd 1 0x0004 1 Final ditto 0x0007 cg 1 0x0003 1 Final ditto 0x0008 cd 1 0x0004 1 Final ditto 0x0009 al 1 - - Final ditto 0x000a ct 1 - - Final ditto 0x000b nt 1 - - Final ditto 0x000c rtp 1 0x000b 1 Final ditto 0x000d tdmc 1 0x000b 1 Final ditto 0x000e ftmd 1 0x0004 1 Final RFC yyyy /H.248 Annex F ITU TSB at above address 0x000f txc 1 - - Final ditto 0x0010 txp 1 - - Final ditto 0x0011 ctyp 1 - - Final ditto 0x0012 fax 1 - - Final ditto 0x0013 ipfax 1 - - Final ditto 0x0014 dis 1 - - Final RFC yyyy /H.248 Annex G ITU TSB at above address 0x0015 key 1 - - Final ditto 0x0016 kp 1 0x0015 1 Final ditto 0x0017 labelkey 1 0x0015 1 Final ditto 0x0018 kf 1 0x0017 1 Final ditto 0x0019 ind 1 - - Final ditto 0x001a ks 1 0x0017 1 Final ditto 0x001b anci 1 - - Final ditto 0x001c dtd 1 - - Final RFC yyyy /H.248 Annex J ITU TSB at above address 0x001d an 1 - - Final RFC yyyy /H.248 Annex K ITU TSB at above address 0x001e bcp 1 - - IP 06/01 Bearer Q.1950 Annex A Characteristics ITU TSB at above address 0x001f bnct 1 - - IP 06/01 Bearer Network Q.1950 Annex A Connection Cut ITU TSB at above address 0x0020 ri 1 - - IP 06/01 Reuse Idle Q.1950 Annex A ITU TSB at above address 0x0021 gb 1 - - IP 06/01 Generic Bearer Q.1950 Annex A Connection ITU TSB at above address 0x0022 bt 1 - - IP 06/01 Bearer Control Q.1950 Annex A Tunnelling ITU TSB at above address 0x0023 bcg 1 0x0003 1 IP 06/01 Basic Call Q.1950 Annex A Progress Tones ITU TSB at above address 0x0024 xcg 1 0x0003 1 IP 06/01 Expanded Call Q.1950 Annex A Progress Tones ITU TSB at above address 0x0025 srvtn 1 0x0003 1 IP 06/01 Basic Services Q.1950 Annex A Tones ITU TSB at above address 0x0026 xsrvtn 1 0x0003 1 IP 06/01 Expanded Services Q.1950 Annex A Tones ITU TSB at above address 0x0027 int 1 0x0003 1 IP 06/01 Intrusion Q.1950 Annex A Tones ITU TSB at above address 0x0028 biztn 1 0x0003 1 IP 06/01 Business Q.1950 Annex A Tones ITU TSB at above address 0x0029 chp 1 - - IP 06/01 Congestion H.248 Annex N Handling ITU TSB at above address * "Status" - whether the package is still being finalized ("IP" = In Progress, with expected completion date) or is final. Error Codes ----------- Errors consist of an IANA registered error code and an explanatory string. Sending the explanatory string is optional. Implementations are encouraged to append diagnostic information to the end of the string. When a MG reports an error to a MGC, it does so in an error descriptor. An error descriptor consists of an error code and optionally the associated explanatory string. The identified error codes are: References ------------------------------ ---------- 400 - Syntax error in message 401 - Protocol Error 402 - Unauthorized 403 - Syntax error in transaction request 406 - Version Not Supported 410 - Incorrect identifier 411 - The transaction refers to an unknown ContextId 412 - No ContextIDs available 421 - Unknown action or illegal combination of actions 422 - Syntax Error in Action 430 - Unknown TerminationID 431 - No TerminationID matched a wildcard 432 - Out of TerminationIDs or No TerminationID available 433 - TerminationID is already in a Context 434 - Max number of Terminations in a Context exceeded 440 - Unsupported or unknown Package 441 - Missing Remote or Local Descriptor 442 - Syntax Error in Command 443 - Unsupported or Unknown Command 444 - Unsupported or Unknown Descriptor 445 - Unsupported or Unknown Property 446 - Unsupported or Unknown Parameter 447 - Descriptor not legal in this command 448 - Descriptor appears twice in a command 450 - No such property in this package 451 - No such event in this package 452 - No such signal in this package 453 - No such statistic in this package 454 - No such parameter value in this package 455 - Parameter illegal in this Descriptor 456 - Parameter or Property appears twice in this Descriptor 457 - Missing parameter in signal or event 471 - Implied Add for Multiplex failure 500 - Internal software Failure in MG 501 - Not Implemented 502 - Not ready. 503 - Service Unavailable 504 - Command Received from unauthorized entity 505 - Transaction Request Received before a Service Change 510 - Insufficient resources 512 - Media Gateway unequipped to detect requested Event 513 - Media Gateway unequipped to generate requested Signals 514 - Media Gateway cannot send the specified announcement 515 - Unsupported Media Type 517 - Unsupported or invalid mode 518 - Event buffer full 519 - Out of space to store digit map 520 - Digit Map undefined in the MG 521 - Termination is "ServiceChangeing" 526 - Insufficient bandwidth 529 - Internal hardware failure in MG 530 - Temporary Network failure 531 - Permanent Network failure 581 - Does Not Exist ServiceChange Reasons --------------------- The ServiceChangeReason parameter specifies the reason why the ServiceChange has or will occur. It consists of an alphanumeric token and, optionally, an explanatory string. The following ServiceChangeReasons are defined. The Reference for the below defined ServiceChange Reasons is [RFC3015] unless otherwise noted. ServiceChangeReasons References -------------------- ---------- 900 Service Restored 901 Cold Boot 902 Warm Boot 903 MGC Directed Change 904 Termination malfunctioning 905 Termination taken out of service 906 Loss of lower layer connectivity (e.g. downstream sync) 907 Transmission Failure 908 MG Impending Failure 909 MGC Impending Failure 910 Media Capability Failure 911 Modem Capability Failure 912 Mux Capability Failure 913 Signal Capability Failure 914 Event Capability Failure 915 State Loss References ---------- [RFC3015] R. Cuervo, N. Greene, C. Huitema, A. Rayhan, B. Rosen, and J. Segers, "Megaco Protocol", RFC 3015, November 2000. People ------ (last updated 02/23/01) (created 10/00) []