Benchev wrote:
astcc is such a neat and stable piece that I would hardly dare toto mess with it.
You make it sound like it's anathema to modify it :)
You mean to say PINS are not required, right? Because they are generated upon card creation, whether or not you use them.My idea was 1) you need a PIN=YES because otherwise pins are not generated;
2)you need a PIN because most of the guysuse CALLERIDNUM as cardnumber, and that's open to see. I think it was JP Carballo suggested earlier to authenticate against another variable i.e.
It's nothing new as everyone here knows that clid can be spoofed. I have other reasons not to use clid.One of them is to allow our customers to call from any phone at their disposal. Another is to allow me to use the prefix of the card account number as a code of sorts.
It can denote the geographic area of sale or even the denomination.
Yep. I would suggest however that you change the pin generation routine a bit to NOT use the same prefix as the card number. It may be paranoid of me to do so but I've changed the routines a bit to generate pins with random first digits.Although, PINS are good thing.
3)I think even if you use quiet=5 i.e.(astcc.agi,${CARDNO},${TEMP},5)
a PIN will be expected(if PIN=YES). That's way a soft link won't work
because you need to comment out the pin validation snippet in your
inner .agi and leave it for you "disa" .agi
I agree.
Hope I'm not waisting your time with already know things, but I love to discuss about asterisk :-)
Like everyone else here :) -- JP Carballo http://www.netfone2x.com Bringing the world closer.It might look like I'm doing nothing, but at the cellular level, I'm really quite busy.
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
