[asterisk-users] GotoIfTime problem - possible bug
Hi, I'm currently doing some testing against asterisk 1.6.1.7-rc2 (keep meaning to upgrade) and am having a problem with the GotoIfTime dial plan function. The asterisk book says that day of week field can include the ampersand () to combine multiple days / day ranges but this gives me an error. For example monwed gives the error (in the asterisk console): [Nov 23 18:04:27] WARNING[11387]: pbx.c:6249 get_range: Invalid day of week 'monwed', assuming none Does anyone else have experience of this problem? Are there any patches / newer versions to get around this? Thanks in advance. Regards, Dr. Nic Colledge ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] GotoIfTime problem - possible bug
On Monday 23 November 2009 12:11:02 pm Nic Colledge wrote: I'm currently doing some testing against asterisk 1.6.1.7-rc2 (keep meaning to upgrade) and am having a problem with the GotoIfTime dial plan function. The asterisk book says that day of week field can include the ampersand () to combine multiple days / day ranges but this gives me an error. For example monwed gives the error (in the asterisk console): [Nov 23 18:04:27] WARNING[11387]: pbx.c:6249 get_range: Invalid day of week 'monwed', assuming none Does anyone else have experience of this problem? Are there any patches / newer versions to get around this? That was an error on my part, when I helped review the book prior to publication. (I was incidentally thinking of the arguments to the CUT() function.) However, given that it was a good idea, it has been implemented in the forthcoming 1.6.2 release, currently in release candidate status. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] GotoIfTime problem - possible bug
On Mon, Nov 23, 2009 at 1:11 PM, Nic Colledge n...@njcolledge.net wrote: I’m currently doing some testing against asterisk 1.6.1.7-rc2 (keep meaning to upgrade) and am having a problem with the GotoIfTime dial plan function. The asterisk book says that day of week field can include the ampersand () to combine multiple days / day ranges but this gives me an error. For example monwed gives the error (in the asterisk console): [Nov 23 18:04:27] WARNING[11387]: pbx.c:6249 get_range: Invalid day of week 'monwed', assuming none I use mon-fri all the time, but I've never tried to grab non-contiguous days before. Have you tried '|', as in the shift of backslash, or some people say pipe? I'm not sure I've ever actually seen documentation that says multiple non-contiguous days is valid syntax. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] GotoIfTime problem - possible bug
Thanks very much, I'll fire up 1.6.2 and see how I go. Nic. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tilghman Lesher Sent: 23 November 2009 18:20 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] GotoIfTime problem - possible bug On Monday 23 November 2009 12:11:02 pm Nic Colledge wrote: I'm currently doing some testing against asterisk 1.6.1.7-rc2 (keep meaning to upgrade) and am having a problem with the GotoIfTime dial plan function. The asterisk book says that day of week field can include the ampersand () to combine multiple days / day ranges but this gives me an error. For example monwed gives the error (in the asterisk console): [Nov 23 18:04:27] WARNING[11387]: pbx.c:6249 get_range: Invalid day of week 'monwed', assuming none Does anyone else have experience of this problem? Are there any patches / newer versions to get around this? That was an error on my part, when I helped review the book prior to publication. (I was incidentally thinking of the arguments to the CUT() function.) However, given that it was a good idea, it has been implemented in the forthcoming 1.6.2 release, currently in release candidate status. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
