call_center 1.0.1 → 1.0.3

data/Gemfile.lock

@@ -1,71 +0,0 @@
-GEM
-  remote: http://rubygems.org/
-  specs:
-    actionpack (2.3.17)
-      activesupport (= 2.3.17)
-      rack (~> 1.1.0)
-    activesupport (2.3.17)
-    ansi (1.4.3)
-    bourne (1.2.0)
-      mocha (= 0.12.3)
-    builder (3.1.3)
-    execjs (1.2.0)
-      multi_json (~> 1.0)
-    git (1.2.5)
-    guard (0.7.0)
-      thor (~> 0.14.6)
-    guard-shell (0.1.1)
-      guard (>= 0.2.0)
-    guard-test (0.3.0)
-      guard (>= 0.2.2)
-      test-unit (~> 2.2)
-    hashie (1.2.0)
-    hsume2-state_machine (1.0.5)
-    jeweler (1.6.4)
-      bundler (~> 1.0)
-      git (>= 1.2.5)
-      rake
-    metaclass (0.0.1)
-    minitest (3.3.0)
-    minitest-reporters (0.11.0)
-      ansi
-      builder
-      minitest (>= 2.12, < 4.0)
-      powerbar
-    mocha (0.12.3)
-      metaclass (~> 0.0.1)
-    multi_json (1.0.3)
-    powerbar (1.0.9)
-      ansi (~> 1.4.0)
-      hashie (>= 1.1.0)
-    pre-commit (0.1.13)
-      execjs
-    rack (1.1.6)
-    rake (0.9.2.2)
-    rcov (0.9.9)
-    shoulda (3.0.1)
-      shoulda-context (~> 1.0.0)
-      shoulda-matchers (~> 1.0.0)
-    shoulda-context (1.0.0)
-    shoulda-matchers (1.0.0)
-    test-unit (2.3.0)
-    thor (0.14.6)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  actionpack (~> 2.3.15)
-  bourne (>= 1.2.0)
-  builder
-  guard
-  guard-shell
-  guard-test
-  hsume2-state_machine (~> 1.0.5)
-  jeweler (~> 1.6.4)
-  minitest (~> 3.3.0)
-  minitest-reporters
-  mocha
-  pre-commit
-  rcov
-  shoulda

data/Guardfile

@@ -1,5 +0,0 @@
-guard 'test' do
-  watch(%r{^lib/(.+)\.rb$})     { |m| "test/#{m[1]}_test.rb" }
-  watch(%r{^test/.+_test\.rb$})
-  watch('test/helper.rb')  { "test" }
-end

data/Guardfile.minitest

@@ -1,9 +0,0 @@
-def run_tests
-  system("ruby minitest/run.rb")
-end
-
-guard 'shell' do
-  watch(%r{^lib/(.+)\.rb$})         { run_tests }
-  watch(%r{^minitest/.+_test\.rb$}) { run_tests }
-  watch('minitest/helper.rb')       { run_tests }
-end

data/LICENSE

@@ -1,176 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS

data/README.md

