canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
| Line 48: | Line 48: | ||
'''The capabilities, addresses and settingURL are not implemented yes'''. | '''The capabilities, addresses and settingURL are not implemented yes'''. | ||
The (optional) capabilities array here is a set of capabilities supported by the SPA for the connected user service. | The (optional) capabilities array here is a set of capabilities supported by the SPA for the connected user service. See the list below for the options. | ||
The settingURL is the address of a webpage that the user can load by clicking in the UI. | The settingURL is the address of a webpage that the user can load by clicking in the UI. | ||
| Line 62: | Line 62: | ||
Note: Needing to re-authentify the user to connect is an error. Having to login on the service provider's website shouldn't be required each time the browser is restarted. | Note: Needing to re-authentify the user to connect is an error. Having to login on the service provider's website shouldn't be required each time the browser is restarted. | ||
=== Capabilities === | |||
These are the possible capabilities an SPA can advertise: | |||
* `call`: The SPA can make calls | |||
* `hold`: The SPA supports hold and resume for calls | |||
* `move`: The SPA supports call move to other devices | |||
* `nodatachannel`: The SPA does not support the data channel and routes text messages and file transfers via the server. | |||
== Call Handling == | == Call Handling == | ||