RFC5947 · Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)
Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)
This document states requirements for a standardized SIP registration mechanism for multiple addresses of record (AORs), the mechanism being suitable for deployment by SIP service providers on a large scale in support of small to medium sized Private Branch Exchanges (PBXs). The requirements are for a solution that can, as a minimum, support AORs based on E.164 numbers. This document is not an Internet Standards Track specification; it is published for informational purposes.
IETF · RFCОфициальная английская аннотация
This document states requirements for a standardized SIP registration mechanism for multiple addresses of record (AORs), the mechanism being suitable for deployment by SIP service providers on a large scale in support of small to medium sized Private Branch Exchanges (PBXs). The requirements are for a solution that can, as a minimum, support AORs based on E.164 numbers. This document is not an Internet Standards Track specification; it is published for informational purposes.
{
"id": "RFC5947",
"number": 5947,
"title_en": "Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "This document states requirements for a standardized SIP registration mechanism for multiple addresses of record (AORs), the mechanism being suitable for deployment by SIP service providers on a large scale in support of small to medium sized Private Branch Exchanges (PBXs). The requirements are for a solution that can, as a minimum, support AORs based on E.164 numbers. This document is not an Internet Standards Track specification; it is published for informational purposes.",
"authors": [
"J. Elwell",
"H. Kaplan"
],
"organizations": [],
"publication_date": "2010-09-01",
"current_status": "INFORMATIONAL",
"current_status_ru": "Информационный",
"publication_status": "INFORMATIONAL",
"publication_status_ru": "Информационный",
"lifecycle": "informational",
"lifecycle_ru": "Справочный",
"stream": "IETF",
"stream_ru": "IETF",
"area": "rai",
"area_ru": "rai",
"working_group": "martini",
"source_draft": "draft-ietf-martini-reqs-09",
"page_count": 13,
"doi": "10.17487/RFC5947",
"keywords": [
"Trunking",
"pbx",
"private branch exchange"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc5947/",
"html": "https://www.rfc-editor.org/rfc/rfc5947.html",
"txt": "https://www.rfc-editor.org/rfc/rfc5947.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc5947/"
}
}