Main • Dumbchan

A Truly "Dumb" Channel

First, there is nothing to configure with the dumbchan module. It is only useful for programmers developing applications with YATE. If the description below doesn't make sense to you, you don't need it so don't worry about it.

For external modules/scripts, the dumb channel module provides Data Endpoints to and from nowhere.

This is best explained with an example:

Assume that we have an IVR script that connects to YATE via extmodule. This script does some routing, plays some audio to the caller, and responds to dtmfs. Instead of actually writing an audio player, the script-writer wanted to make use of the existing wavefile module in order to play the audio.

Here is the logic for the script:

  • Tell YATE that this script is interested in call.route messages
  • Wait for call.route messages to come in from YATE
  • When a call comes in (let's say on Sip Channel sip/1), I get a call.route message. I respond to the message telling the caller that they should connect their Data Endpoints to a dumb/ channel's endpoints.
  • The caller interprets the response as a confirmation that they should proceed with the call. Internally, the Sip Channel sends a call.execute request to YATE requesting to be connected to a dumb/ channel.
  • The dumb channel basically creates a new identifier for itself, let's say dumb/1, that YATE can use for this call
  • After processing the call.execute, sip/1's Data Source is connected to dumb/1's Data Consumer and sip/1's Data Consumer is connected to dumb/1's Data Source. Since a dumb channel's Data Source comes from nowhere, sip/1's Data Consumer is effectively consuming nothing - For audio channels (which most channels will be), that means silence. Also, since dumb channel's Data Consumer goes to nowhere, any audio that sip/1 sends goes unheard.
  • When the IVR script wants to play an audio file, it sends a chan.attach message to YATE requesting that the wavefile module be attached to dumb/1's Data Source so that it no longer comes from nowhere. Any audio that the wavefile module plays will be heard by whoever is listening on sip/1's Data Consumer end (usually a person).

A script author could make use of similar principles to record audio from callers. They would just instruct YATE to chan.attach a wavefile recorder to a dumb channel's Data Consumer.

July 2014:
Yate 5.4 and YateBTS 4 launched. Added JSON and DNS support in Javascript, Handover support in YateBTS.

March 2014:
YateBTS 2.0 launched. Added authentication and WebGUI. Added USSD support in commercial version.

March 2014:
Yate 5.2 launched. Better JavaScript support and a fixed memory leak.

Jan 2014:
YateBTS 1.0 launched. The first GSM Basestation which works with an IMS/VoLTE core network.

Jan 2014:
Yate 5.1 launched. Better JavaScript support and added libygsm. Elisa chatbot added in RManager

Oct 2013:
OpenHSS is the Yate based HLR/HSS solution for MVNO and LTE carriers.

Oct 2013:
Yate 5 released. Added IPv6 support in SIP for LTE. Improved JavaScript support. Download NOW

Jan 2013:
Yate 4.3 released: Added XML support in Javascript. SCCP - GTT routing between different networks. Stability improvements.
Download NOW

Aug 2012:
Yate 4.2 released: SIP flood protection. Better Jabber/Google Voice support. Usable Javascript. Fixed SIGTRAN links fluctuations.
Download NOW

Apr 2012:
YateClient was accepted in the Mac Store.

Yate 4.1 released: better Gvoice support, iSAC codec, support for new Wanpipe drivers. Fixes T.38 and Mac client issues.

Mar 2012:
SS7Cloud is launched today, 1st March, 2012, by NullTeam, Yate creators. Having all you need to be a US CLEC, it brings SS7 services in a cloud.

Feb 2012:
Yate 4.0 released.
SCCP, TCAP, MAP and CAMEL, TCP and TLS in SIP, Javascript fast prototyping of telephony applications and brand new face for YateClient.

Nov 2011:
Here is a video that, quote "demonstrates the truly awesome power of the YATE engine, as it easily handles 3 simultaneous calls to an audio player application including dtmf (button press) handling "(from PaintedRockComm).

Nov 2011:
Yate will attend ORR - OPENRHEINRUHR (November 12 - 13).

04 May 2011:
sipgate chooses open source project Yate for core infrastructure.

12 Apr 2011:
Yate 3.3.2 released.
Fix for Jingle calls to Google Voice dropping after 5 minutes.
4 Apr 2011:
Yate 3.3 released.
Support for GMail chat conference, fixes for internal microphone in MacOS. Minor fixes in SS7 M2PA and ANSI. Fixes in H.323, SIP and RTP.

9 Mar 2011:
Yate 3.2 released.
Bug fixes in SIGTRAN/MGCP/SS7 and added support for CNAM/LNP lookup by SIP INVITE/3xx.

Feb 2011:
Yate will attend FOSDEM and XMPP summit.

31 Jan 2011:
Yate 3.1 released.
Yate client support for Google Voice. Support for any country tones in tonegen.

20 Dec 2010:
Yate 3.0 released.
SS7 ITU certified. SS7 STP added. Client supports Jabber IM (Google Talk + Facebook).

3 May 2010:
Yate 3.0.0 alpha 3 released. Featuring the new Jabber server and wideband audio.

8 March 2010:
Yate 2.2 released. Mostly bug fixes. Dahdi compatible. Latest 2 release before 3.0.

6-7 February 2010:
Yate booth at FOSDEM 2010. Free CD with Freesentral available.

2 Nov 2009:
Yate 2.1 launched. Can replace a Cisco PGW2200 to control a Cisco AS54xx.

6 Aug 2008:
Yate and OpenSIPS (former OpenSER) join to build IP based clusters.

4 Aug 2008:
Yate 2 launched.

EditHistoryBacklinksRecent ChangesSearch