2007
DOI: 10.17487/rfc5057
|View full text |Cite
|
Sign up to set email alerts
|

Multiple Dialog Usages in the Session Initiation Protocol

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0

Year Published

2007
2007
2015
2015

Publication Types

Select...
6
1

Relationship

2
5

Authors

Journals

citations
Cited by 8 publications
(14 citation statements)
references
References 2 publications
0
14
0
Order By: Relevance
“…If multiple usages [RFC5057] are used within an early dialog, and it is not clear which dialog usage the 199 response terminates, SIP entities that keep dialog state SHALL NOT release resources associated with the early dialog when they receive the 199 response.…”
Section: User Agent Client Behaviormentioning
confidence: 99%
“…If multiple usages [RFC5057] are used within an early dialog, and it is not clear which dialog usage the 199 response terminates, SIP entities that keep dialog state SHALL NOT release resources associated with the early dialog when they receive the 199 response.…”
Section: User Agent Client Behaviormentioning
confidence: 99%
“…However, the approach described in this document is to avoid dialog reuse. The issues and difficulties associated with dialog reuse are described in [RFC5057].…”
Section: Using Refer To Achieve Call Transfermentioning
confidence: 99%
“…This specification is based on a header field first proposed by Robert Sparks in the dialog usage draft [12]. John Elwell provided helpful comments.…”
Section: Acknowledgementsmentioning
confidence: 99%
“…Current implementations deal with this by sending the REFER on the same dialog as the one in place between user agents A and B. However, this approach has numerous problems [12]. These problems include difficulties in determining the lifecycle of the dialog and its usages and in determining which messages are associated with each application usage.…”
Section: Introductionmentioning
confidence: 99%