[App_rpt] 2199 appears to be operational
Looks like AllStar node 2199 is fully operational. Today, I upgraded chan_rtpdir to v 0.5, and tbd (the other end of the link) to version 1.05. While there is some DTMF capability, in theory, I don't have a huge need for this feature. I did discover some issues with connecting to other AllStar nodes, but with a bit of tweaking of rpt.conf, I think I have fixed things up. I also have IAXRpt working (which I've been using to monitor traffic on the Asterisk side of the link). Anyway, if anyone wants to try connecting to AllStar node 2199, give it a try. You should be able to connect, and find yourself connected to the core of the VK national IRLP/Echolink network. There is often traffic (check the AllStar stats page and see for yourself - I fixed that reporting too :) ), as we are also connected to the UK and other parts of the world. Any reports would be appreciated, in case there's something else I've missed. If anyone wants to make a sked, I'll try and connect to your node as well. 73 de VK3JED http://vkradio.com
Tony, I connected to it from node 2010 and it has excellent sounding audio! It was very busy when I connected so I didn't stay connected very long. If someone is talking on the Echolink side does our audio mix with theirs or are we locked out? I'm not sure of thelinkbox is a mixing or one-at-a-time echolink reflector. In app_rpt everything is mixing, but typically echolink is one-at-a-time. Steve WA6ZFT Tony Langdon, VK3JED wrote:
Looks like AllStar node 2199 is fully operational. Today, I upgraded chan_rtpdir to v 0.5, and tbd (the other end of the link) to version 1.05. While there is some DTMF capability, in theory, I don't have a huge need for this feature.
I did discover some issues with connecting to other AllStar nodes, but with a bit of tweaking of rpt.conf, I think I have fixed things up. I also have IAXRpt working (which I've been using to monitor traffic on the Asterisk side of the link).
Anyway, if anyone wants to try connecting to AllStar node 2199, give it a try. You should be able to connect, and find yourself connected to the core of the VK national IRLP/Echolink network. There is often traffic (check the AllStar stats page and see for yourself - I fixed that reporting too :) ), as we are also connected to the UK and other parts of the world.
Any reports would be appreciated, in case there's something else I've missed.
If anyone wants to make a sked, I'll try and connect to your node as well.
73 de VK3JED http://vkradio.com
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
Tony,
I connected to it from node 2010 and it has excellent sounding audio! It was very busy when I connected so I didn't stay connected very long.
If someone is talking on the Echolink side does our audio mix with theirs or are we locked out? I'm not sure of thelinkbox is a mixing or one-at-a-time echolink reflector. In app_rpt everything is mixing, but typically echolink is one-at-a-time.
I'll answer for Tony since he's asleep. Yes thelinkbox mixes active audio sources. It treats all VoIP endpoints as separate streams, mixes the active audio and then sends the audio out. If the output is a radio port then that's it. If the output is another VoIP stream then the audio is encoded using the appropriate codec (currently GSM, ADPCM or uLaw) before being sent back out. Thelinkbox also has packet layer conferencing since it's an extension to thebridge. Thebridge and the linkbox can repack GSM data between Asterisk, EchoLink and IRLP connections so there's no need to decode and then re-encode. Clearly that capability doesn't provide connectivity between GSM Asterisk and ADPCM IRLP. Since Tony is currently using thebridge not thelinkbox there's no mixing at the moment. 73's Skip WB6YMH
At 01:17 AM 8/3/2008, you wrote:
Tony,
I connected to it from node 2010 and it has excellent sounding audio! It was very busy when I connected so I didn't stay connected very long.
Thanks. I have seen the issue that Bill saw, namely the long dropouts. I'm wondering if that's due to the linking protocol used by chan_rtpdir not coping with the long link between the Asterisk and Echolink systems (on opposite sides of the world!). I might see if I can find a way to shorten that hop (e.g. by using a "dummy" conference).
If someone is talking on the Echolink side does our audio mix with theirs or are we locked out? I'm not sure of thelinkbox is a mixing or one-at-a-time echolink reflector. In app_rpt everything is mixing, but typically echolink is one-at-a-time.
Echolink is one at a time. Interestingly, tbd reports the connection as full duplex, so Skip, could a tlb based node run full duplex with Asterisk via my conference? 73 de VK3JED http://vkradio.com
At 01:17 AM 8/3/2008, you wrote:
Tony,
I connected to it from node 2010 and it has excellent sounding audio! It was very busy when I connected so I didn't stay connected very long.
Thanks. I have seen the issue that Bill saw, namely the long dropouts. I'm wondering if that's due to the linking protocol used by chan_rtpdir not coping with the long link between the Asterisk and Echolink systems (on opposite sides of the world!). I might see if I can find a way to shorten that hop (e.g. by using a "dummy" conference).
If someone is talking on the Echolink side does our audio mix with theirs or are we locked out? I'm not sure of thelinkbox is a mixing or one-at-a-time echolink reflector. In app_rpt everything is mixing, but typically echolink is one-at-a-time.
Echolink is one at a time. Interestingly, tbd reports the connection as full duplex, so Skip, could a tlb based node run full duplex with Asterisk via my conference?
Yes if the conference is tbd 1.03 or later and tlb is 0.36 or later. Of course standard Echolink clients that are connected to the conference will only hear the station that "has the floor". tlb clients will hear a mix of everyone that's talking. I haven't tested full duplex with Asterisk, but I'll bet you will to call my bluff! 73's Skip WB6YMH
Asterisk app_rpt runs standard endpoints nodes in full duplex by default. The default config file specifies duplex=2. For bridging nodes, the setup is a little different, as you don't want app_rpt acting like a repeater controller with all the ID's courtesy tones, etc. As long as you say: duplex=0 ; kills courtesy tones, but is half-duplex linktolink=yes ; restores full duplex sematics hangtime=0 ; Sets hangtime to 0 idtime=0 ; kills the ID'er You should see audio going in both directions simultaneously with no mutual exclusivity. Steve WA6ZFT Skip WB6YMH wrote:
At 01:17 AM 8/3/2008, you wrote:
Tony,
I connected to it from node 2010 and it has excellent sounding audio! It was very busy when I connected so I didn't stay connected very long. Thanks. I have seen the issue that Bill saw, namely the long dropouts. I'm wondering if that's due to the linking protocol used by chan_rtpdir not coping with the long link between the Asterisk and Echolink systems (on opposite sides of the world!). I might see if I can find a way to shorten that hop (e.g. by using a "dummy" conference).
If someone is talking on the Echolink side does our audio mix with theirs or are we locked out? I'm not sure of thelinkbox is a mixing or one-at-a-time echolink reflector. In app_rpt everything is mixing, but typically echolink is one-at-a-time. Echolink is one at a time. Interestingly, tbd reports the connection as full duplex, so Skip, could a tlb based node run full duplex with Asterisk via my conference?
Yes if the conference is tbd 1.03 or later and tlb is 0.36 or later. Of course standard Echolink clients that are connected to the conference will only hear the station that "has the floor". tlb clients will hear a mix of everyone that's talking.
I haven't tested full duplex with Asterisk, but I'll bet you will to call my bluff!
73's Skip WB6YMH
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
At 10:52 AM 8/3/2008, you wrote:
duplex=0 ; kills courtesy tones, but is half-duplex linktolink=yes ; restores full duplex sematics hangtime=0 ; Sets hangtime to 0 idtime=0 ; kills the ID'er
You should see audio going in both directions simultaneously with no mutual exclusivity.
I think that's the settings I'm using. Certainly looks familiar. :) 73 de VK3JED http://vkradio.com
At 10:34 AM 8/3/2008, you wrote:
Yes if the conference is tbd 1.03 or later and tlb is 0.36 or later. Of
Which the conference has to be (actually, to use chan_rtpdir 0.5, it has to be tbd 1.05 or later ;) ).
course standard Echolink clients that are connected to the conference will only hear the station that "has the floor". tlb clients will hear a mix of everyone that's talking.
I haven't tested full duplex with Asterisk, but I'll bet you will to call my bluff!
Hmm, looks like I'll have to try tlb on my other IRLP node, as that has full duplex capable hardware. :-D 73 de VK3JED http://vkradio.com
participants (3)
-
Skip WB6YMH -
Stephen Rodgers -
Tony Langdon, VK3JED