1 / 18

DSPs and HMP in Voice over IP Application Design

DSPs and HMP in Voice over IP Application Design. Mike Kane Senior Product Manager Brooktrout Technology. DSPs and HMP in VoIP App Design. Changing Requirements DSPs & HMP Issues Use Case Examples VoIP Solution Requirements Conclusions. Four migrations to manage

joylyn
Télécharger la présentation

DSPs and HMP in Voice over IP Application Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DSPs and HMP in Voice over IP Application Design Mike Kane Senior Product Manager Brooktrout Technology

  2. DSPs and HMP in VoIP App Design • Changing Requirements • DSPs & HMP Issues • Use Case Examples • VoIP Solution Requirements • Conclusions

  3. Four migrations to manage Migration to IP networks Adoption of Industry-standard APIs Migration from Hardware to Host-based Media Processing Adoption of nextgen architectures The Changing Media Processing Environment PSTN IP Host Media Processing DSP-Based Hardware Today

  4. IP networks Less ”virtual” resources are required per call = less cost Multimedia & greater bandwidth = new solutions Adoption of Industry-standard APIs More tools = faster, cheaper development Easier application level integration = incremental development Migration from Hardware to HMP Software = easier installation/management No DSP hardware = lower cost Adoption of NextGen architectures Modular systems = install only what you need Decentralized decisions = flexibility, adaptability, extensibility The Changing Media Processing Environment -The Perceived Promise

  5. Migration to IP:TDM Voice Processing Requirements  • Telephony Interface • Call Quality • Media Processing • Call Processing • Call Management Voice Processing System PSTN  • Echo Cancellation • Gain Control • DTMF handling • Speech Buffering • Transferring • Tromboning Analog/Digital TDM Residential Phone PBX  • Prompt & Collect • Play & Record • Conferencing • Speech Management All TDM app functions & control happen at the voice processing system Digital Set

  6. IP Migration to IP:VoIP Requirements  IVR System • Prompt & Collect • Play & Record • Conferencing • Speech Management PSTN IP Phone  IP PBX • Telephony • Call Quality • Media Proc. • Call Processing • Call Mgmt IP app functions & control happen at different points in the IP architecture  Access Gateway • Echo Cancellation • Gain Control • DTMF handling • Speech Buffering • Transferring/Tromboning

  7. Migration to IP:VoIP Requirements Features to Ensure Voice Processing working with Access Gateway or IP PBX • Echo cancellation to support latency between GW and HMP Host • Gain Control to support voice quality • Interoperability with Access Gateway • DTMF transport support across VoIP network between GW and Host (RFC 2833) • Signaling support for circuit switching inband information • SIP Call Control • Codec support • Gateway Support for desired connection to Central Office or PBX • Echo Cancellation • Analog FX0

  8. AdoptionStandards-Based Development  • Prompt & Collect • Play & Record • Conferencing • Speech Management Application • Emerging standards for Application APIs including SALT and VXML • Enabling API integration to Application API Application API Abstraction Layer Enabling API  • Echo Cancellation • Gain Control • DTMF handling • Speech Buffering • Transferring • Tromboning Enabling API Media Processing • Speed development for speech, IVR, multimedia • Common application across TDM and IP • Platform portability Network Interface Media Processing  • Telephony Interface • Call Quality • Media Processing • Call Processing • Call Management Network Interface

  9. DSPs & HMP Issues #1: Programmability • Where is programmability happening? • Rarely at DSP but…APIs don’t always expose DSP functionality • Direct APIs expose DSP or HMP functionality but…don’t integrate IP PBX or Gateway control • Standards-based APIs have the potential to integrate and provide easier development but… don’t go deep enough for call control

  10. Predictable performance per board Near linear scalability using multi-boards Interoperability over H.100 IP Capable Standards Driven Design/Functional maturity Regular performance improvements Regular cost improvements Migration from DSP to HMP: DSP Value Comparison

  11. 60 30 20 50 40 10 DSPs & HMP Issues #2: Scaling/Performance* # of channels # of channels Dual Span DSP Board Dual CPU HBM Single Span DSP Board Single CPU HBM • Processor intensive functions have dramatic impact on performance • Conferencing (-30%) • Fax (-50%) • Transcoding (-80%) Play & Collect (Messag- ing) Play & Record (IVR) FAX Confer- encing Trans- coding Prompt & Play (Announce- ments) * # of channels is illustrative. Actual scaling numbers will vary by processor and by product.

  12. Hardware Independence Ride Moore’s Law Curve Low Total Cost of Operations Software model Remote support/upgrades Low Logistics Low inventory Low/No shipping Standards based Development Interoperability Rapid performance improvements Leap in cost improvements Migration from DSP to HMP: HMP Value Comparison

  13. Distributed Business Case – Vroom Auto Parts Vroom sells 4 & 8 port auto parts inventory and ordering systems to 100’s of dealers across the US. Due to competition, Mr. Vroom needs to find ways to cut costs. Today he sells 4 and 8 port analog board systems. Assumptions DSPs & HMP Issues #3: Total Cost of Operation (TCO) • Purchase includes approximate list price of voice product plus PC & OS. • Board Solution assumes site visit/HMP remote install • Upgrade is from 4 to 8 ports. Board requires site visit, HMP is 4 port license with phone support install.

  14. Use Case A: Speech-Enabled Auto Attendant TDM/DSP vs IP/HMP • Incoming call for speech treatment • App turns on • EC & VAD @ DSP • DSP/Driver Buffers Speech • API takes buffer • performs app TDM/DSP Configuration PSTN PBX • Incoming call to PBX • PBX Call Mgr sees call for speech • PBX Call Mgr turns on EC, sends call to HMP • HMP Buffers Speech • API takes buffer performs app ASR System IP/HMP Configuration IP PSTN IP PBX ASR System

  15. Use Case B: Conferencing ServiceIP/DSP vs IP/HMP • Incoming call come to GW • GW Call Mgr passes calls to Conf sys. • DSP mix calls across codecs • DSPs are added as app scales IP/DSP Configuration IP PSTN Access Gateway • Incoming call come to GW • GW Call Mgr passes calls to Conf sys. • HMP mix calls across codecs • Host takes 30% - 80% capacity hit w/ confer. & codecs • Add more hosts to scale Conferencing System IP/HMP Configuration IP PSTN Access Gateway ASR System Conferencing System

  16. Use Case B: Distributed IVRIP/DSP vs IP/HMP • Incoming call come to GW • GW Call Mgr passes calls to IVR • DSP receives call over IP • DSPs passes call to app IP/DSP Configuration Access Gateway IP IVR System PSTN IP Access Gateway • Incoming call come to GW • GW Call Mgr passes calls to IVR • App takes call IVR System IP/HMP Configuration Access Gateway IVR System IP PSTN IP IVR System Access Gateway

  17. Issues in VoIP Solution Selection

  18. DSPs and HMP in VoIP App DesignConclusions • Many dimensions to comparison • Both DSPs and HMP have place • Choice is as much about architecture as technology • Look for a VoIP solution that is flexible, that allows both DSP and HMP options

More Related