Thread: [Asterisk-java-users] MonitorAction, audio formats and mixing.
Brought to you by:
srt
From: Jan G. du T. <s22...@tu...> - 2005-12-13 13:07:18
|
Hi. Can somebody please supply me with a list of all surported recording audio formats that MonitorAction supports? Also, I have set my MonitorAction mixing variable to true, but it doesn't "join" the in and out channels, it still produces two seperate files with the recorded in and out channels. I am using .wav format. Does the chosen format have something to do with my mixing problem? Thanks in advance. |
From: Jan G. du T. <s22...@tu...> - 2005-12-15 05:29:24
|
Hi. Can somebody please supply me with a list of all surported recording audio formats that MonitorAction supports? Also, I have set my MonitorAction mixing variable to true, but it doesn't "join" the in and out channels, it still produces two seperate files with the recorded in and out channels. I am using .wav format. Does the chosen format have something to do with my mixing problem? Thanks in advance. |
From: Stefan R. <sr...@re...> - 2005-12-15 09:03:56
Attachments:
signature.asc
|
Jan Gerryt du Toit schrieb: > Hi. > > Can somebody please supply me with a list of all surported recording audio > formats that MonitorAction supports? you can use any of the audio formats for monitoring that asterisk supports. type show file formats on the asterisk console to get a list. > Also, I have set my MonitorAction mixing variable to true, but it doesn't "join" > the in and out channels, it still produces two seperate files with the recorded > in and out channels. I am using .wav format. Does the chosen format have > something to do with my mixing problem? Asterisk uses soxmix to mix the files therefore soxmix must be installed on the Asterisk machine and must be available on the PATH. =Stefan |
From: Jonathan A. <jau...@st...> - 2005-12-14 04:52:20
|
I am developing an IVR application. I have done some prototyping with the AGI interface and it does not quite work the way I need. I have determined that the asynchronous behavior of the Manager API is a better fit. However, I have been unable to determine how to call CLI applications. For instance, I need to play a prompt file and collect DTMF digits to allow the caller to enter an ID code. Can someone please point me in the direction of how to accomplish this? Jonathan |
From: Stefan R. <sr...@re...> - 2005-12-14 07:52:22
|
Hi Jonathan, what problems did you encounter when you tried the AGI interface? The AGI interface is usually much better suited for IVR style applications than the Manager API. =3DStefan On Tue, 2005-12-13 at 20:52 -0800, Jonathan Augenstine wrote: > I am developing an IVR application. I have done some prototyping with > the AGI interface and it does not quite work the way I need. I have > determined that the asynchronous behavior of the Manager API is a better > fit. However, I have been unable to determine how to call CLI > applications. For instance, I need to play a prompt file and collect > DTMF digits to allow the caller to enter an ID code. Can someone please > point me in the direction of how to accomplish this? >=20 > Jonathan >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > Asterisk-java-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/asterisk-java-users |
From: Jonathan A. <jau...@st...> - 2005-12-14 15:59:55
|
Stefan, The specific problem I encountered is that I make an outbound call from Asterisk using the execCommand(Dial). The problem is that the execCommand call blocks and I need to have the application and move on to other tasks. Specifically, I have an inbound call to Asterisk, it does some user id/account verification and then makes an outbound call. I need to make the outbound call, perform other tasks, and then disconnect the outbound call. I concluded that while the AGI worked great for the initial IVR portion, some of the other actions I needed to perform had a better fit to an event driven model. Jonathan On Wed, 2005-12-14 at 07:54 +0000, Stefan Reuter wrote: > Hi Jonathan, > > what problems did you encounter when you tried the AGI interface? > The AGI interface is usually much better suited for IVR style > applications than the Manager API. > > =Stefan > > On Tue, 2005-12-13 at 20:52 -0800, Jonathan Augenstine wrote: > > I am developing an IVR application. I have done some prototyping with > > the AGI interface and it does not quite work the way I need. I have > > determined that the asynchronous behavior of the Manager API is a better > > fit. However, I have been unable to determine how to call CLI > > applications. For instance, I need to play a prompt file and collect > > DTMF digits to allow the caller to enter an ID code. Can someone please > > point me in the direction of how to accomplish this? > > > > Jonathan > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > > _______________________________________________ > > Asterisk-java-users mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/asterisk-java-users |
From: Stefan R. <sr...@re...> - 2005-12-14 16:38:56
|
On Wed, 2005-12-14 at 08:00 -0800, Jonathan Augenstine wrote: > The specific problem I encountered is that I make an outbound call from > Asterisk using the execCommand(Dial). The problem is that the > execCommand call blocks and I need to have the application and move on > to other tasks. Thanks for the clarification. I propose to use AGI for the identification as you said that already works well. I understand you problem with the exec dial though. For this there are two solutions. First you can call setContext, setExtension and setPriority inside your AGI script instead of exec dial. This causes the call to continue at the given extension in the dialplan when the AGI script ends. Second you could just issue a RedirectAction via the Manager API at the end of the AGI script. That way you can combine the strenghts of both interfaces (and you probably already use the Manager API to originate the outbound call). Do you think this would solve your problem? =3DStefan |
From: Jonathan A. <jau...@st...> - 2005-12-14 17:16:18
|
Stefan, Thank you very much for your input. You have confirmed some ideas I have been working with last night which was to integrate AGI/Manager API. I was not yet confident that was the solution. I wanted to make sure I was not missing something in looking at the Manager API. I believe that utilization of both interfaces will provide the capabilities I need. Thanks again for your help. Jonathan On Wed, 2005-12-14 at 16:40 +0000, Stefan Reuter wrote: > > On Wed, 2005-12-14 at 08:00 -0800, Jonathan Augenstine wrote: > > The specific problem I encountered is that I make an outbound call from > > Asterisk using the execCommand(Dial). The problem is that the > > execCommand call blocks and I need to have the application and move on > > to other tasks. > > Thanks for the clarification. > I propose to use AGI for the identification as you said that already > works well. I understand you problem with the exec dial though. For this > there are two solutions. First you can call setContext, setExtension and > setPriority inside your AGI script instead of exec dial. This causes the > call to continue at the given extension in the dialplan when the AGI > script ends. Second you could just issue a RedirectAction via the > Manager API at the end of the AGI script. > That way you can combine the strenghts of both interfaces (and you > probably already use the Manager API to originate the outbound call). > Do you think this would solve your problem? > > =Stefan |