[Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

Pisac pisacc at gmail.com
Tue Jan 17 14:35:43 MST 2006


I was never read documentation about that substring functionality. I was
(once upon a time) just thinking about how can I extract first 3 digits
from CALLERIDNUM, and what appears logical to me is that I should try
CALLERIDNUM::3

Guess what, it's worked! That was the first idea that come in to my
mind, and it really worked, and (of course) I believed that it is the
way it should work.

By the way, I understand your point of view, but, when I'm making a new
dialplan (IVR system) I don't think about what is documented and what
isn't. I just wrote dialplan and try it, and if it working like it
should, then I switch my mind to other problems.

By the way, autofallthrough is also needless & problematic change :-).
You should set it as default =NO, and only if in extensions.conf exist
"autofallthrough=yes" it should work. I had problems with this feature,
that appears to me as a bug. I still think that is a bug: unexpected
disconnecting IVR if I press any digit during playing announce (not
after announce) and only if digittimeout=0. Hmmmm?




----- Original Message ----- 
From: "Kevin P. Fleming" <kpfleming at digium.com>

> It was _never_ documented that you could skip a numeric parameter for
> the substring functionality and expect it to work properly. If it did,
> you got lucky. When it stopped, you got unlucky.
>
> This was not a 'needless & problematic' change, it was not a change at
> all, for people who followed the documentation.




More information about the asterisk-users mailing list