![]() The caller is recalled after the callee has The caller is recalled after the callee has completed aĬompletion of Calls on Not Logged-in (CCNL): The callee is not The caller is recalled after the callee is no longer busy.Ĭompletion of Calls on No Reply (CCNR): The callee does not answer This document defines the following CC features:Ĭompletion of Calls to Busy Subscriber (CCBS): The callee is busy. Order in which they have requested the CC feature. They will be recalled in a predefined order, which is usually the Several callers have requested the CC feature on the same callee, Recall, then a CC call to the callee will automatically start. If the callee does not initiate a new call within this time frame, ![]() The callee will be given a certain time frame for initiating a call. When theĬaller requests the use of the CC feature, the callee will be The Completion of Calls (CC) feature allows the caller of a failedĬall to have the call completed without having to make a new callĪttempt while guessing when the callee becomes available. The 'purpose' Parameter Value 'call-completion'. MIME Registration for application/call-completion. Subscriber Processing of NOTIFY Requests. Notifier Processing of SUBSCRIBE Requests. RFC 6910 Completion of Calls April 2013 9.7. Subscriber Generation of SUBSCRIBE Requests. The Trust Legal Provisions and are provided without warranty asġ. Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained atĬopyright (c) 2013 IETF Trust and the persons identified as the Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. The architecture is designed to interoperate well with existingĬompletion of calls solutions in other networks. Is ready to be serviced, re-attempt of the original, failed call is This document introduces an architecture for implementing theseįeatures in the Session Initiation Protocol where "completion ofĬalls" implementations associated with the caller's and callee'sĮndpoints cooperate to place the caller's request for completion ofĬalls into a queue at the callee's endpoint when a caller's request That is described as 'Automatic Redial' in "Session Initiationįor the realization of a more comprehensive solution with queuing, The "completion of calls" feature defined in this specificationĪllows the caller of a failed call to be notified when the calleeįor the realization of a basic solution without queuing, thisĭocument references the usage of the dialog event package ( RFC 4235) Request for Comments: 6910 Ariadne Internet Services, Inc.Ĭompletion of Calls for the Session Initiation Protocol (SIP) Internet Engineering Task Force (IETF) D. SSLException didn’t help me much.Īlso I logged these questions as a support email on the 24th June and haven't heard back yet.RFC 6910: Completion of Calls for the Session Initiation Protocol (SIP) I used Runscope as the middle man to help figure this out (FYI, it appears that Runscope have updated their screens so it would be helpful if you updated your help re: setting up runscope: )Īre the HTTPS requirements listed for Fitbit subscription end point call purely for the POST call… are the requirements different for the verification call? (since it seems to be able to do the GET verify call ok, but not the POST activity call – note, I’m not 100% sure about if the GET call succeeded or not - I was making lots of changes to try and figure out the issue).Īre there any plans to support TLS + SNI (any reason why it isn't currently supported)?Īs some feedback, it might be useful to have something in the documentation that talks about common errors in the subscription activity screen and want they might be caused by e.g. I'm almost certain it's because Azure (where my app is hosted) quite often uses TLS + SNI which isn't supported by Fitbit (for others interested in HTTPS requirements check out "Using HTTPS" under ). I see "SSLException" logged on the Fitbit subscriberstats page for the app when Fitbit calls my subscription end point.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |