[App_rpt-users] one-way key-up delay
telesistant at hotmail.com
Fri Dec 10 12:26:39 EST 2010
Oh the 2 nodes that have the "delay", try starring Asterisk manually
(first by doing a 'service asterisk stop' then 'asterisk -vvvvc').
The system is "running" when you get the CLI> prompt.
Does it hang for a little bit before it gives you that prompt. If so,
I think I may know what the problem is.
> From: ke2n at cs.com
> To: app_rpt-users at qrvc.com
> Date: Fri, 10 Dec 2010 09:37:17 -0500
> Subject: [App_rpt-users] one-way key-up delay
> My system has 3 PCs, two of them have "private" nodes (node number <2000 not
> registering with the Allstar address server).
> These private nodes are half-duplex or simplex links (duplex=1 in rpt.conf)
> - they are connected to transceivers (and use DSP squelch/ctcss just like
> the main node). Everything is connected together by gigabit Ethernet behind
> a common router.
> When I key up the "public" node, the other linked nodes start transmitting
> in a fraction of a second. But, when I transmit into one of the "private"
> nodes, from a cold start, it takes 3+ seconds before the main node starts
> transmitting. Other than the very first fraction of a second, no audio is
> lost - it is just delayed. Once things are going, the time delay largely
> disappears (i.e., private nodes are now keying up during the hang-time of
> the public node).
> What is causing the long startup time? I can key up, say my callsign and go
> back to receive, before the public node has even started to transmit.
> At the moment, the nodes are running versions 267 and 266. Each of the
> [nodes] stanzas include the local IP addresses of the "other" nodes in
> addition to its own. If it makes any difference - the connections were made
> *from* the public node *to* the private node.
> App_rpt-users mailing list
> App_rpt-users at qrvc.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the App_rpt-users