Re: [Freeswitch-users] Better results from mod_vmd
Matt, Okay the good news is vmd should be able to handle these cases. The bad news is for whatever reason they are not getting detected at the moment. vmd-not-panasonic-home-ans.wav is a sine at ~1400Hz you can change MAX_FREQ to 1450 and play with MIN_AMPL if that still doesn't help. The following seem to use the same beep: vmd-not-tmobile.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise You can try to play with these values: POINTS 32 VALID 22 MAX_CHIRP 22 If that doesn't work let me know I will try to improve the algorithm to detect the providers. Cheers! Eric des Courtis On Mon, Aug 17, 2009 at 1:52 PM, Matthew Fong<mattdfong@gmail.com> wrote:
Hi Eric, Thanks for the response. I had tried emailing you @brenbria.com and the email had bounced, thanks for responding to my mail. If you'd be interested I .zipped up my sample voicemail beeps at http://bandcon.hellohunter.com/vmd_wav.zip I'm relatively new to telephony, but can you point me in the right direction for figuring out if the beeps are sinewaves. About as far as I've come with audio is being able to open the .wav files in audacity. Any website recommendations I can read? Thanks so much. --matt
On Mon, Aug 17, 2009 at 10:29 AM, Eric des Courtis <eric.des.courtis@gmail.com> wrote:
Matt,
You must first capture the audio beeps and verify that they are sine waves. If not, simply tweaking the algorithm will not give you better results.
It might be possible to use FFT and I would be happy to help you implement such a solution but keep in mind FFT is very very demanding on the hardware. Ideally what you want to find out is what functions was use to generate the beep in the first place so that it can be detected. Is it two sines waves like in DTMF? Or something more complex?
Anyway my email is eric.des.courtis@benbria.ca.
Cheers.
Eric des Courtis
On Mon, Aug 17, 2009 at 12:26 AM, Matthew Fong<mattdfong@gmail.com> wrote:
I tried emailed Eric, seeking advice on this, but his email (the one in the source code) is bouncing email (invalid user), so thought I would ask here instead. If anyone has eric's new email address, I'd be interesting in it.
I did some tests with mod_vmd this afternoon, but I'm only finding about 33% of the voice mail beeps and did have 1 false-positive in my test of 7 voice mail machines. I've recorded the audio of the session in .wav files that were both successful and not, as a comparison. I can upload the .wav files if they would be useful. mod_vmd works great for voicemails of Skype Users, and kall8.com, but has issues dealing with mobile phone carriers. sprint - not successful tmobile - not successful verizon - not successful panasonic home answering machine system - not successful kall8 - SUCCESS skype - SUCCESS I'm wondering if you can recommend a simple fix, like changing some of the constants like MAX_FREQ, or MIN_TIME at the top of the mod_vmd.c source file, or if better success requires more complex analysis. Do you have any recommendations on how this might be done? Listening to the .wav's its apparent the beeps are not as loud for the mobile phone carriers as they are with skype and kall8. Any guidance would be greatly appreciated. --matt hello hunter http://www.hellohunter.com voice broadcasting & hosted dialer _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Hi Eric, Thanks for these recommendations. for vmd-not-panasonic-home-ans.wav changing MAX_FREQ to 1450 WORKED! but I'm still having problems picking out the ~750Hz beep of sprint, tmobile, and verizon. I tried first cutting POINTS and VALID in half, then in half again, while also reducing MIN_AMPL in half but still no luck. I assumed from the descriptions of each, that reducing the numbers would make the algorithm less picky at finding a beep. Is this correct? Any other recommendations on picking up these ~750Hz beeps? Thanks again for the help. --matt On Mon, Aug 17, 2009 at 2:15 PM, Eric des Courtis < eric.des.courtis@gmail.com> wrote:
Matt,
Okay the good news is vmd should be able to handle these cases. The bad news is for whatever reason they are not getting detected at the moment.
vmd-not-panasonic-home-ans.wav is a sine at ~1400Hz you can change MAX_FREQ to 1450 and play with MIN_AMPL if that still doesn't help.
The following seem to use the same beep:
vmd-not-tmobile.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise
You can try to play with these values:
POINTS 32 VALID 22 MAX_CHIRP 22
If that doesn't work let me know I will try to improve the algorithm to detect the providers.
Cheers!
Eric des Courtis
On Mon, Aug 17, 2009 at 1:52 PM, Matthew Fong<mattdfong@gmail.com> wrote:
Hi Eric, Thanks for the response. I had tried emailing you @brenbria.com and the email had bounced, thanks for responding to my mail. If you'd be interested I .zipped up my sample voicemail beeps at http://bandcon.hellohunter.com/vmd_wav.zip I'm relatively new to telephony, but can you point me in the right direction for figuring out if the beeps are sinewaves. About as far as I've come with audio is being able to open the .wav files in audacity. Any website recommendations I can read? Thanks so much. --matt
On Mon, Aug 17, 2009 at 10:29 AM, Eric des Courtis <eric.des.courtis@gmail.com> wrote:
Matt,
You must first capture the audio beeps and verify that they are sine waves. If not, simply tweaking the algorithm will not give you better results.
It might be possible to use FFT and I would be happy to help you implement such a solution but keep in mind FFT is very very demanding on the hardware. Ideally what you want to find out is what functions was use to generate the beep in the first place so that it can be detected. Is it two sines waves like in DTMF? Or something more complex?
Anyway my email is eric.des.courtis@benbria.ca.
Cheers.
Eric des Courtis
On Mon, Aug 17, 2009 at 12:26 AM, Matthew Fong<mattdfong@gmail.com>
wrote:
I tried emailed Eric, seeking advice on this, but his email (the one in the source code) is bouncing email (invalid user), so thought I would ask here instead. If anyone has eric's new email address, I'd be interesting in it.
I did some tests with mod_vmd this afternoon, but I'm only finding about 33% of the voice mail beeps and did have 1 false-positive in my test of 7 voice mail machines. I've recorded the audio of the session in .wav files that were both successful and not, as a comparison. I can upload the .wav files if they would be useful. mod_vmd works great for voicemails of Skype Users, and kall8.com, but has issues dealing with mobile phone carriers. sprint - not successful tmobile - not successful verizon - not successful panasonic home answering machine system - not successful kall8 - SUCCESS skype - SUCCESS I'm wondering if you can recommend a simple fix, like changing some of the constants like MAX_FREQ, or MIN_TIME at the top of the mod_vmd.c source file, or if better success requires more complex analysis. Do you have any recommendations on how this might be done? Listening to the .wav's its apparent the beeps are not as loud for the mobile phone carriers as they are with skype and kall8. Any guidance would be greatly appreciated. --matt hello hunter http://www.hellohunter.com voice broadcasting & hosted dialer _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Wed, Aug 19, 2009 at 1:43 AM, Matthew Fong <mattdfong@gmail.com> wrote:
Hi Eric, Thanks for these recommendations.
for vmd-not-panasonic-home-ans.wav changing MAX_FREQ to 1450 WORKED!
but I'm still having problems picking out the ~750Hz beep of sprint, tmobile, and verizon. I tried first cutting POINTS and VALID in half, then in half again, while also reducing MIN_AMPL in half but still no luck. I assumed from the descriptions of each, that reducing the numbers would make the algorithm less picky at finding a beep. Is this correct?
Any other recommendations on picking up these ~750Hz beeps? Thanks again for the help.
How close are they to 750Hz? If they're not more than say +/- 16Hz then the tone_detect app *should* be able to detect them. At the very least I would try it. See if tone_detect can detect those beeps. While it may not be the most elegant solution, having mod_vmd looking for one set of tones and tone_detect looking for the 750Hz tones might actually get the job done, at least until you and Eric can get together to see what's happening on the 750's. -MC
--matt
On Mon, Aug 17, 2009 at 2:15 PM, Eric des Courtis < eric.des.courtis@gmail.com> wrote:
Matt,
Okay the good news is vmd should be able to handle these cases. The bad news is for whatever reason they are not getting detected at the moment.
vmd-not-panasonic-home-ans.wav is a sine at ~1400Hz you can change MAX_FREQ to 1450 and play with MIN_AMPL if that still doesn't help.
The following seem to use the same beep:
vmd-not-tmobile.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise
You can try to play with these values:
POINTS 32 VALID 22 MAX_CHIRP 22
If that doesn't work let me know I will try to improve the algorithm to detect the providers.
Cheers!
Eric des Courtis
On Mon, Aug 17, 2009 at 1:52 PM, Matthew Fong<mattdfong@gmail.com> wrote:
Hi Eric, Thanks for the response. I had tried emailing you @brenbria.com and the email had bounced, thanks for responding to my mail. If you'd be interested I .zipped up my sample voicemail beeps at http://bandcon.hellohunter.com/vmd_wav.zip I'm relatively new to telephony, but can you point me in the right direction for figuring out if the beeps are sinewaves. About as far as I've come with audio is being able to open the .wav files in audacity. Any website recommendations I can read? Thanks so much. --matt
On Mon, Aug 17, 2009 at 10:29 AM, Eric des Courtis <eric.des.courtis@gmail.com> wrote:
Matt,
You must first capture the audio beeps and verify that they are sine waves. If not, simply tweaking the algorithm will not give you better results.
It might be possible to use FFT and I would be happy to help you implement such a solution but keep in mind FFT is very very demanding on the hardware. Ideally what you want to find out is what functions was use to generate the beep in the first place so that it can be detected. Is it two sines waves like in DTMF? Or something more complex?
Anyway my email is eric.des.courtis@benbria.ca.
Cheers.
Eric des Courtis
On Mon, Aug 17, 2009 at 12:26 AM, Matthew Fong<mattdfong@gmail.com>
wrote:
I tried emailed Eric, seeking advice on this, but his email (the one in the source code) is bouncing email (invalid user), so thought I would ask here instead. If anyone has eric's new email address, I'd be interesting in it.
I did some tests with mod_vmd this afternoon, but I'm only finding about 33% of the voice mail beeps and did have 1 false-positive in my test of 7 voice mail machines. I've recorded the audio of the session in .wav files that were both successful and not, as a comparison. I can upload the .wav files if they would be useful. mod_vmd works great for voicemails of Skype Users, and kall8.com, but has issues dealing with mobile phone carriers. sprint - not successful tmobile - not successful verizon - not successful panasonic home answering machine system - not successful kall8 - SUCCESS skype - SUCCESS I'm wondering if you can recommend a simple fix, like changing some of the constants like MAX_FREQ, or MIN_TIME at the top of the mod_vmd.c source file, or if better success requires more complex analysis. Do you have any recommendations on how this might be done? Listening to the .wav's its apparent the beeps are not as loud for the mobile phone carriers as they are with skype and kall8. Any guidance would be greatly appreciated. --matt hello hunter http://www.hellohunter.com voice broadcasting & hosted dialer _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
my bet is if mod_vmd is not getting them that they are not going to work with tone detect either. Someone needs to look at the tone and see what frequencies are really involved and if they change throughout the beep. Mike On Aug 19, 2009, at 12:41 PM, Michael Collins wrote:
On Wed, Aug 19, 2009 at 1:43 AM, Matthew Fong <mattdfong@gmail.com> wrote: Hi Eric,
Thanks for these recommendations.
for vmd-not-panasonic-home-ans.wav changing MAX_FREQ to 1450 WORKED!
but I'm still having problems picking out the ~750Hz beep of sprint, tmobile, and verizon. I tried first cutting POINTS and VALID in half, then in half again, while also reducing MIN_AMPL in half but still no luck. I assumed from the descriptions of each, that reducing the numbers would make the algorithm less picky at finding a beep. Is this correct?
Any other recommendations on picking up these ~750Hz beeps? Thanks again for the help.
How close are they to 750Hz? If they're not more than say +/- 16Hz then the tone_detect app *should* be able to detect them. At the very least I would try it. See if tone_detect can detect those beeps. While it may not be the most elegant solution, having mod_vmd looking for one set of tones and tone_detect looking for the 750Hz tones might actually get the job done, at least until you and Eric can get together to see what's happening on the 750's.
-MC
--matt
On Mon, Aug 17, 2009 at 2:15 PM, Eric des Courtis <eric.des.courtis@gmail.com
wrote: Matt,
Okay the good news is vmd should be able to handle these cases. The bad news is for whatever reason they are not getting detected at the moment.
vmd-not-panasonic-home-ans.wav is a sine at ~1400Hz you can change MAX_FREQ to 1450 and play with MIN_AMPL if that still doesn't help.
The following seem to use the same beep:
vmd-not-tmobile.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise
You can try to play with these values:
POINTS 32 VALID 22 MAX_CHIRP 22
If that doesn't work let me know I will try to improve the algorithm to detect the providers.
Cheers!
Eric des Courtis
On Mon, Aug 17, 2009 at 1:52 PM, Matthew Fong<mattdfong@gmail.com> wrote:
Hi Eric, Thanks for the response. I had tried emailing you @brenbria.com and the email had bounced, thanks for responding to my mail. If you'd be interested I .zipped up my sample voicemail beeps at http://bandcon.hellohunter.com/vmd_wav.zip I'm relatively new to telephony, but can you point me in the right direction for figuring out if the beeps are sinewaves. About as far as I've come with audio is being able to open the .wav files in audacity. Any website recommendations I can read? Thanks so much. --matt
On Mon, Aug 17, 2009 at 10:29 AM, Eric des Courtis <eric.des.courtis@gmail.com> wrote:
Matt,
You must first capture the audio beeps and verify that they are
sine
waves. If not, simply tweaking the algorithm will not give you better results.
It might be possible to use FFT and I would be happy to help you implement such a solution but keep in mind FFT is very very demanding on the hardware. Ideally what you want to find out is what functions was use to generate the beep in the first place so that it can be detected. Is it two sines waves like in DTMF? Or something more complex?
Anyway my email is eric.des.courtis@benbria.ca.
Cheers.
Eric des Courtis
On Mon, Aug 17, 2009 at 12:26 AM, Matthew Fong<mattdfong@gmail.com> wrote:
I tried emailed Eric, seeking advice on this, but his email (the one in the source code) is bouncing email (invalid user), so thought I would ask here instead. If anyone has eric's new email address, I'd be interesting in it.
I did some tests with mod_vmd this afternoon, but I'm only finding about 33% of the voice mail beeps and did have 1 false-positive in my test of 7 voice mail machines. I've recorded the audio of the session in .wav files that were both successful and not, as a comparison. I can upload the .wav files if they would be useful. mod_vmd works great for voicemails of Skype Users, and kall8.com, but has issues dealing with mobile phone carriers. sprint - not successful tmobile - not successful verizon - not successful panasonic home answering machine system - not successful kall8 - SUCCESS skype - SUCCESS I'm wondering if you can recommend a simple fix, like changing some of the constants like MAX_FREQ, or MIN_TIME at the top of the mod_vmd.c source file, or if better success requires more complex analysis. Do you have any recommendations on how this might be done? Listening to the .wav's its apparent the beeps are not as loud for the mobile phone carriers as they are with skype and kall8. Any guidance would be greatly appreciated. --matt hello hunter http://www.hellohunter.com voice broadcasting & hosted dialer _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Can anyone recommend a tool to analyze the wave files to see what's causing the sine wav not to be detected? I have them zipped at http://bandcon.hellohunter.com/vmd_wav.zip <http://bandcon.hellohunter.com/vmd_wav.zip>I was trying to use audacity, but not sure how to tell the exact frequency. --matt On Wed, Aug 19, 2009 at 10:26 AM, Michael Jerris <mike@jerris.com> wrote:
my bet is if mod_vmd is not getting them that they are not going to work with tone detect either. Someone needs to look at the tone and see what frequencies are really involved and if they change throughout the beep. Mike
On Aug 19, 2009, at 12:41 PM, Michael Collins wrote:
On Wed, Aug 19, 2009 at 1:43 AM, Matthew Fong <mattdfong@gmail.com> wrote:
Hi Eric, Thanks for these recommendations.
for vmd-not-panasonic-home-ans.wav changing MAX_FREQ to 1450 WORKED!
but I'm still having problems picking out the ~750Hz beep of sprint, tmobile, and verizon. I tried first cutting POINTS and VALID in half, then in half again, while also reducing MIN_AMPL in half but still no luck. I assumed from the descriptions of each, that reducing the numbers would make the algorithm less picky at finding a beep. Is this correct?
Any other recommendations on picking up these ~750Hz beeps? Thanks again for the help.
How close are they to 750Hz? If they're not more than say +/- 16Hz then the tone_detect app *should* be able to detect them. At the very least I would try it. See if tone_detect can detect those beeps. While it may not be the most elegant solution, having mod_vmd looking for one set of tones and tone_detect looking for the 750Hz tones might actually get the job done, at least until you and Eric can get together to see what's happening on the 750's.
-MC
--matt
On Mon, Aug 17, 2009 at 2:15 PM, Eric des Courtis < eric.des.courtis@gmail.com> wrote:
Matt,
Okay the good news is vmd should be able to handle these cases. The bad news is for whatever reason they are not getting detected at the moment.
vmd-not-panasonic-home-ans.wav is a sine at ~1400Hz you can change MAX_FREQ to 1450 and play with MIN_AMPL if that still doesn't help.
The following seem to use the same beep:
vmd-not-tmobile.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise
You can try to play with these values:
POINTS 32 VALID 22 MAX_CHIRP 22
If that doesn't work let me know I will try to improve the algorithm to detect the providers.
Cheers!
Eric des Courtis
On Mon, Aug 17, 2009 at 1:52 PM, Matthew Fong<mattdfong@gmail.com> wrote:
Hi Eric, Thanks for the response. I had tried emailing you @brenbria.com and the email had bounced, thanks for responding to my mail. If you'd be interested I .zipped up my sample voicemail beeps at http://bandcon.hellohunter.com/vmd_wav.zip I'm relatively new to telephony, but can you point me in the right direction for figuring out if the beeps are sinewaves. About as far as I've come with audio is being able to open the .wav files in audacity. Any website recommendations I can read? Thanks so much. --matt
On Mon, Aug 17, 2009 at 10:29 AM, Eric des Courtis <eric.des.courtis@gmail.com> wrote:
Matt,
You must first capture the audio beeps and verify that they are sine waves. If not, simply tweaking the algorithm will not give you better results.
It might be possible to use FFT and I would be happy to help you implement such a solution but keep in mind FFT is very very demanding on the hardware. Ideally what you want to find out is what functions was use to generate the beep in the first place so that it can be detected. Is it two sines waves like in DTMF? Or something more complex?
Anyway my email is eric.des.courtis@benbria.ca.
Cheers.
Eric des Courtis
On Mon, Aug 17, 2009 at 12:26 AM, Matthew Fong<mattdfong@gmail.com>
wrote:
I tried emailed Eric, seeking advice on this, but his email (the one in the source code) is bouncing email (invalid user), so thought I would ask here instead. If anyone has eric's new email address, I'd be interesting in it.
I did some tests with mod_vmd this afternoon, but I'm only finding about 33% of the voice mail beeps and did have 1 false-positive in my test of 7 voice mail machines. I've recorded the audio of the session in .wav files that were both successful and not, as a comparison. I can upload the .wav files if they would be useful. mod_vmd works great for voicemails of Skype Users, and kall8.com, but has issues dealing with mobile phone carriers. sprint - not successful tmobile - not successful verizon - not successful panasonic home answering machine system - not successful kall8 - SUCCESS skype - SUCCESS I'm wondering if you can recommend a simple fix, like changing some of the constants like MAX_FREQ, or MIN_TIME at the top of the mod_vmd.c source file, or if better success requires more complex analysis. Do you have any recommendations on how this might be done? Listening to the .wav's its apparent the beeps are not as loud for the mobile phone carriers as they are with skype and kall8. Any guidance would be greatly appreciated. --matt hello hunter http://www.hellohunter.com voice broadcasting & hosted dialer _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Can anyone recommend a tool to analyze the wave files to see what's causing the sine wav not to be detected? I have them zipped at http://bandcon.hellohunter.com/vmd_wav.zip <http://bandcon.hellohunter.com/vmd_wav.zip>I was trying to use audacity, but not sure how to tell the exact frequency. sorry if this was a double post... On Wed, Aug 19, 2009 at 10:26 AM, Michael Jerris <mike@jerris.com> wrote:
my bet is if mod_vmd is not getting them that they are not going to work with tone detect either. Someone needs to look at the tone and see what frequencies are really involved and if they change throughout the beep. Mike
On Aug 19, 2009, at 12:41 PM, Michael Collins wrote:
On Wed, Aug 19, 2009 at 1:43 AM, Matthew Fong <mattdfong@gmail.com> wrote:
Hi Eric, Thanks for these recommendations.
for vmd-not-panasonic-home-ans.wav changing MAX_FREQ to 1450 WORKED!
but I'm still having problems picking out the ~750Hz beep of sprint, tmobile, and verizon. I tried first cutting POINTS and VALID in half, then in half again, while also reducing MIN_AMPL in half but still no luck. I assumed from the descriptions of each, that reducing the numbers would make the algorithm less picky at finding a beep. Is this correct?
Any other recommendations on picking up these ~750Hz beeps? Thanks again for the help.
How close are they to 750Hz? If they're not more than say +/- 16Hz then the tone_detect app *should* be able to detect them. At the very least I would try it. See if tone_detect can detect those beeps. While it may not be the most elegant solution, having mod_vmd looking for one set of tones and tone_detect looking for the 750Hz tones might actually get the job done, at least until you and Eric can get together to see what's happening on the 750's.
-MC
--matt
On Mon, Aug 17, 2009 at 2:15 PM, Eric des Courtis < eric.des.courtis@gmail.com> wrote:
Matt,
Okay the good news is vmd should be able to handle these cases. The bad news is for whatever reason they are not getting detected at the moment.
vmd-not-panasonic-home-ans.wav is a sine at ~1400Hz you can change MAX_FREQ to 1450 and play with MIN_AMPL if that still doesn't help.
The following seem to use the same beep:
vmd-not-tmobile.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise
You can try to play with these values:
POINTS 32 VALID 22 MAX_CHIRP 22
If that doesn't work let me know I will try to improve the algorithm to detect the providers.
Cheers!
Eric des Courtis
On Mon, Aug 17, 2009 at 1:52 PM, Matthew Fong<mattdfong@gmail.com> wrote:
Hi Eric, Thanks for the response. I had tried emailing you @brenbria.com and the email had bounced, thanks for responding to my mail. If you'd be interested I .zipped up my sample voicemail beeps at http://bandcon.hellohunter.com/vmd_wav.zip I'm relatively new to telephony, but can you point me in the right direction for figuring out if the beeps are sinewaves. About as far as I've come with audio is being able to open the .wav files in audacity. Any website recommendations I can read? Thanks so much. --matt
On Mon, Aug 17, 2009 at 10:29 AM, Eric des Courtis <eric.des.courtis@gmail.com> wrote:
Matt,
You must first capture the audio beeps and verify that they are sine waves. If not, simply tweaking the algorithm will not give you better results.
It might be possible to use FFT and I would be happy to help you implement such a solution but keep in mind FFT is very very demanding on the hardware. Ideally what you want to find out is what functions was use to generate the beep in the first place so that it can be detected. Is it two sines waves like in DTMF? Or something more complex?
Anyway my email is eric.des.courtis@benbria.ca.
Cheers.
Eric des Courtis
On Mon, Aug 17, 2009 at 12:26 AM, Matthew Fong<mattdfong@gmail.com>
wrote:
I tried emailed Eric, seeking advice on this, but his email (the one in the source code) is bouncing email (invalid user), so thought I would ask here instead. If anyone has eric's new email address, I'd be interesting in it.
I did some tests with mod_vmd this afternoon, but I'm only finding about 33% of the voice mail beeps and did have 1 false-positive in my test of 7 voice mail machines. I've recorded the audio of the session in .wav files that were both successful and not, as a comparison. I can upload the .wav files if they would be useful. mod_vmd works great for voicemails of Skype Users, and kall8.com, but has issues dealing with mobile phone carriers. sprint - not successful tmobile - not successful verizon - not successful panasonic home answering machine system - not successful kall8 - SUCCESS skype - SUCCESS I'm wondering if you can recommend a simple fix, like changing some of the constants like MAX_FREQ, or MIN_TIME at the top of the mod_vmd.c source file, or if better success requires more complex analysis. Do you have any recommendations on how this might be done? Listening to the .wav's its apparent the beeps are not as loud for the mobile phone carriers as they are with skype and kall8. Any guidance would be greatly appreciated. --matt hello hunter http://www.hellohunter.com voice broadcasting & hosted dialer _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Wed, 19 Aug 2009 14:50:34 -0400, Matthew Fong <mattdfong@gmail.com> wrote:
I was trying to use audacity, but not sure how to tell the exact frequency.
Audacity can do it. Highlight the "beep" (and nothing but the beep) with the selection cursor, then click "Analyze->Plot Spectrum..." In the "Frequency Analysis" window that opens, place the cursor on the center of the largest peak. Near the base of that window it will show the Cursor and Peak frequencies. For example, in the "vmd-not-panasonic-home-ans.wav" file, the "beep" is 1400 Hz (for a very short 1 second). Then later it switches to FAX CED tone (2100 Hz) and FAX preamble. --Woof!
On 08/18/2009 05:15 AM, Eric des Courtis wrote:
Matt,
Okay the good news is vmd should be able to handle these cases. The bad news is for whatever reason they are not getting detected at the moment.
vmd-not-panasonic-home-ans.wav is a sine at ~1400Hz you can change MAX_FREQ to 1450 and play with MIN_AMPL if that still doesn't help.
The following seem to use the same beep:
vmd-not-tmobile.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise vmd-not-sprint.wav is a sine at ~750Hz but has a bit of noise
You can try to play with these values:
POINTS 32 VALID 22 MAX_CHIRP 22
If that doesn't work let me know I will try to improve the algorithm to detect the providers.
There is no noise on those 3 beeps. In fact, for something that's been through ulaw/alaw compression those beeps are very clean. They are quite short, though. Steve
There is no noise on those 3 beeps. In fact, for something that's been through ulaw/alaw compression those beeps are very clean. They are quite short, though.
Heck yeah they're short! Steve, in your experience is there a practical way to detect a beep that short without chewing up system resources or having lots of false positives? -MC
On 08/20/2009 05:22 AM, Michael Collins wrote:
There is no noise on those 3 beeps. In fact, for something that's been through ulaw/alaw compression those beeps are very clean. They are quite short, though.
Heck yeah they're short! Steve, in your experience is there a practical way to detect a beep that short without chewing up system resources or having lots of false positives? -MC
The tone samples I just looked at are about 130ms long. The problem is the detector is trying to be a very open ended detector of anything narrowband enough to be a single tone, and of any duration beyond some small minimum. Its difficult to make such a thing voice immune unless you can also count on a very large signal to noise ratio. With a digital trunk you can probably rely on a large SNR, but what happens when people use analogue lines? There is a reason why DTMF detectors try hard to work down to about 10dB SNR. :-) Steve
On Thu, Aug 20, 2009 at 11:06 AM, Steve Underwood <steveu@coppice.org>wrote:
On 08/20/2009 05:22 AM, Michael Collins wrote:
There is no noise on those 3 beeps. In fact, for something that's
been
through ulaw/alaw compression those beeps are very clean. They are quite short, though.
Heck yeah they're short! Steve, in your experience is there a practical way to detect a beep that short without chewing up system resources or having lots of false positives? -MC
The tone samples I just looked at are about 130ms long. The problem is the detector is trying to be a very open ended detector of anything narrowband enough to be a single tone, and of any duration beyond some small minimum. Its difficult to make such a thing voice immune unless you can also count on a very large signal to noise ratio. With a digital trunk you can probably rely on a large SNR, but what happens when people use analogue lines? There is a reason why DTMF detectors try hard to work down to about 10dB SNR. :-)
Steve
Thanks for the lesson uncle Steve! I'm guessing that the OP will need a new strategy. Possibly waiting for silence? Not sure what's the best way to go but I'm interested in hearing if someone has a solution. -MC
Matt, For your information the tones you gave me are exactly 738Hz. If you want to try that tone detection thing. Cheers. Eric des Courtis On Thu, Aug 20, 2009 at 2:20 PM, Michael Collins<msc@freeswitch.org> wrote:
On Thu, Aug 20, 2009 at 11:06 AM, Steve Underwood <steveu@coppice.org> wrote:
On 08/20/2009 05:22 AM, Michael Collins wrote:
There is no noise on those 3 beeps. In fact, for something that's been through ulaw/alaw compression those beeps are very clean. They are quite short, though.
Heck yeah they're short! Steve, in your experience is there a practical way to detect a beep that short without chewing up system resources or having lots of false positives? -MC
The tone samples I just looked at are about 130ms long. The problem is the detector is trying to be a very open ended detector of anything narrowband enough to be a single tone, and of any duration beyond some small minimum. Its difficult to make such a thing voice immune unless you can also count on a very large signal to noise ratio. With a digital trunk you can probably rely on a large SNR, but what happens when people use analogue lines? There is a reason why DTMF detectors try hard to work down to about 10dB SNR. :-)
Steve
Thanks for the lesson uncle Steve! I'm guessing that the OP will need a new strategy. Possibly waiting for silence? Not sure what's the best way to go but I'm interested in hearing if someone has a solution.
-MC
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Matt, As is mod_vmd will not detect tones shorter then 138ms. However I could get that value down to ~30ms at best by making a few modifications to the algorithm. Cheers. Eric des Courtis On Thu, Aug 20, 2009 at 7:51 PM, Eric des Courtis<eric.des.courtis@gmail.com> wrote:
Matt,
For your information the tones you gave me are exactly 738Hz. If you want to try that tone detection thing.
Cheers.
Eric des Courtis
On Thu, Aug 20, 2009 at 2:20 PM, Michael Collins<msc@freeswitch.org> wrote:
On Thu, Aug 20, 2009 at 11:06 AM, Steve Underwood <steveu@coppice.org> wrote:
On 08/20/2009 05:22 AM, Michael Collins wrote:
There is no noise on those 3 beeps. In fact, for something that's been through ulaw/alaw compression those beeps are very clean. They are quite short, though.
Heck yeah they're short! Steve, in your experience is there a practical way to detect a beep that short without chewing up system resources or having lots of false positives? -MC
The tone samples I just looked at are about 130ms long. The problem is the detector is trying to be a very open ended detector of anything narrowband enough to be a single tone, and of any duration beyond some small minimum. Its difficult to make such a thing voice immune unless you can also count on a very large signal to noise ratio. With a digital trunk you can probably rely on a large SNR, but what happens when people use analogue lines? There is a reason why DTMF detectors try hard to work down to about 10dB SNR. :-)
Steve
Thanks for the lesson uncle Steve! I'm guessing that the OP will need a new strategy. Possibly waiting for silence? Not sure what's the best way to go but I'm interested in hearing if someone has a solution.
-MC
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
I changed /*! Minimum time for a beep. */ #define MIN_TIME 8000 to 6500 and it seemed to work, but I'm not sure how many false positives I will get in a real-world environment. at 4000 it fired the event like 5 times in a session, but 6500 only once. Do you think I should expect a lot of false positives after changing this value? --matt http://www.hellohunter.com On Thu, Aug 20, 2009 at 4:54 PM, Eric des Courtis < eric.des.courtis@gmail.com> wrote:
Matt,
As is mod_vmd will not detect tones shorter then 138ms. However I could get that value down to ~30ms at best by making a few modifications to the algorithm.
Cheers.
Eric des Courtis
On Thu, Aug 20, 2009 at 7:51 PM, Eric des Courtis<eric.des.courtis@gmail.com> wrote:
Matt,
For your information the tones you gave me are exactly 738Hz. If you want to try that tone detection thing.
Cheers.
Eric des Courtis
On Thu, Aug 20, 2009 at 2:20 PM, Michael Collins<msc@freeswitch.org> wrote:
On Thu, Aug 20, 2009 at 11:06 AM, Steve Underwood <steveu@coppice.org> wrote:
On 08/20/2009 05:22 AM, Michael Collins wrote:
There is no noise on those 3 beeps. In fact, for something that's been through ulaw/alaw compression those beeps are very clean. They
are
quite short, though.
Heck yeah they're short! Steve, in your experience is there a practical way to detect a beep that short without chewing up system resources or having lots of false positives? -MC
The tone samples I just looked at are about 130ms long. The problem is the detector is trying to be a very open ended detector of anything narrowband enough to be a single tone, and of any duration beyond some small minimum. Its difficult to make such a thing voice immune unless you can also count on a very large signal to noise ratio. With a digital trunk you can probably rely on a large SNR, but what happens when people use analogue lines? There is a reason why DTMF detectors try hard to work down to about 10dB SNR. :-)
Steve
Thanks for the lesson uncle Steve! I'm guessing that the OP will need a new strategy. Possibly waiting for silence? Not sure what's the best way to go but I'm interested in hearing if someone has a solution.
-MC
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Matt, I think the only way to know for sure is to try it. I would try to get the value as high as possible while still detecting that 738Hz sine (with a small margin of error). Lowering the value increases false positives rapidly. Eric des Courtis On Thu, Aug 20, 2009 at 8:36 PM, Matthew Fong<mattdfong@gmail.com> wrote:
I changed
/*! Minimum time for a beep. */ #define MIN_TIME 8000 to 6500 and it seemed to work, but I'm not sure how many false positives I will get in a real-world environment. at 4000 it fired the event like 5 times in a session, but 6500 only once. Do you think I should expect a lot of false positives after changing this value?
--matt http://www.hellohunter.com
On Thu, Aug 20, 2009 at 4:54 PM, Eric des Courtis <eric.des.courtis@gmail.com> wrote:
Matt,
As is mod_vmd will not detect tones shorter then 138ms. However I could get that value down to ~30ms at best by making a few modifications to the algorithm.
Cheers.
Eric des Courtis
On Thu, Aug 20, 2009 at 7:51 PM, Eric des Courtis<eric.des.courtis@gmail.com> wrote:
Matt,
For your information the tones you gave me are exactly 738Hz. If you want to try that tone detection thing.
Cheers.
Eric des Courtis
On Thu, Aug 20, 2009 at 2:20 PM, Michael Collins<msc@freeswitch.org> wrote:
On Thu, Aug 20, 2009 at 11:06 AM, Steve Underwood <steveu@coppice.org> wrote:
On 08/20/2009 05:22 AM, Michael Collins wrote:
There is no noise on those 3 beeps. In fact, for something that's been through ulaw/alaw compression those beeps are very clean. They are quite short, though.
Heck yeah they're short! Steve, in your experience is there a practical way to detect a beep that short without chewing up system resources or having lots of false positives? -MC
The tone samples I just looked at are about 130ms long. The problem is the detector is trying to be a very open ended detector of anything narrowband enough to be a single tone, and of any duration beyond some small minimum. Its difficult to make such a thing voice immune unless you can also count on a very large signal to noise ratio. With a digital trunk you can probably rely on a large SNR, but what happens when people use analogue lines? There is a reason why DTMF detectors try hard to work down to about 10dB SNR. :-)
Steve
Thanks for the lesson uncle Steve! I'm guessing that the OP will need a new strategy. Possibly waiting for silence? Not sure what's the best way to go but I'm interested in hearing if someone has a solution.
-MC
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Thu, Aug 20, 2009 at 6:36 PM, Matthew Fong<mattdfong@gmail.com> wrote:
/*! Minimum time for a beep. */ #define MIN_TIME 8000 to 6500 and it seemed to work, but I'm not sure how many false positives I will get in a real-world environment. at 4000 it fired the event like 5 times in a session, but 6500 only once. Do you think I should expect a lot of false positives after changing this value?
YES.
On Thu, Aug 20, 2009 at 9:16 PM, Gabriel Gunderson<gabe@gundy.org> wrote:
On Thu, Aug 20, 2009 at 6:36 PM, Matthew Fong<mattdfong@gmail.com> wrote:
/*! Minimum time for a beep. */ #define MIN_TIME 8000 to 6500 and it seemed to work, but I'm not sure how many false positives I will get in a real-world environment. at 4000 it fired the event like 5 times in a session, but 6500 only once. Do you think I should expect a lot of false positives after changing this value?
YES.
Err, NO.
participants (8)
-
Andy Spitzer
-
Eric des Courtis
-
Gabriel Gunderson
-
Matt Hunter
-
Matthew Fong
-
Michael Collins
-
Michael Jerris
-
Steve Underwood