Test A ECHO-TEST NODE 48230 for me ?

I have framed-up a stand alone echo-test / parrot type node on 48230

Being only framed up, it has much work to be completed on it. More than just window dressing.

I wanted it to function on a VPS node and to be able to operate simply on the connect string without

any dtmf required. Since there would be no way of knowing if your audio levels are good enough to run dtmf.

I need to adjust some timers and such. And I may need to limit both 1 connect at a time and a 5 min connection timer in the future (as it appears to me now). giving anyone a chance to use without interference. I may in the future, make a drop box to pick-up the audio file for additional analytic on www.29993.link (work in progress)

So, that's it, just connect to 48230, listen for the 'poorly recorded' prompts (LOL), and help me find a bug ?

Perhaps someone can help me with better menu prompts ?

Work in progress, it will get better. Please let me know what you think or how to improve it.

I have a full duplex latency test destined for the next node on my list.

But I hope to keep these 'testing' node numbers permanent tools at your disposal 24/7.

In doing this I found a lot of errors in the default config modules.conf of deb9 install (more on this later).

But this is the point of playing around at this point for me. 'TESTing', Getting back in practice of the asterisk/app_rpt code with a few useful trivial experiments.

73,

...mike/kb8jnm