new content for 0.7.0 release (#25)

* new content for 0.7.0 release

* shorter banner

* another banner change

data/docs.yml

@@ -4,7 +4,7 @@ root:
 navi:
   -
     path: webhooks
-    title: Using webhooks
+    title: Webhooks
     pages:
       -
         path: overview
@@ -109,6 +109,9 @@ navi:
     path: release-notes
     title: Release Notes
     pages:
+      -
+        path: v0.7.0
+        title: v0.7.0
       -
         path: v0.6.6
         title: v0.6.6

data/site.yml

@@ -1,7 +1,7 @@
 banner:
   active: true
-  text: View our presentation at ClueCon 2021! - "The case for an open-source CPaaS"
-  link: https://bit.ly/3CrNAIc
+  text: Click here to install from AWS Marketplace
+  link: https://aws.amazon.com/marketplace/pp/prodview-55wp45fowbovo
 latest:
   -
     active: false
@@ -16,7 +16,7 @@ latest:
     headline: jambonz will be at Enterprise Connect 2021
     subtext: Ping us at <a href="mailto:sales@jambonz.org" target="_blank">sales@jambonz.org</a> to set up a meeting!
   -
-    active: true
+    active: false
     label: aws
     headline: Are you looking to self-host your CPaaS? 
     subtext: Deploy jambonz in seconds on AWS using <a href="https://aws.amazon.com/marketplace/pp/prodview-55wp45fowbovo" target="_blank">our CloudFormation script!</a>
@@ -32,7 +32,7 @@ navi:
       label: Why jambonz
       link: /why/
     -
-      label: For Developers
+      label: Docs
       link: /docs/
     -
       label: Pricing

markdown/docs/release-notes/v0.7.0.md

@@ -0,0 +1,32 @@
+# Release v0.7.0
+> Release Date: Dec 12, 2021
+
+#### New Features
+- Add support for Microsoft as a speech synthesis and recognition vendor.
+- Add `sip:refer` verb to support initiating a blind call transfer.
+- Reduce the number of media anchors on bridged calls by removing Freeswitch from media path when possible.
+- Add support for Subspace sip teleports.
+- The `say` verb now supports loop=forever.
+- REST outdial handles 302 Redirect response and supports `overrideTo` property.
+- Add support for muting and unmuting non-moderators in a conference.
+- Add support for conference members joining a conference in an initially muted state.
+- SBC SIP and RTP servers now deployed in autoscale groups for improved and easier scalability on AWS.
+- Update to aes-256-cbc algorigthm for encrypting some data.
+- Allow application to specify a SIP trunk for outdial when multiple carriers are configured.
+- Improved UI for adding Carriers.
+- Add support for SIP proxies that add X-Forwarded-For header
+
+#### Bug fixes
+- `enqueue` task was only invoking `waitUrl` a single time.
+- `gather` task throws an error about missing speech credentials even when only dtmf input is requested.
+- `dial` task was not clearing max call time when dial completes.
+- remove sensitive info from logs.
+- various bugfixes in `gather` command.
+- fix error responses for sms.
+- fix Stripe integration bug.
+- fix bug in some re-Invite scenarios.
+
+#### Availability
+- Available now on <a href="https://aws.amazon.com/marketplace/pp/prodview-55wp45fowbovo" target="_blank" >AWS Marketplace</a>
+
+**Questions?** Contact us at <a href="mailto:support@jambonz.org">support@jambonz.org</a>

markdown/docs/webhooks/overview.md

@@ -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?
 

markdown/docs/webhooks/say.md

@@ -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 |

markdown/docs/webhooks/sip-refer.md

@@ -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.