Concept clearification of Transaction, dialog and call
2008-12-08 14:30
405 查看
A single SIP request and all its responses form a SIP transaction. Different types of
transaction are used for different protocol functions. For example, an INVITE starts a
telephone call, and a MESSAGE sends an instant message.
A SIP dialog is a persistent link between two devices that is used to associate transactions
and to provide ordering between them. SIP transactions can exist within or outside a SIP
dialog, and transactions are used to establish and terminate dialogs. For example, in
telephony, the initial INVITE that starts the call also establishes a dialog between the
participants. To end the call, one participant sends a BYE within the context of this
dialog. This BYE transaction terminates both the call and the associated dialog.
The high-level concept of a call does not simply map to a SIP dialog, because a single
telephone call may include conversations with several people and devices, for example
receptionists and voicemail systems. These individual connections need separate SIP
dialogs, so the call can contain multiple dialogs. SIP messages contain a call identifier
field (Call-ID) that is sometimes used to link the dialogs and transaction into an
application-level concept of a call, although this use is strictly outside the standard.
transaction are used for different protocol functions. For example, an INVITE starts a
telephone call, and a MESSAGE sends an instant message.
A SIP dialog is a persistent link between two devices that is used to associate transactions
and to provide ordering between them. SIP transactions can exist within or outside a SIP
dialog, and transactions are used to establish and terminate dialogs. For example, in
telephony, the initial INVITE that starts the call also establishes a dialog between the
participants. To end the call, one participant sends a BYE within the context of this
dialog. This BYE transaction terminates both the call and the associated dialog.
The high-level concept of a call does not simply map to a SIP dialog, because a single
telephone call may include conversations with several people and devices, for example
receptionists and voicemail systems. These individual connections need separate SIP
dialogs, so the call can contain multiple dialogs. SIP messages contain a call identifier
field (Call-ID) that is sometimes used to link the dialogs and transaction into an
application-level concept of a call, although this use is strictly outside the standard.
相关文章推荐
- Bjarne Stroustrup Expounds on Concepts and the Future of C++
- SIP 基本概念---Dialog,call,session 和 transaction .
- How JavaScript works: an overview of the engine, the runtime, and the call stack
- Understanding Windows CardSpace: An Introduction to the Concepts and Challenges of Digital Identitie
- 【转】SIP 中的Dialog,call,session 和 transaction
- SIP 中的Dialog,call,session 和 transaction
- The Why and the How of the Long Transaction
- Contracted Concept and Dimensions of International Law
- The Call of the Wild——2、The law of club and tooth
- SIP 中的Dialog,call,session 和 transaction
- Change ICON of MFC Application and Dialog
- SIP 中的Dialog,call,session 和 transaction
- Machine learning of neural representations of suicide and emotion concepts identifies suicidal youth
- const at the end of function and passing const object in a function call
- Sip协议中Call, Dialog, Transaction和Message之间的关系
- Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements
- Difference Between CALL TRANSACTION and SESSION METHOD
- Junit 4 Core Concept [3] suit of test cases and suit of suits
- SIP 中的Dialog,call,session 和 transaction .
- 解决No Hibernate Session bound to thread, and configuration does not allow creation of non-transaction