User Tools

Site Tools


restrictions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

restrictions [2019-07-23 20:28] (current)
Line 1: Line 1:
 +<WRAP center round box centeralign 70%>
 +<fs 200%>​**Avaya Breeze(tm) Learning**</​fs>​\\
 +<fs 160%>​**Lab Usage Quirks**</​fs>​\\
 +</​WRAP>​
 +
 +===== Differences from a Standard Collaboratory =====
 +
 +===== Guidelines =====
 +  - This lab is shared by many users, and solely for learning Avaya Breeze programming techniques.
 +    * **There is no privacy:​** ​ //You can see what others are doing, and they can see what you are doing.//
 +    * We cannot guarantee that this lab will correctly function (or function at all) all of the time, so giving demonstrations from this lab is precarious at best.
 +    * If you wish to have your own, private lab where you can do real development,​ [[https://​news.avaya.com/​avaya-collaboratory|sign up for your own Avaya Collaboratory today.]]
 +  - The System Manager and Breeze nodes in this lab are shared by all participants:​
 +    * For workflows, create a folder that matches your account name (e.g. student45), and save all your workflow drafts there.
 +    * Participants will be able to uninstall and delete each others'​ snap-ins. ​ Please don't do that to others.
 +    * Since others can do this, make sure to externally save any Workflow you can't easily reproduce. Java snap-ins are built externally on your own PC and uploaded to System Manager, so you will not need to explicitly save these.
 +    * Work only with your assigned service profile and the snap-ins you create.
 +  - There are many scheduled activities in this lab
 +    * Immediately before each of these activities, **ALL SNAP-INS MAY BE REMOVED** from the lab.
 +    * During the activities, accounts **MAY BE LOCKED OUT** without prior notice.
 +  - We will be monitoring calling and other activity in this lab from time to time and reserve the right to take corrective action (e.g. locking out an account) should its use pose a threat to the others'​ use of the lab.
 +
 +
 +==== Features/​APIs Support ====
 +^ Feature ^ Supported ^
 +| Scopia Connector ​                          | No |
 +| Avaya Mobile Video                         | No |
 +| WebRTC Audio                               | No |
 +| Clickatell SMS                             | No |
 +
 +===== Differences from a Breeze on Your Own Network =====
 +  * The From: user in the send email API should be left null.
 +    * The connector will then fill in the default user for this lab.
 +    * Only email from this default user will be accepted by our email server.
 +    * You set the reply-to field to any legal value
 +    * When using EDPTester, you must set the From: user to lab13@collaboratory.avaya.com
 +  * The Breeze IP addresses you were given are external, Internet facing addresses.
 +    * They allow only HTTPS (i.e. not HTTP), even though the servers themselves support both HTTP and HTTPS.
 +  * The lab media server does not trust https:// URLs that include a Breeze server'​s FQDN/IP address
 +    * Intead, always give an http:// URL to the media server if you are wanting to play a file served up by your application from a Breeze server.
 +    * Because of the immediately previous restriction,​ always use the internal ip address of these Breeze server
 +    * This is not a problem in a standard Collaboratory.
  
restrictions.txt ยท Last modified: 2019-07-23 20:28 (external edit)