RFC4967 · Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier
Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier
RFC 3966 explicitly states that 'tel' URIs may not represent a dial string. That leaves no way specify a dial string in a standardized way. Great confusion exists with the SIP URI parameter "user=phone", and specifically, if it can represent a dial string. This memo creates a new value for the user parameter "dialstring", so that one may specify "user=dialstring" to encode a dial string as a 'sip:' or 'sips:' URI. [STANDARDS-TRACK]
IETF · RFCОфициальная английская аннотация
RFC 3966 explicitly states that 'tel' URIs may not represent a dial string. That leaves no way specify a dial string in a standardized way. Great confusion exists with the SIP URI parameter "user=phone", and specifically, if it can represent a dial string. This memo creates a new value for the user parameter "dialstring", so that one may specify "user=dialstring" to encode a dial string as a 'sip:' or 'sips:' URI. [STANDARDS-TRACK]
{
"id": "RFC4967",
"number": 4967,
"title_en": "Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier",
"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": "RFC 3966 explicitly states that 'tel' URIs may not represent a dial string. That leaves no way specify a dial string in a standardized way. Great confusion exists with the SIP URI parameter \"user=phone\", and specifically, if it can represent a dial string. This memo creates a new value for the user parameter \"dialstring\", so that one may specify \"user=dialstring\" to encode a dial string as a 'sip:' or 'sips:' URI. [STANDARDS-TRACK]",
"authors": [
"B. Rosen"
],
"organizations": [],
"publication_date": "2007-07-01",
"current_status": "PROPOSED STANDARD",
"current_status_ru": "Предлагаемый стандарт",
"publication_status": "PROPOSED STANDARD",
"publication_status_ru": "Предлагаемый стандарт",
"lifecycle": "active",
"lifecycle_ru": "Действующий",
"stream": "IETF",
"stream_ru": "IETF",
"area": "",
"area_ru": "",
"working_group": "NON WORKING GROUP",
"source_draft": "draft-rosen-iptel-dialstring-05",
"page_count": 6,
"doi": "10.17487/RFC4967",
"keywords": [
"dialstring"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc4967/",
"html": "https://www.rfc-editor.org/rfc/rfc4967.html",
"txt": "https://www.rfc-editor.org/rfc/rfc4967.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc4967/"
}
}