WebAPI/WebTelephony: Difference between revisions

WebAPI/WebTelephony (view source)

425 bytes removed , 2 November 2011

no edit summary

Confirmed users

716

edits

@@ Line 1: / Line 1: @@
-== Goals ==
-Our first goal is to create a low-level API for "plain" telephony. I.e. not SIP or other VoIP calls. This is because plain telephony is still the main use case for most users. While we long term will want to have APIs for things like SIP, it's likely that those APIs will look substantially different since the capabilities there are much more advanced.
-It's possible that we will want to have a higher level API which abstracts over POTS and VoIP, but that's something we should focus on once we have the lower level pieces in place. See also the discussion [[WebAPI#Low_Level_vs._High_Level|here]].
-== Status ==
-There are some rudamentory patches in {{bug|674726}}, but they don't implement much of what we need yet.
 == Proposed API ==
@@ Line 17: / Line 7: @@
      attribute boolean speakerOn;
      attribute double speakerVolume;
+    attribute boolean doNotDisturb;    // Automatically drops calls. Not sure if needed. Only seems needed
+                                       // if supported as a network feature.
      attribute any active; // Either a call or a group
@@ Line 45: / Line 37: @@
      void answer(); // Should this make the call the active one?
-     void hangUp();
+     void disconnect();
-   }
+    // void hold(); Not sure if needed for now. We might need to remake group APi to make it async
+    // void resume();
+  }
    [Constructor()]