<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The CT is when the receiver squelch closes and the time-out timer resets. It is not specifically to do with unkeying the transmitter. You can have a really long hang time and the transmitter will practically never unkey, but you still get CT’s. I don’t think there is a time-out timer for a SIP connection. So the timer that triggers the CT is not there. If, however, you have your SIP users entering a DTMF function to “transmit” maybe you can modify that function so it plays a tone on unkey. Of course, unkey is usually the pound symbol so that might be tricky…<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Ken<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Mike - W5JR [mailto:w5jr.lists@gmail.com] <br><b>Sent:</b> Thursday, December 17, 2015 11:53 PM<br><b>To:</b> Mike M <kf7mbk@w7ara.net><br><b>Cc:</b> app_rpt-users@ohnosec.org<br><b>Subject:</b> Re: [App_rpt-users] SIP CT<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>The stations down link have the usual CTs, but the node the SIP is connected to doesn't. I'm intuiting the workaround is to have an intervening node. I've not implemented this for my connection but sounds like a good test. <br><br>tnx<o:p></o:p></p><div><p class=MsoNormal>Mike / W5JR<o:p></o:p></p></div><div><p class=MsoNormal>Alpharetta GA<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On Dec 17, 2015, at 5:02 PM, Mike M <<a href="mailto:kf7mbk@w7ara.net">kf7mbk@w7ara.net</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal>When you "unkey" from the SIP side, I want a CT to come out on the radio. I can see what you mean about not needing a CT out of the SIP side. But when apt_rpt unkeys the radio, whether from a link or SIP, I would think it should generate a CT on the radio. Whether that's the logic in the code, I don't know.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I'll play around with it tonight, maybe take a look through the code.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><div><p class=MsoNormal><br>Regards,<br>Mike Montalvo, KF7MBK<br>ARA Membership Chair<br><a href="http://www.w7ara.org" target="_blank">www.w7ara.org</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Dec 17, 2015 at 11:22 AM, <<a href="mailto:mike@midnighteng.com" target="_blank">mike@midnighteng.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>Ken your right, no sip ct.<br>Feeling a bit stupid after testing mine that I have not used in years, it does not<br>trip CT either.<br>I 'think' because it does not trip the COR code. It bypasses it. Could be for good<br>reason?<br><br>Echolink connections are full duplex. A requirement of the host.<br>ELink user can key-up and rptr users can converse with him without him ever<br>unkeying until rptr time-out. Same with SIP.<br>I don't feel it's pointless to have a CT at the end of any tx on a repeater.<br><br>But since most just use it for sysop testing and monitoring, no big deal.<br><br>...mike/kb8jnm<br><br>> I don't think SIP has a CT.<br>> SIP connections are full duplex; it's pointless to have an "over" beep.<br>><br>> 73<br>> Ken<br>><br>><br>> -----Original Message-----<br>> From: <a href="mailto:app_rpt-users-bounces@ohnosec.org">app_rpt-users-bounces@ohnosec.org</a><br>> [mailto:<a href="mailto:app_rpt-users-bounces@ohnosec.org">app_rpt-users-bounces@ohnosec.org</a>] On Behalf Of<br>> <a href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a><br>> Sent: Thursday, December 17, 2015 12:00 PM<br>> To: <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a><br>> Subject: App_rpt-users Digest, Vol 82, Issue 39<br>><br>> Send App_rpt-users mailing list submissions to<br>> <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a><br>><br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>> or, via email, send a message with subject or body 'help' to<br>> <a href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a><br>><br>> You can reach the person managing the list at<br>> <a href="mailto:app_rpt-users-owner@ohnosec.org">app_rpt-users-owner@ohnosec.org</a><br>><br>> When replying, please edit your Subject line so it is more specific than<br>> "Re: Contents of App_rpt-users digest..."<br>><br>> _______________________________________________<br>> App_rpt-users mailing list<br>> <a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>> <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>><br>> To unsubscribe from this list please visit<br>> <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the<br>> bottom of the page. Enter your email address and press the "Unsubscribe or edit<br>> options button"<br>> You do not need a password to unsubscribe, you can do it via email confirmation. If<br>> you have trouble unsubscribing, please send a message to the list detailing the<br>> problem.<br>><br><br><br>_______________________________________________<br>App_rpt-users mailing list<br><a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br><br>To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.<o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></blockquote><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>_______________________________________________<br>App_rpt-users mailing list<br><a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br><br>To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. <o:p></o:p></p></div></blockquote></div></body></html>