Docs

Welcome to diago documentation!.

What is Diago?

If you are familiar with terms Calling, Bridging, Conferencing, IVR, Recording, Transcribing, Voicemail … that is all about.

Developing this kind of services can be challenging when it needs more behavior: monitoring, media control, integrations, databases etc…

Diago with GO offers faster way of developing and testing communication services, but keeping care on providing low latency.

More on Why Diago

Core (Roadmap):

  • Full dialog control and High Level API
  • alaw,ulaw codecs (opus as third is planned as well)
  • Audio package for streaming: WAV reader/writer, PCM transcoding to alaw/ulaw
  • Playbacks as buffers,files(wav),url
  • Playback URL streaming
  • Playback with control mute/unmute
  • Audio Reader/Writer stream exposed for manual processing like sending to third party
  • DTMF with RTP
  • Handling Reinvites with media updates
  • Bridging as proxy media for 2 parties B2BUA
  • Handling transfers (Refers)
  • Handle Anonymous Trust Domain PAI handling (rfc3325)
  • Conferencing audio
  • DTMF with SIP INFO (Needed more in case webrtc)
  • Writing Unit Test on Server with SIP and Media Recorder
  • RTP symetric
  • SRTP for more critical services
  • Simple Wav recording
  • Webrtc as media stack
  • And plenty more …

If you want support/sponzor current development roadmap or you want to prioritize different contact me on mail

Diago extra modules

Some of modules are not yet considered to be part of lib and they are developed/consulted for private projects. To mention few:

  • Recording
  • Webrtc(pion) stack over diago’s media stack
  • Complex modules etc…

NEXT: -> Guides