Dbwave - Revision history

Monica at 10:10, 4 November 2013

2013-11-04T10:10:50Z

Dana at 12:18, 11 June 2013

2013-06-11T12:18:46Z

Dana at 12:18, 11 June 2013

2013-06-11T12:18:28Z

Dana at 12:14, 11 June 2013

2013-06-11T12:14:17Z

Dana at 14:27, 10 June 2013

2013-06-10T14:27:49Z

Dana at 14:24, 10 June 2013

2013-06-10T14:24:46Z

Dana at 14:10, 16 October 2012

2012-10-16T14:10:59Z

Dana: Created page with " This module works with wavefile and a database driver (currently MySQL only!) to play or record wave sounds in binary database records. From a routing module you can pla..."

2012-10-16T14:09:41Z

Created page with " This module works with wavefile and a database driver (currently MySQL only!) to play or record wave sounds in binary database records. From a routing module you can pla..."

New page

This module works with [[wavefile]] and a database driver (currently MySQL only!) to play or record wave sounds in binary database records.

From a routing module you can play a wave record like this:

^1$=dbwave/play//path/to/fallback/file/audiotoplay.slin;callto_account=dbaccount;callto_query=SELECT binary_field FROM table WHERE condition

Or new syntax since Yate 3.3.3

To play a sound file and hangup the call

^1$=fork;callto.1=dbwave/play//path/to/fallback/file/audiotoplay.slin;callto.1.callto_account=dbaccount;callto.1.callto_query=SELECT binary_field FROM table WHERE condition
;callto.1.fork.autoring=true;callto.2=error;stoperror=busy;autoanswer=yes

To record a wave you can use this:

^1$=dbwave/record//path/to/file/audiorecorded.slin;callto_account=dbaccount;callto_query=INSERT INTO table(binary_field) VALUES('$($){data}')

In the example above the construction '''$($){data}''' is specific to regexroute. The raw string required is '''${data}'''

The matching [[call.execute]], [[chan.attach]] and [[chan.record]] messages are modified just before being received by wavefile.

For playback (parameters ''source'', ''override'' or ''replace'') the query is executed and the result (must be exactly 1 row, 1 column, binary) is passed to the wavefile module as a DataBlock.

For recording (parameters ''consumer'', ''call'' or ''peer'') a memory stream is created that executes the query after all data is collected. The query can contain two variable parameters:
* '''${data}''' - holds the collected binary data
* '''${length}''' - holds the length of the data in bytes

The name of the parameters holding the database account and the query depends on the relevant parameter of the message.
* ''param'' - holds the desired attach or record (example: override)
* ''param_account'' - holds the database account used (example: override_account)
* ''param_query'' - holds the query to execute (example: override_query)

This way you can specify different accounts and queries even if you attach or record multiple data channels in the same message.

For [[callexecute|call.execute]] (when routing directly to the module) the relevant parameter is '''callto'''.

=== Example===

To record wave data from an external module do this:

%%>message:<id>:<time>:chan.attach::consumer=dbwave/record/arbitrary.alaw:notify=myid42:single=true:consumer_account=dbaccount:consumer_query=INSERT INTO table(len,data) VALUES('${length}','${data}')

← Older revision		Revision as of 10:10, 4 November 2013
Line 54:		Line 54:

	* [[Modules]]		* [[Modules]]
		+
		+	[[Category:Wave]] [[Category:Database]]

← Older revision		Revision as of 12:18, 11 June 2013
Line 1:		Line 1:

−	This module works with [[wavefile]] module and a database driver currently only [[MySQL]].	+	This module works with [[wavefile]] module and a database driver, currently only [[MySQL]].

	The module is used to play or record wave sounds. The wave sounds are kept in binary database records.		The module is used to play or record wave sounds. The wave sounds are kept in binary database records.

← Older revision		Revision as of 12:18, 11 June 2013
Line 1:		Line 1:

−	This module works with [[wavefile]] module and a database driver (currently ~~MySQL~~ only!).	+	This module works with [[wavefile]] module and a database driver currently only [[MySQL]].

	The module is used to play or record wave sounds. The wave sounds are kept in binary database records.		The module is used to play or record wave sounds. The wave sounds are kept in binary database records.

← Older revision		Revision as of 12:14, 11 June 2013
Line 1:		Line 1:

−	This module works with [[wavefile]] and a database driver (currently MySQL only!) to play or record wave sounds in binary database records.	+	This module works with [[wavefile]] module and a database driver (currently MySQL only!).
		+
		+	The module is used to play or record wave sounds. The wave sounds are kept in binary database records.

	===Play a wave record===		===Play a wave record===

@@ Line 30: / Line 30: @@
 * '''${data}''' - holds the collected binary data
 * '''${length}''' - holds the length of the data in bytes
 The name of the parameters holding the database account and the query depends on the relevant parameter of the message.

@@ Line 1: / Line 1: @@
 This module works with [[wavefile]] and a database driver (currently MySQL only!) to play or record wave sounds in binary database records.
 From a routing module you can play a wave record like this:
@@ Line 12: / Line 14: @@
   ^1$=fork;callto.1=dbwave/play//path/to/fallback/file/audiotoplay.slin;callto.1.callto_account=dbaccount;callto.1.callto_query=SELECT binary_field FROM table WHERE condition
   ;callto.1.fork.autoring=true;callto.2=error;stoperror=busy;autoanswer=yes
 To record a wave you can use this:
@@ Line 34: / Line 38: @@
 This way you can specify different accounts and queries even if you attach or record multiple data channels in the same message.
-For [[callexecute|call.execute]] (when routing directly to the module) the relevant parameter is '''callto'''.
+For [[call.execute]] (when routing directly to the module) the relevant parameter is '''callto'''.
 === Example===
@@ Line 42: / Line 46: @@
   %%&gt;message:&lt;id&gt;:&lt;time&gt;:chan.attach::consumer=dbwave/record/arbitrary.alaw:notify=myid42:single=true:consumer_account=dbaccount:consumer_query=INSERT INTO table(len,data)
   VALUES('${length}','${data}')

← Older revision		Revision as of 14:10, 16 October 2012
Line 40:		Line 40:
	To record wave data from an external module do this:		To record wave data from an external module do this:

−	%%>message:<id>:<time>:chan.attach::consumer=dbwave/record/arbitrary.alaw:notify=myid42:single=true:consumer_account=dbaccount:consumer_query=INSERT INTO table(len,data) VALUES('${length}','${data}')	+	%%>message:<id>:<time>:chan.attach::consumer=dbwave/record/arbitrary.alaw:notify=myid42:single=true:consumer_account=dbaccount:consumer_query=INSERT INTO table(len,data)
		+	VALUES('${length}','${data}')