11. Example Message Flows
The next section shows call flow and message examples. The flows and descriptions are non-normative. Note that, in these examples, all INVITEs sent by a UA in the group will be From the shared AOR (sip:HelpDesk@example.com in this case), and all INVITES sent to the group will have a Request-URI of the shared AOR. Any other requests would not apply to this feature and would be handled using normal SIP mechanisms.
Note that the first 12 examples assume the Appearance Agent is aware of dialog state events. The example in Section 11.13 shows the case where this is not the case, and, as a result, the Appearance Agent initiates a subscription to users of the shared AOR. Any of the other call flow examples could have shown this mode of operation as it is equally valid.
Contents
- 11.1. Registration and Subscription
- 11.2. Appearance Selection for Incoming Call
- 11.3. Outgoing Call without Appearance Seizure
- 11.4. Outgoing Call with Appearance Seizure
- 11.5. Outgoing Call without Using an Appearance Number
- 11.6. Appearance Release
- 11.7. Appearance Pickup
- 11.8. Call between UAs within the Group
- 11.9. Consultation Hold with Appearances
- 11.10. Joining or Bridging an Appearance
- 11.11. Loss of Appearance during Allocation
- 11.12. Appearance Seizure Contention Race Condition
- 11.13. Appearance Agent Subscription to UAs
- 11.14. Appearance Pickup Race Condition Failure
- 11.15. Appearance Seizure Incoming/Outgoing Contention Race Condition
This section contains detailed SIP message flow examples demonstrating various shared appearance scenarios. Each subsection includes call flow diagrams and complete SIP message examples showing the interactions between User Agents, the Appearance Agent, Proxy, and Registrar.
For the complete message details, please refer to the official RFC 7463 specification at RFC Editor.