@@ -1,212 +0,0 @@
-Call Center
-===========
-
-Support for defining call center workflows.
-
-[![Build Status](https://secure.travis-ci.org/zendesk/call_center.png)](http://travis-ci.org/zendesk/call_center)
-
-Overview
---------
-Call Center streamlines the process of defining multi-party call workflows in your application. Particularly, with [Twilio](http://www.twilio.com/docs) in mind.
-
-[Twilio](http://www.twilio.com/docs) provides a two-part API for managing phone calls, and is mostly driven by callbacks. Call Center DRYs up the application logic dealing with a callback driven API so you can focus on the business logic of your call center.
-
-Usage
------
-
-```ruby
-class Call
-  include CallCenter
-
-  call_flow :state, :intial => :incoming do
-    actor :customer do |call, event|
-      "/voice/calls/flow?event=#{event}&actor=customer&call_id=#{call.id}"
-    end
-
-    state :incoming do
-      response do |x|
-        x.Gather :numDigits => '1', :action => customer(:wants_voicemail) do
-          x.Say "Hello World"
-          x.Play some_nice_music, :loop => 100
-        end
-        # <?xml version="1.0" encoding="UTF-8" ?>
-        # <Response>
-        #   <Gather numDigits="1" action="/voice/calls/flow?event=wants_voicemail&actor=customer&call_id=5000">
-        #     <Say>Hello World</Say>
-        #     <Play loop="100">http://some.nice.music.com/1.mp3</Play>
-        #   </Gather>
-        # </Response>
-      end
-
-      event :called, :to => :routing, :if => :agents_available?
-      event :called, :to => :voicemail
-      event :wants_voicemail, :to => :voicemail
-      event :customer_hangs_up, :to => :cancelled
-    end
-
-    state :voicemail do
-      response do |x|
-        x.Say "Please leave a message"
-        x.Record(:action => customer(:voicemail_complete))
-        # <?xml version="1.0" encoding="UTF-8" ?>
-        # <Response>
-        #   <Say>Please leave a message</Say>
-        #   <Record action="/voice/calls/flow?event=voicemail_complete&actor=customer&call_id=5000"/>
-        # </Response>
-      end
-
-      event :voicemail_complete, :to => :voicemail_completed
-      event :customer_hangs_up, :to => :cancelled
-    end
-
-    state :routing do
-
-    end
-  end
-end
-```
-
-Benefits of **CallCenter** is that it's backed by [state_machine](https://github.com/pluginaweek/state_machine). Which means you can interact with events the same you do in `state_machine`.
-
-```ruby
-@call.called!
-@call.wants_voicemail!
-@call.routing?
-@call.render # See Rendering
-```
-
-Flow
-----
-
-The general application flow for a **CallFlow** is like this:
-
-1. An incoming call is posted to your application
-   * You create a **Call**
-   * You execute an initial event
-   * You respond by rendering TwiML. Your TwiML contains callbacks to events or redirects
-2. Something happens and Twilio posts an event to your application
-   * You find the **Call**
-   * You store any new information
-   * You execute the posted event
-   * You respond by rendering TwiML. Your TwiML contains callbacks to events or redirects
-3. Repeat 2.
-
-In order to DRY up the callbacks, it is best to have use standardized callback URLs. A handy concept is the `flow_url`, which follows the pattern:
-
-    http://domain.com/calls/flow?call_id=?&event=?
-
-By handling this in your controller, you can immediately retrieve the **Call** from persistence, run an event on the call, and return the rendered TwiML. Here's an example:
-
-```ruby
-def flow
-  render :xml => @call.run(params[:event])
-end
-```
-
-For an in-depth example, take a look at [call_roulette](https://github.com/zendesk/call_roulette).
-
-Rendering
----------
-
-Rendering is your way of interacting with Twilio. Thus, it provides two facilities: access to an XML builder and access to your call.
-
-```ruby
-state :sales do
-  response do |xml_builder, the_call|
-    xml_builder.Say "This is #{the_call.agent.name}!" # Or agent.name, you can access he call implicitly
-  end
-end
-```
-
-Renders with `@call.render` if the current state is :sales:
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<Response>
-  <Say>This is Henry!</Say>
-</Response>
-```
-
-Callbacks
----------
-
-You have control over what you want to happen before/after state transitions:
-
-```ruby
-state :voicemail do
-  before(:always) { # Invokes before any transition }
-  before(:always, :uniq => true) { # Invokes before transitions to a different state }
-
-  after(:always) { # Invokes after any transition }
-  after(:success) { # Invokes after any successful transition }
-  after(:failure) { # Invokes after any failed transition (those not covered in your call flow) }
-
-  after(:always, :uniq => true) { # Invokes after any transition to a different state }
-  after(:success, :uniq => true) { # Successful unique transitions }
-  after(:failure, :uniq => true) { # Failed unique transitions }
-end
-```
-
-For example,
-
-```ruby
-state :voicemail do
-  before(:always) { log_start_event }
-
-  after(:always) { log_end_event }
-  after(:failure) { notify_airbrake }
-
-  after(:success, :uniq => true) { notify_browser }
-  after(:failure, :uniq => true) { notify_cleanup_browser }
-end
-```
-
-Motivation
-----------
-
-### Not DRY
-Twilio requests your application to return [TwiML](http://www.twilio.com/docs/api/twiml/) that describes the call workflow. TwiML contains commands which Twilio then executes. It is essentially an application-to-application API, synonymous to making a REST call.
-
-In the context of "[Skinny Controller, Fat Model](http://weblog.jamisbuck.org/2006/10/18/skinny-controller-fat-model)", outgoing REST calls for the function of business logic are not a view concern but a model concern. Therefore, so is TwiML.
-
-Twilio supports callbacks URLs and redirects to URLs that also render TwiML as a method of modifying live calls. Incoming callbacks are handled by the controller first, but the response is still a model concern.
-
-
-Terminology
------------
-
-* **Call** - An application resource of yours that encapsulates a phone call. Phone calls are then acted on: answered, transferred, declined, etc.
-* **Event** - Is something that happens outside or inside your application in relation to a **Call**. Someone picks up, hangs up, presses a button, etc. But overall, it's anything that can be triggered by Twilio callbacks.
-* **State** - Is the status a **Call** is in which is descriptive of what's happened so far and what are the next things that should happen. (e.g. a call on hold is waiting for the agent to return)
-* **CallFlow** - Is a definition of the process a **Call** goes through. **Events** drive the flow between **States**. (e.g. a simple workflow is when noone answers the call, send the call to voicemail)
-* **Render** - Is the ability of the **CallFlow** to return TwiML to bring the call into the **State** or modify the live call through a **Redirect**.
-* **Redirect** - Is a way of modifying a live call outside of a TwiML response (e.g. background jobs)
-
-Tools
------
-
-### Drawing ###
-
-Should you be interested in what your call center workflow looks like, you can draw.
-
-```ruby
-Call.state_machines[:status].draw(:font => 'Helvetica Neue')
-# OR
-@call.draw_call_flow(:font => 'Helvetica Neue')
-```
-
-Future
-------
-
-* Integrate making new calls into the **CallFlow** DSL
-
-## Copyright and license
-
-Copyright 2013 Zendesk
-
-Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.