Re: [asterisk-dev] confbridge DTMF
Hi Thanks for reply. Actually, what I have tried to do is, I don't configure any menu in confbridge.conf file, and here is application syntax like... ConfBridge(conference[,bridge_profile[,user_profile[,menu]]]). But from asterisk's dialplan, I just passed ConfBridge(CONFERENCE_NUMBER), nothing else, so bridge user has don't have any menu option, while user pressed '*', so now how can i read DTMF, using any asterisk standard function. As we have Meetme application, in which user join the meetme room and then pressed '*' it will play file e.g. conf-adminmenu I would like to do same thing in confbridge. -- Chandrakant Solanki On Fri, Dec 20, 2013 at 9:41 PM, Jason Ostrom wrote: > Chandrakant, > > It's my understanding that DTMF should be automatically detected on the > conference if the SIP UA has correct DTMF mode, such as the following in > sip.conf for peer: > dtmfmode=rfc2833 > > In ingress through SIP trunk your provider would have to properly relay > through rfc2833 or SIP INFO. > > The way I have been able to detect DTMF detection using confbridge is to > configuring logger.conf to display DTMF on console, such as: > console => notice,warning,error,dtmf > > In confbridge.conf you can have a simple menu to verify actions such as > muting, etc., and this is how I have been testing menu responses as > confbridge app detecting DTMF. > > My issue is that I can't get DTMF relay/broadcast to work so that any DTMF > digits entered are picked up by other conference users. I think the > setting is: > dtmf_passthrough=yes > > Let me know if I can help further or if you figure out how to do DTMF > Broadcast / relay to all conference participants. > > > On Dec 19, 2013, at 11:13 PM, Chandrakant Solanki < > solanki.chandrak...@gmail.com> wrote: > > > Hello All, > > > > I am using ConfBridge application using Asterisk 11.5.1. > > > > I would like to know is there any way to detect DTMF, without > configuring menu in confbridge.conf. If yes, then how it could be, please > help me. > > > > I would like to do thing like, user entered conference number and he is > into the conference, and when user press '*' then menu gets activated and > play prompt file. > > > > -- > > Chandrakant Solanki > > -- > > _ > > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > > > asterisk-dev mailing list > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-dev > > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Additional release checksums?
On Sun, Dec 22, 2013 at 1:25 PM, Ben Langfeld wrote: > But how do I know which one of those is which hash, since they're not > labelled? > The *sum programs can tell by the length. md5 is 32, sha1 is 40, sha256 is 64, etc. They ignore with warnings lines that don't match length. > > > On 22 December 2013 16:11, George Joseph wrote: > >> The *sum tools will test all lines in a checksum file and will return 0 >> if any match or 1 if none match. >> >> md5sum --quiet -c xxx.asc < xxx.tar.gz >> sha1sum --quiet -c xxx.asc < xxx.tar.gz >> sha256sum --quiet -c xxx.asc < xxx.tar.gz >> >> where xxx.asc is >> ecb9ac329728d0b2b947d4b2fba85b53b00dbf81737fc6db7e5e343025f98536 >> xxx.tar.gz >> 28f1a190d4b4d03a36744e9ba8518c8ca42e9276 xxx.tar.gz >> 5feb02a70a357cbbca1458498d5ed655 xxx.tar.gz >> >> will all return 0. >> >> sha512sum --quiet -c xxx.asc < xxx.tar.gz >> >> will return 1 because there's no sha512 line in the text file. >> >> >> >> >> >> >> On Sun, Dec 22, 2013 at 9:27 AM, Matthew Jordan wrote: >> >>> >>> On Sun, Dec 22, 2013 at 7:31 AM, Ben Langfeld wrote: >>> If everything went in one checksum file, how would one (or shasum) tell each of the checksums apart? I'll submit a patch to mkrelease for the extra files. >>> I was thinking a JSON blob, but I'm perfectly happy with multiple files >>> as well. >>> >>> -- >>> Matthew Jordan >>> Digium, Inc. | Engineering Manager >>> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA >>> Check us out at: http://digium.com & http://asterisk.org >>> >>> -- >>> _ >>> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >>> >>> asterisk-dev mailing list >>> To UNSUBSCRIBE or update options visit: >>>http://lists.digium.com/mailman/listinfo/asterisk-dev >>> >> >> >> -- >> _ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-dev mailing list >> To UNSUBSCRIBE or update options visit: >>http://lists.digium.com/mailman/listinfo/asterisk-dev >> > > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Additional release checksums?
But how do I know which one of those is which hash, since they're not labelled? On 22 December 2013 16:11, George Joseph wrote: > The *sum tools will test all lines in a checksum file and will return 0 if > any match or 1 if none match. > > md5sum --quiet -c xxx.asc < xxx.tar.gz > sha1sum --quiet -c xxx.asc < xxx.tar.gz > sha256sum --quiet -c xxx.asc < xxx.tar.gz > > where xxx.asc is > ecb9ac329728d0b2b947d4b2fba85b53b00dbf81737fc6db7e5e343025f98536 > xxx.tar.gz > 28f1a190d4b4d03a36744e9ba8518c8ca42e9276 xxx.tar.gz > 5feb02a70a357cbbca1458498d5ed655 xxx.tar.gz > > will all return 0. > > sha512sum --quiet -c xxx.asc < xxx.tar.gz > > will return 1 because there's no sha512 line in the text file. > > > > > > > On Sun, Dec 22, 2013 at 9:27 AM, Matthew Jordan wrote: > >> >> On Sun, Dec 22, 2013 at 7:31 AM, Ben Langfeld wrote: >> >>> If everything went in one checksum file, how would one (or shasum) tell >>> each of the checksums apart? >>> >>> I'll submit a patch to mkrelease for the extra files. >>> >>> >> I was thinking a JSON blob, but I'm perfectly happy with multiple files >> as well. >> >> -- >> Matthew Jordan >> Digium, Inc. | Engineering Manager >> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA >> Check us out at: http://digium.com & http://asterisk.org >> >> -- >> _ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-dev mailing list >> To UNSUBSCRIBE or update options visit: >>http://lists.digium.com/mailman/listinfo/asterisk-dev >> > > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Additional release checksums?
The *sum tools will test all lines in a checksum file and will return 0 if any match or 1 if none match. md5sum --quiet -c xxx.asc < xxx.tar.gz sha1sum --quiet -c xxx.asc < xxx.tar.gz sha256sum --quiet -c xxx.asc < xxx.tar.gz where xxx.asc is ecb9ac329728d0b2b947d4b2fba85b53b00dbf81737fc6db7e5e343025f98536 xxx.tar.gz 28f1a190d4b4d03a36744e9ba8518c8ca42e9276 xxx.tar.gz 5feb02a70a357cbbca1458498d5ed655 xxx.tar.gz will all return 0. sha512sum --quiet -c xxx.asc < xxx.tar.gz will return 1 because there's no sha512 line in the text file. On Sun, Dec 22, 2013 at 9:27 AM, Matthew Jordan wrote: > > On Sun, Dec 22, 2013 at 7:31 AM, Ben Langfeld wrote: > >> If everything went in one checksum file, how would one (or shasum) tell >> each of the checksums apart? >> >> I'll submit a patch to mkrelease for the extra files. >> >> > I was thinking a JSON blob, but I'm perfectly happy with multiple files as > well. > > -- > Matthew Jordan > Digium, Inc. | Engineering Manager > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > Check us out at: http://digium.com & http://asterisk.org > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Additional release checksums?
On Sun, Dec 22, 2013 at 7:31 AM, Ben Langfeld wrote: > If everything went in one checksum file, how would one (or shasum) tell > each of the checksums apart? > > I'll submit a patch to mkrelease for the extra files. > > I was thinking a JSON blob, but I'm perfectly happy with multiple files as well. -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Additional release checksums?
Patch submitted for review: https://reviewboard.asterisk.org/r/3091/ On 22 December 2013 11:31, Ben Langfeld wrote: > If everything went in one checksum file, how would one (or shasum) tell > each of the checksums apart? > > I'll submit a patch to mkrelease for the extra files. > > > On 21 December 2013 22:57, Matthew Jordan wrote: > >> >> On Sat, Dec 21, 2013 at 4:26 PM, Paul Belanger < >> paul.belan...@polybeacon.com> wrote: >> >>> On 13-12-21 11:04 AM, Ben Langfeld wrote: >>> Congrats to all on the 12 release yesterday. There's some excellent work that's gone into that release and we're all very grateful and excited about using it. Unfortunately, Chef only currently supports SHA-256 checksums of downloaded files. This means that in order to properly release new builds of Asterisk to my machines, I need to manually download the release, verify the SHA1, generate a SHA-256, feed this to Chef and converge. There's work underway on Chef to support other checksum types, but it might be helpful regardless for Asterisk to include other checksum types. Would it be a lot of work to add at least SHA-256, if not MD5 as well, to the release process? The build script for asterisk releases are located in repotools[1], so >>> adding support should be a matter of just submitting a patch to the tracker. >>> >>> [1] http://svnview.digium.com/svn/repotools/ >>> >> >> It's pretty trivial to update mkrelease and releaser to create a new >> checksum file using sha256sum/md5sum. >> >> The question is: if we're going to generate three checksums, is it >> worthwhile to put them all into a single checksum file? Or do we want three >> separate files? >> >> Going the separate file approach would end up generating 6 files per >> release (3 for the release, 3 for the patch), times 3 supported release >> branches. Not that it would take up a lot of disk space, but it would be >> more stuff to browse through. >> >> Matt >> >> -- >> Matthew Jordan >> Digium, Inc. | Engineering Manager >> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA >> Check us out at: http://digium.com & http://asterisk.org >> >> -- >> _ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-dev mailing list >> To UNSUBSCRIBE or update options visit: >>http://lists.digium.com/mailman/listinfo/asterisk-dev >> > > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Additional release checksums?
If everything went in one checksum file, how would one (or shasum) tell each of the checksums apart? I'll submit a patch to mkrelease for the extra files. On 21 December 2013 22:57, Matthew Jordan wrote: > > On Sat, Dec 21, 2013 at 4:26 PM, Paul Belanger < > paul.belan...@polybeacon.com> wrote: > >> On 13-12-21 11:04 AM, Ben Langfeld wrote: >> >>> Congrats to all on the 12 release yesterday. There's some excellent work >>> that's gone into that release and we're all very grateful and excited >>> about >>> using it. >>> >>> Unfortunately, Chef only currently supports SHA-256 checksums of >>> downloaded >>> files. This means that in order to properly release new builds of >>> Asterisk >>> to my machines, I need to manually download the release, verify the SHA1, >>> generate a SHA-256, feed this to Chef and converge. >>> >>> There's work underway on Chef to support other checksum types, but it >>> might >>> be helpful regardless for Asterisk to include other checksum types. Would >>> it be a lot of work to add at least SHA-256, if not MD5 as well, to the >>> release process? >>> >>> The build script for asterisk releases are located in repotools[1], so >> adding support should be a matter of just submitting a patch to the tracker. >> >> [1] http://svnview.digium.com/svn/repotools/ >> > > It's pretty trivial to update mkrelease and releaser to create a new > checksum file using sha256sum/md5sum. > > The question is: if we're going to generate three checksums, is it > worthwhile to put them all into a single checksum file? Or do we want three > separate files? > > Going the separate file approach would end up generating 6 files per > release (3 for the release, 3 for the patch), times 3 supported release > branches. Not that it would take up a lot of disk space, but it would be > more stuff to browse through. > > Matt > > -- > Matthew Jordan > Digium, Inc. | Engineering Manager > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > Check us out at: http://digium.com & http://asterisk.org > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
