mirror of
https://github.com/jambonz/next-static-site.git
synced 2026-10-30 23:34:38 +00:00
new content for 0.7.0 release (#25)
* new content for 0.7.0 release * shorter banner * another banner change
This commit is contained in:
1 parent
82b20253b2
commit
9b3305ef80
6 files changed
+46
-9
No files matched your search
@@ -2,9 +2,11 @@
|
||||
|
||||
jambonz uses JSON payloads that are exchanged in HTTP messages to control calls.
|
||||
|
||||
When an incoming call for your account is received, jambonz makes an HTTP request to a URL that you have configured and your response will contain a JSON body that indicates how you want the call handled.
|
||||
When an incoming call for your account is received, jambonz makes an HTTP request to a URL that you have configured and your webapp will then return a response containing a JSON body that indicates how you want the call handled.
|
||||
|
||||
When you want to launch an outbound call it works similarly: you will make an HTTP request using the [REST API](/docs/api/rest) and in it you will specify a URL or application identifier that will be invoked once the call is answered. Once again, your response to that HTTP request will contain a JSON body that indicates how you want the call handled.
|
||||
> You can develop your webapp using whatever language or framework you like, but the quickest way to scaffold up a webapp is by using our [Node.js framework](/docs/client-sdks/create-jambonz-app/.)
|
||||
|
||||
If you want to generate an outbound call it works similarly: you will make an HTTP request using the [REST API](/docs/api/rest) and in it you will specify a URL or application identifier that will be invoked once the call is answered. Once again, your response to that HTTP request will contain a JSON body that indicates how you want the call handled.
|
||||
|
||||
Simple enough, right?
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ You can use the following options in the `say` action:
|
||||
| option | description | required |
|
||||
| ------------- |-------------| -----|
|
||||
| text | text to speak; may contain SSML tags | yes |
|
||||
| synthesizer.vendor | speech vendor to use: <br>- 'google', <br>- 'aws', <br>- 'microsoft' (coming in v0.6.7)| no |
|
||||
| synthesizer.vendor | speech vendor to use: <br>- 'google', <br>- 'aws', <br>- 'microsoft'| no |
|
||||
| synthesizer.language | language code to use. | no |
|
||||
| synthesizer.gender | (Google only) MALE, FEMALE, or NEUTRAL. | no |
|
||||
| synthesizer.voice | voice to use. Note that the voice list differs whether you are using aws or Google. Defaults to application setting, if provided. | no |
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# sip:refer
|
||||
> Coming in v0.6.7
|
||||
> Added in v0.7.0
|
||||
|
||||
The sip:refer action is used to blind transfer a call. It will send a sip REFER to the far end carrier or sip phone, which must support the REFER in order for the transfer to work. After the sip:refer completes successfully, the call leg will have left the jambonz platform.
|
||||
|
||||
|
||||
Reference in new issue
Block a user