<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>With Zopier you can use the *99 feature for PTT if you have you extension configure correctly for it.</div><div>I have discovered this works very nicely! Also I use text Aloud for text to speech conversion with very nice sounding voices available and then use audacity to customize the voice, save it in u law format then use sox to convert it to GSM format!</div><div>I do believe Audacity has a GSM format but have not used it. I have several 7330 controllers I do custom voice libraries for and they require the ulaw format<br><br>Eric</div><div><br></div><div>N7JYS</div><div><br>Sent from my iPhone</div><div><br>On Sep 8, 2015, at 3:17 AM, Mike / W5JR <<a href="mailto:w5jr.lists@gmail.com">w5jr.lists@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>Yep, all of the multiple nodes on the ACID server are working as well. Sure wish Zoiper had a PTT like functionality, but it's "mic mute" for now. </div><div><br></div><div>And I've begun a few custom voice responses versus the "node xxxxx connected" approach. I've found a fairly decent female TTS voice/program to make acceptable WAV files. She even says "dubbya" correctly. </div><div><br></div><div>I've shut the computer down for the night. I'll share the name of it tomorrow. It's not the super quality of some of the online translator voices, but she isn't robotic, either. I think it is eSpeak, using the Zira voice (Windows 10?). <br><br>tnx<div>Mike / W5JR</div><div>Alpharetta GA</div></div><div><br>On Sep 8, 2015, at 1:12 AM, Doug Crompton <<a href="mailto:doug@crompton.com">doug@crompton.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr"><font style="" color="#000000" face="Tahoma,sans-serif">Glad you got it going.<br id="FontBreak"></font><br><b><font style="font-size:16pt;" size="4">73 Doug</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">WA3DSP</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4"><a href="http://www.crompton.com/hamradio">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div><hr id="stopSpelling">From: <a href="mailto:w5jr.lists@gmail.com">w5jr.lists@gmail.com</a><br>Date: Mon, 7 Sep 2015 23:29:29 -0400<br>To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>Subject: Re: [arm-allstar] Zoiper & BBB<br><br><div>Ok, all better now. </div><div><br></div><div>Unbeknownst to me, one "taps" the "node number" at the top of the app to select the profile. </div><div><br></div><div>My "working" node was the first entry in the profile list. It always worked since it was selected by default. Removing it placed the previously non-working profile at the top of the list and it began working. Adding the first profile back in saw a "failure" when I keyed in that node number on the keypad with the wrong profile. That's when I discovered the "tap to change profile" sequence. </div><div><br></div><div>Both work as expected, now. And I'm pretty sure I can make the ACID PC work as well, now. </div><div><br></div><div>Learned new stuff today (after pulling out what little hair was left). </div><div><br>tnx<div>Mike / W5JR</div><div>Alpharetta GA</div></div><div><br>On Sep 7, 2015, at 10:59 PM, Mike / W5JR <<a href="mailto:w5jr.lists@gmail.com">w5jr.lists@gmail.com</a>> wrote:<br><br></div><blockquote><div><div>Ok, client open on both of the BBB's and the ACID box. </div><div><br></div><div>On both BBB's , the registration request comes through and is authenticated. </div><div><br></div><div>On the working BBB, "accepting AUTHENTICATED call....." and associated data happens. On the non-working BBB, no messages whatsoever for the connect attempt. Me thinks the issue is on the Zoiper end. </div><div><br></div><div>Testing to continue. <br><br>tnx<div>Mike / W5JR</div><div>Alpharetta GA</div></div><div><br>On Sep 7, 2015, at 10:08 PM, Mike / W5JR <<a href="mailto:w5jr.lists@gmail.com">w5jr.lists@gmail.com</a>> wrote:<br><br></div><blockquote><div><div>Good idea on opening the client. Doing that now. <br><br>tnx<div>Mike / W5JR</div><div>Alpharetta GA</div></div><div><br>On Sep 7, 2015, at 10:01 PM, Doug Crompton <<a href="mailto:doug@crompton.com">doug@crompton.com</a>> wrote:<br><br></div><blockquote><div>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr"><font style="" color="#000000" face="Tahoma,sans-serif">I doubt the TOS codes have anything to do with it. It depends on your router and also would not have anything to do with connection but rather data flow after connection.<br><br><a href="http://www.wildpackets.com/resources/compendium/tcp_ip/ip_tos" target="_blank">http://www.wildpackets.com/resources/compendium/tcp_ip/ip_tos</a><br><br>0xbc is critical, low delay, high thruput, high reliability. <br id="ecxFontBreak"></font><br><font style="" face="Tahoma,sans-serif">Change it to 0xbc and see what happens it should not matter. </font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">You cited a Zopier error. What about at the Allstar end? Go into the client - asterisk -rvvv and see what messages you get a that end. If its remote just ssh in.</font><font style="" face="Tahoma,sans-serif"><br></font><br><b><font style="font-size:16pt;" size="4">73 Doug</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">WA3DSP</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4"><a href="http://www.crompton.com/hamradio" target="_blank">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div>> From: <a href="mailto:w5jr.lists@gmail.com">w5jr.lists@gmail.com</a><br>> Date: Mon, 7 Sep 2015 21:16:39 -0400<br>> To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>> Subject: [arm-allstar] Zoiper & BBB<br>> <br>> Hey, Zoiper on iPhone users. Trying to resolve why one of my BBB packages works great and the other does not. <br>> <br>> I've made the iax and extensions conf files identical between the two, using the respective node numbers with the exception of the "tos" value in the iax general stanza. The working connection is tos=0xBC and the non-working one is tos=0x1E. No clue what this refers to. Yes, I full reboot the non-working one after making changes. <br>> <br>> The iPhone app registers successfully on both. The working one spits the "node xxxxx connected" speech as scripted in the example found here on this web site. <br>> <br>> On the non-working one (but again registers successfully), Zoiper returns "Error no such context/extension (3)". <br>> <br>> These are at two different physical locations with unique IP, both behind NAT routers. The nodes are working correctly as for in and out connections. I'm able to ssh into both. The Zoiper working unit is local to me, so I can connect either via the 192.xxx address or via the public IP :4564, and from the LTE network. Both units are off the 4569 port as I have an ACID box on that port (which doesn't connect, either, but registers successfully). <br>> <br>> Thinking I'm overlooking the obvious. <br>> <br>> tnx<br>> Mike / W5JR<br>> Alpharetta GA<br>> _______________________________________________<br>> <br>> arm-allstar mailing list<br>> <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>> <a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>> <br>> Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" target="_blank">http://hamvoip.org</a><br>> <br></div> </div>
</div></blockquote><blockquote><div><span>_______________________________________________</span><br><span></span><br><span>arm-allstar mailing list</span><br><span><a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a></span><br><span><a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a></span><br><span></span><br><span>Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" target="_blank">http://hamvoip.org</a></span></div></blockquote></div></blockquote></div></blockquote><br>_______________________________________________
arm-allstar mailing list
<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org">http://hamvoip.org</a></div> </div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span></span><br><span>arm-allstar mailing list</span><br><span><a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a></span><br><span><a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a></span><br><span></span><br><span>Visit the BBB and RPi2 web page - <a href="http://hamvoip.org">http://hamvoip.org</a></span></div></blockquote></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span></span><br><span>arm-allstar mailing list</span><br><span><a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a></span><br><span><a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a></span><br><span></span><br><span>Visit the BBB and RPi2 web page - <a href="http://hamvoip.org">http://hamvoip.org</a></span></div></blockquote></body></html>