[App_rpt-users] SIP CT
Stacy
kg7qin at arrl.net
Fri Dec 18 19:35:53 UTC 2015
The processing in app_rpt is split into a couple of sections. It can be
hard to follow if you are just doing a casual look through the code.
You either need Jim's help, or just add a bunch of debugging stuff into
it to follow the flow/execution of the code.
-Stacy
KG7QIN
On 12/18/2015 06:35 AM, Mike M wrote:
> I was looking at the code last night for exactly that.. I found where
> the COP 6 command is processed. But as you said, unkey is # and I
> couldn't even find where that is processed. I didn't look super hard
> as recompinling on the BBB is stupid slow and I just didn't want to
> spend the time.
>
> I did have the idea of creating a pseudo node to come in with the sip
> connection that then connects to the radio node as Mike mentioned. I
> think then I could have a CT out the radio.
>
> Thanks for the help everyone. For now I'll deal..
>
>
> Regards,
> Mike Montalvo, KF7MBK
> ARA Membership Chair
> www.w7ara.org <http://www.w7ara.org>
>
>
>
>
>
>
> On Fri, Dec 18, 2015 at 7:18 AM, Ken <ke2n at cs.com
> <mailto:ke2n at cs.com>> wrote:
>
> 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…
>
> Ken
>
> *From:*Mike - W5JR [mailto:w5jr.lists at gmail.com
> <mailto:w5jr.lists at gmail.com>]
> *Sent:* Thursday, December 17, 2015 11:53 PM
> *To:* Mike M <kf7mbk at w7ara.net <mailto:kf7mbk at w7ara.net>>
> *Cc:* app_rpt-users at ohnosec.org <mailto:app_rpt-users at ohnosec.org>
> *Subject:* Re: [App_rpt-users] SIP CT
>
> 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.
>
> tnx
>
> Mike / W5JR
>
> Alpharetta GA
>
>
> On Dec 17, 2015, at 5:02 PM, Mike M <kf7mbk at w7ara.net
> <mailto:kf7mbk at w7ara.net>> wrote:
>
> 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.
>
> I'll play around with it tonight, maybe take a look through
> the code.
>
>
>
> Regards,
> Mike Montalvo, KF7MBK
> ARA Membership Chair
> www.w7ara.org <http://www.w7ara.org>
>
> On Thu, Dec 17, 2015 at 11:22 AM, <mike at midnighteng.com
> <mailto:mike at midnighteng.com>> wrote:
>
> Ken your right, no sip ct.
> Feeling a bit stupid after testing mine that I have not
> used in years, it does not
> trip CT either.
> I 'think' because it does not trip the COR code. It
> bypasses it. Could be for good
> reason?
>
> Echolink connections are full duplex. A requirement of the
> host.
> ELink user can key-up and rptr users can converse with him
> without him ever
> unkeying until rptr time-out. Same with SIP.
> I don't feel it's pointless to have a CT at the end of any
> tx on a repeater.
>
> But since most just use it for sysop testing and
> monitoring, no big deal.
>
> ...mike/kb8jnm
>
> > I don't think SIP has a CT.
> > SIP connections are full duplex; it's pointless to have
> an "over" beep.
> >
> > 73
> > Ken
> >
> >
> > -----Original Message-----
> > From: app_rpt-users-bounces at ohnosec.org
> <mailto:app_rpt-users-bounces at ohnosec.org>
> > [mailto:app_rpt-users-bounces at ohnosec.org
> <mailto:app_rpt-users-bounces at ohnosec.org>] On Behalf Of
> > app_rpt-users-request at ohnosec.org
> <mailto:app_rpt-users-request at ohnosec.org>
> > Sent: Thursday, December 17, 2015 12:00 PM
> > To: app_rpt-users at ohnosec.org
> <mailto:app_rpt-users at ohnosec.org>
> > Subject: App_rpt-users Digest, Vol 82, Issue 39
> >
> > Send App_rpt-users mailing list submissions to
> > app_rpt-users at ohnosec.org <mailto:app_rpt-users at ohnosec.org>
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> > or, via email, send a message with subject or body 'help' to
> > app_rpt-users-request at ohnosec.org
> <mailto:app_rpt-users-request at ohnosec.org>
> >
> > You can reach the person managing the list at
> > app_rpt-users-owner at ohnosec.org
> <mailto:app_rpt-users-owner at ohnosec.org>
> >
> > When replying, please edit your Subject line so it is
> more specific than
> > "Re: Contents of App_rpt-users digest..."
> >
> > _______________________________________________
> > App_rpt-users mailing list
> > App_rpt-users at ohnosec.org <mailto:App_rpt-users at ohnosec.org>
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> >
> > To unsubscribe from this list please visit
> >
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> and scroll down to the
> > bottom of the page. Enter your email address and press
> the "Unsubscribe or edit
> > options button"
> > 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.
> >
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org <mailto:App_rpt-users at ohnosec.org>
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> and scroll down to the bottom of the page. Enter your
> email address and press the "Unsubscribe or edit options
> button"
> 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.
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org <mailto:App_rpt-users at ohnosec.org>
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and
> scroll down to the bottom of the page. Enter your email
> address and press the "Unsubscribe or edit options button"
> 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.
>
>
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20151218/023e4378/attachment.html>
More information about the App_rpt-users
mailing list