comment on

hmmmm, amTapi can decipher the CallerID stream. *That* would allow the script to run or not run based on the incoming phone number.

Arg! So many things that I want to add in now. Trying to plan and implement solutions one at a time is going to be frustrating. I can see there always being something on the horizon waiting to be added.

As for making an XS interface, I don't know that I would hold my breath. I am nowhere near that level yet. Getting my script to determine that a number '5' has been pushed on the other end is quite enough challenge right now.

............

You know, after reviewing some of the TAPI documentation, getting perl to see my modem on a win machine will be challenge enough!

Thanks to you and ony other posters I have not already thanked. This is more information than I ever thought I would get.

In reply to Re: Re: Parsing touch tone input? by TacoVendor
in thread Parsing touch tone input? by TacoVendor

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks