1 / 8

IETF 69, Chicago BLISS WG draft-poetzl-bliss-call-completion-00

IETF 69, Chicago BLISS WG draft-poetzl-bliss-call-completion-00 Denis Alexeitsev d.alexeitsev@t-com.net Martin Huelsemann martin.huelsemann@t-com.net.

jeanette-stewart
Download Presentation

IETF 69, Chicago BLISS WG draft-poetzl-bliss-call-completion-00

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF 69, Chicago BLISS WG draft-poetzl-bliss-call-completion-00 Denis Alexeitsev d.alexeitsev@t-com.net Martin Huelsemann martin.huelsemann@t-com.net Call-Completion

  2. work has been shifted to BLISS- was draft-poetzl-sipping-call-completion-02- was revised to draft-poetzl-bliss-call-completion-00- did huge editorial changes, tried to compare different solutions, hasn’t yet looked at the interop problems among solutions Call-Completion

  3. queuing method has been changed- event header parameters are no longer used for queue manipulation actions (add, suspend and resume) - queuing is done implicitly by creating a queue-entry when a call ends in busy- suspension and resumption is done by unsubscribing and subscribing again to the queue-entry Call-Completion

  4. call-completion prioritization has been changed- new p-header is no longer used for prioritization> issue: can prioritization be done implicitly by comparing caller identity with queue-entry on top? Call-Completion

  5. resulting basic flow Call-Completion

  6. changed queue model has to be described - queue-entry is created when a call results in busy or no-reply; caller can subscribe to the queue-entry - queue-entry is deleted when it matures after timer expiry or when a call-completion attempt is started- caller is informed when the state of his queue-entry changes from ‘queued’ to ‘ready-for-call-completion’; caller can start call-completion attempt> issue: what happens to the state of the queue entry if no call- completion attempt is started?> issue: what happens if call-completion attempt results in busy again: shall queue-entry remain? shall queue-entry be deleted and new entry be created? Call-Completion

  7. other open issues- procedures for general error, e.g. queue-entry doesn’t exist at the time of the subscription; proposed: usage of 403 Forbidden response- procedures for temporary error, e.g. several devices of a user, using the same identity, wish to subscribe to the same queue-entry; proposed: usage of 480 Temporarily Unavailable response Call-Completion

  8. next steps- discussion of open issues- revision including alignment with problem statement draft Call-Completion

More Related