Talk:WebAPI/WebTelephony: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 26: | Line 26: | ||
attribute Function ondisconnect; | attribute Function ondisconnect; | ||
attribute Function onbusy; | attribute Function onbusy; | ||
attribute Function onreadystatechange; | |||
void answer(); | void answer(); | ||
void hangUp(); | void hangUp(); |
Revision as of 12:17, 7 September 2011
Counter proposal:
navigator.telephony would return an object with the following interface
interface Telephony : EventTarget { TelephonySession newSession(DOMString number); // Multiple number call?? readonly attribute TelephonySession liveSession; attribute Function onincoming; } interface TelephonySession : EventTarget { readonly attribute DOMString originNumber; readonly attribute DOMString number; // Do the call void call(); attribute boolean muted; attribute boolean speakerOn; void startTone(DOMString tone); void stopTone(); void sendTones(DOMString tones, [optional] unsigned long toneDuration, [optional] unsigned long intervalDuration); readonly attribute DOMString readyState; // "calling", "incomming", "connected", "closed", "busy" // Can we get info on when a call goes from "trying to place call" to "calling"? attribute Function onconnect; attribute Function ondisconnect; attribute Function onbusy; attribute Function onreadystatechange; void answer(); void hangUp(); } interface IncomingCallEvent : Event { readonly attribute TelephonySession session; }