Re: [asterisk-users] Gosub behavior change =1.6.0.5 to 1.6.0.6
amit mehta wrote: Hello Users, Is anyone aware about a solution to call incoming number and dictate the files by using Dictate feature of Asterisk used for Medical Transcription industry. I guess nobody will read your email as you: 1. hijacked a thread (http://www.internet-description.com/t/thread-hijacking.html) 2. did not even changed the subject So, most user do not even read your email as they think the subject is about Gosub, not dictate. So I would suggest to try again, writing a new email instead of clicking on reply. regards klaus ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Klaus Darilion klaus.mailingli...@pernau.at writes: What about a config option gototriggersinvalid=yes (default=no) in extensions.conf for users which are using this feature? Please, no more options. There are way too many options already. Since I personally believe the use of the special extensions should be limited as much as possible, I believe Goto and Gosub should not end up in the i extension. I can live with the opposite as well, even if it isn't what I prefer. Just not another option. /Benny ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Tilghman Lesher schrieb: On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote: Barry L. Kline wrote: that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the requested extension wasn't present in the incoming context. Really strange that Goto and Gosub behave different. If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. The problem is, that the old behavior is there since 1.4 and many users use it. Thus, if you change it now you break the dialplan of many users. klaus ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Tilghman Lesher wrote:
On Tuesday 24 February 2009 13:44:25 Barry L. Kline wrote:
Here's one that may be of interest to any upgraders. If you rely on the
behavior of gosub you may want to make note of this change.
I have an incoming call context:
exten = _,n,GoSub(incoming,${EXTEN},1(${EXTEN}));
that is supposed to gosub into the incoming extension at priority 1.
Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the
requested extension wasn't present in the incoming context.
When I upgraded to 1.6.0.6 this behavior changed and I would simply get
an error on the console that a matching extension was not found, and the
dialplan would simply stop. It was easy enough to add:
[incoming]
exten = _,1,Goto(i,1)
to restore the previous behavior (I'm looking at four-digits from a PRI)
which I should probably have done anyway.
I don't know if this is a bug or WAD but just wanted to mention it.
It was a bug. Gosub/Goto should NEVER go to the i extension, unless that
target is explicitly given. The use of the i extension for invalid
extensions is limited to WaitExten/Background.
Why should it be so limited? It's clearly not now, and it's not been
considered a bug - certainly no bug reports or user confusion. Some of
us have used this behaviour for quite a while. It's very useful.
Why change?
sean
___
-- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
On Tue, 2009-02-24 at 16:58 -0600, Tilghman Lesher wrote: If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. While I personally believe it's a bug, it has been in Asterisk for a very long time, and I know from teaching Asterisk training classes that there are *many* *many* people abusing this in their dialplans. I'd be quite hesitant to change this behavior without some very large warning signs. -- Jared Smith Digium, Inc. | Training Manager ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jared Smith wrote: While I personally believe it's a bug, it has been in Asterisk for a very long time, and I know from teaching Asterisk training classes that there are *many* *many* people abusing this in their dialplans. I'd be quite hesitant to change this behavior without some very large warning signs. I think that the appropriate time is during an upgrade to a new version. Even from 1.6.0 to 1.6.1 would be okay, given that the behavior change is documented in the upgrade.txt document. Doing it from a .05 to a .06 release can certainly catch many off-guard. BK -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFJpWAfCFu3bIiwtTARAp1AAJoDgKg1o0UPHg/0uGXesOVMZyP+0wCfXzbY XWUUOuxPwKdWG2xsbEGV2PY= =6+mm -END PGP SIGNATURE- ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Tilghman Lesher schrieb: On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote: Barry L. Kline wrote: that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the requested extension wasn't present in the incoming context. Really strange that Goto and Gosub behave different. If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. FYI: If you take a look at the history of http://www.voip-info.org/wiki/index.php?page=Asterisk+i+extension you will find out that the old behavior is there since at least Nov. 2005, and probably used since then. regards klaus ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
On Wednesday 25 February 2009 09:51:23 Klaus Darilion wrote: Tilghman Lesher schrieb: On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote: Barry L. Kline wrote: that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the requested extension wasn't present in the incoming context. Really strange that Goto and Gosub behave different. If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. FYI: If you take a look at the history of http://www.voip-info.org/wiki/index.php?page=Asterisk+i+extension you will find out that the old behavior is there since at least Nov. 2005, and probably used since then. voip-info.org is best known for being often wrong. -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Tilghman Lesher wrote: On Wednesday 25 February 2009 09:51:23 Klaus Darilion wrote: Tilghman Lesher schrieb: On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote: Barry L. Kline wrote: that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the requested extension wasn't present in the incoming context. Really strange that Goto and Gosub behave different. If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. FYI: If you take a look at the history of http://www.voip-info.org/wiki/index.php?page=Asterisk+i+extension you will find out that the old behavior is there since at least Nov. 2005, and probably used since then. voip-info.org is best known for being often wrong. I think the point being made was that a lot of people thought this was a feature, not a bug. I assume you're asserting the the dev's did not expect this behaviour, even if a large group of users did. That's OK. But there's still the question about why this behaviour is so bad/inconsistent/something that it should be changed. Simply labeling it a bug is just a conclusion. Why is it a bug??? sean ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Tilghman Lesher schrieb: On Wednesday 25 February 2009 09:51:23 Klaus Darilion wrote: Tilghman Lesher schrieb: On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote: Barry L. Kline wrote: that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the requested extension wasn't present in the incoming context. Really strange that Goto and Gosub behave different. If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. FYI: If you take a look at the history of http://www.voip-info.org/wiki/index.php?page=Asterisk+i+extension you will find out that the old behavior is there since at least Nov. 2005, and probably used since then. voip-info.org is best known for being often wrong. voip-info.org is also beeing known as where to find documentation where Asterisk itself lacks of documentation. The problem here is not voip-info, but that the old behavior is there and used since at least Nov 2005. Changing an over 3 years old behavior is not nice. regards klaus ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
On Wednesday 25 February 2009 11:19:08 sean darcy wrote: Tilghman Lesher wrote: On Wednesday 25 February 2009 09:51:23 Klaus Darilion wrote: Tilghman Lesher schrieb: On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote: Barry L. Kline wrote: that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the requested extension wasn't present in the incoming context. Really strange that Goto and Gosub behave different. If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. FYI: If you take a look at the history of http://www.voip-info.org/wiki/index.php?page=Asterisk+i+extension you will find out that the old behavior is there since at least Nov. 2005, and probably used since then. voip-info.org is best known for being often wrong. I think the point being made was that a lot of people thought this was a feature, not a bug. I assume you're asserting the the dev's did not expect this behaviour, even if a large group of users did. That's OK. But there's still the question about why this behaviour is so bad/inconsistent/something that it should be changed. Simply labeling it a bug is just a conclusion. Why is it a bug??? It's a bug, because the i extension has a very limited intended usage, and any additional cases where the i extension is implicitly invoked is therefore a bug. This thread has convinced me not to change Goto in 1.6.0, but I absolutely defend fixing this bug in Gosub, given that I'm the designer of it, and it was never supposed to fail into the i extension. -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Why not expand the usage of the i extension? If not in 1.6.0, then some later 1.6. Call it a feature enhancement. Tilghman Lesher wrote: On Wednesday 25 February 2009 11:19:08 sean darcy wrote: Tilghman Lesher wrote: On Wednesday 25 February 2009 09:51:23 Klaus Darilion wrote: Tilghman Lesher schrieb: On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote: Barry L. Kline wrote: that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the requested extension wasn't present in the incoming context. Really strange that Goto and Gosub behave different. If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. FYI: If you take a look at the history of http://www.voip-info.org/wiki/index.php?page=Asterisk+i+extension you will find out that the old behavior is there since at least Nov. 2005, and probably used since then. voip-info.org is best known for being often wrong. I think the point being made was that a lot of people thought this was a feature, not a bug. I assume you're asserting the the dev's did not expect this behaviour, even if a large group of users did. That's OK. But there's still the question about why this behaviour is so bad/inconsistent/something that it should be changed. Simply labeling it a bug is just a conclusion. Why is it a bug??? It's a bug, because the i extension has a very limited intended usage, and any additional cases where the i extension is implicitly invoked is therefore a bug. This thread has convinced me not to change Goto in 1.6.0, but I absolutely defend fixing this bug in Gosub, given that I'm the designer of it, and it was never supposed to fail into the i extension. -- Eric Wieling * Asteria Solutions Group * Huntsville, AL Call centers * IVRs * Enterprise PBXs * Conferencing applications 256-705-0277 * http://www.asteriasgi.com/ * sa...@asteriasgi.com ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Tilghman Lesher wrote: . ... but I absolutely defend fixing this bug in Gosub, given that I'm the designer of it, and it was never supposed to fail into the i extension. Wow. sean ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Tilghman Lesher wrote: On Wednesday 25 February 2009 11:19:08 sean darcy wrote: Tilghman Lesher wrote: On Wednesday 25 February 2009 09:51:23 Klaus Darilion wrote: Tilghman Lesher schrieb: On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote: Barry L. Kline wrote: that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the requested extension wasn't present in the incoming context. Really strange that Goto and Gosub behave different. If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. FYI: If you take a look at the history of http://www.voip-info.org/wiki/index.php?page=Asterisk+i+extension you will find out that the old behavior is there since at least Nov. 2005, and probably used since then. voip-info.org is best known for being often wrong. I think the point being made was that a lot of people thought this was a feature, not a bug. I assume you're asserting the the dev's did not expect this behaviour, even if a large group of users did. That's OK. But there's still the question about why this behaviour is so bad/inconsistent/something that it should be changed. Simply labeling it a bug is just a conclusion. Why is it a bug??? It's a bug, because the i extension has a very limited intended usage, and any additional cases where the i extension is implicitly invoked is therefore a bug. This thread has convinced me not to change Goto in 1.6.0, but I absolutely defend fixing this bug in Gosub, given that I'm the designer of it, and it was never supposed to fail into the i extension. What about a config option gototriggersinvalid=yes (default=no) in extensions.conf for users which are using this feature? regards klaus ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Hello Users, Is anyone aware about a solution to call incoming number and dictate the files by using Dictate feature of Asterisk used for Medical Transcription industry. Looking forward for help. Thanks, Amit ___ -- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
Barry L. Kline wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's one that may be of interest to any upgraders. If you rely on the
behavior of gosub you may want to make note of this change.
I have an incoming call context:
exten = _,n,GoSub(incoming,${EXTEN},1(${EXTEN}));
that is supposed to gosub into the incoming extension at priority 1.
Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the
requested extension wasn't present in the incoming context.
When I upgraded to 1.6.0.6 this behavior changed and I would simply get
an error on the console that a matching extension was not found, and the
dialplan would simply stop. It was easy enough to add:
[incoming]
exten = _,1,Goto(i,1)
to restore the previous behavior (I'm looking at four-digits from a PRI)
which I should probably have done anyway.
I don't know if this is a bug or WAD but just wanted to mention it.
That's probably related to a bug I reported. The i extension did match
when the Gosub was executed normally, but now when the Gosub was
executed from within a macro. I reported that they should fix the macro
case - obviously they implemented the bug also in the normal case.
Nevertheless you can workaround it by using e.g. _[0-9]. instead of i
Really strange that Goto and Gosub behave different.
regards
klaus
___
-- 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] Gosub behavior change =1.6.0.5 to 1.6.0.6
On Tuesday 24 February 2009 13:44:25 Barry L. Kline wrote:
Here's one that may be of interest to any upgraders. If you rely on the
behavior of gosub you may want to make note of this change.
I have an incoming call context:
exten = _,n,GoSub(incoming,${EXTEN},1(${EXTEN}));
that is supposed to gosub into the incoming extension at priority 1.
Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the
requested extension wasn't present in the incoming context.
When I upgraded to 1.6.0.6 this behavior changed and I would simply get
an error on the console that a matching extension was not found, and the
dialplan would simply stop. It was easy enough to add:
[incoming]
exten = _,1,Goto(i,1)
to restore the previous behavior (I'm looking at four-digits from a PRI)
which I should probably have done anyway.
I don't know if this is a bug or WAD but just wanted to mention it.
It was a bug. Gosub/Goto should NEVER go to the i extension, unless that
target is explicitly given. The use of the i extension for invalid
extensions is limited to WaitExten/Background.
--
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] Gosub behavior change =1.6.0.5 to 1.6.0.6
On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote: Barry L. Kline wrote: that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the incoming,i,1 priority if the requested extension wasn't present in the incoming context. Really strange that Goto and Gosub behave different. If Goto behaves that way, that's a bug. As stated in a prior email, the i extension should only be implicitly invoked when waiting for a new extension and the typed extension does not match anything. -- 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
