Difference between revisions of "Hosted Services Platform"

From Freeside
Jump to: navigation, search
(Asterisk Integration)
(Asterisk Integration)
Line 5: Line 5:
 
* Using [http://www.voicerd.com/ VoiceRD]
 
* Using [http://www.voicerd.com/ VoiceRD]
 
** our contact: Ryan Trantvein rtrauntvein@novacoast.com
 
** our contact: Ryan Trantvein rtrauntvein@novacoast.com
 +
** add'l (more knowledgable wrt voicerd internals, but less accessible) contact: Eron Howard ehoward@novacoast.com
 
* Real-time CDR integration
 
* Real-time CDR integration
 
** MySQL (InnoDB or MyISAM?)
 
** MySQL (InnoDB or MyISAM?)
** format forthcoming
+
*** According to [[http://www.voicerd.org/index.php/Open_Source_Installation_Guide#Setting_up_the_mysql_for_CDR VoiceRD installation guide]], uses default MyISAM tables.
 +
*** Note with VoiceRD that we want InnoDB for our install
 +
** format: standard asterisk CDRs (excellent!)
 
* Integrate prepaid hook (Perl or XML-RPC) for "minutes left on prepaid card"
 
* Integrate prepaid hook (Perl or XML-RPC) for "minutes left on prepaid card"
** awaiting documentation
+
** will need to be written on VoiceRD's side
 +
** we will provide XML-RPC & Perl API
 +
** Pravin will go over with VoiceRD exactly how the IVR "flow" should function
 
* Provisioning/deprovisioning integration (ARA, LDAP, something else?)
 
* Provisioning/deprovisioning integration (ARA, LDAP, something else?)
 
** modify LDAP database
 
** modify LDAP database

Revision as of 15:37, 5 November 2007

Phase one: hosted VoIP

Asterisk Integration

  • Using VoiceRD
    • our contact: Ryan Trantvein rtrauntvein@novacoast.com
    • add'l (more knowledgable wrt voicerd internals, but less accessible) contact: Eron Howard ehoward@novacoast.com
  • Real-time CDR integration
    • MySQL (InnoDB or MyISAM?)
    • format: standard asterisk CDRs (excellent!)
  • Integrate prepaid hook (Perl or XML-RPC) for "minutes left on prepaid card"
    • will need to be written on VoiceRD's side
    • we will provide XML-RPC & Perl API
    • Pravin will go over with VoiceRD exactly how the IVR "flow" should function
  • Provisioning/deprovisioning integration (ARA, LDAP, something else?)
    • modify LDAP database
    • LDAP info forthcoming
  • Feature control integration
    • Call forwarding w/ or w/o simul-ring
    • Voicemail
    • same as above, LDAP database, info forthcoming

End-customer frontend

Introduction

  • Based on existing Freeside self-service, with a simplified, clean VoIP-only interface and expanded VoIP functionality.
  • Probably PHP with XML-RPC access to Freeside functionality.

Features to add

(could use some expansion and categorization, certainly not yet complete):

  • View recent calls and call history
  • View minutes remaining
  • Voicemail view/listen/delete/etc.
  • Call forwarding (+simul-ring) configuration
  • Order new lines and cancel existing ones.
  • Edit 911 address associated with each line

Existing features to be used in new interface

  • View past and currently open invoices
  • Make payments, change payment information
  • Order new packages and cancel existing ones

Reseller back-end

Introduction

  • Based on existing Freeside backoffice interface configured to disable unnecessary features and present a simplified, clean VoIP-only interface and expanded VoIP functionality.
  • Using existing Freeside backoffice Perl/HTML::Mason

Features to add

  • Same VoIP feature controls as end-user interface.
  • Add configuration options and ACLs to disable/hide unnecessary any features to simplify the interface.
  • Agent-virtualize any remaining configuration or tables necessary for fully-virtualized VoIP (CDRs, others?)