<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
[In Yoda voice... mmmmm, very peculiar configuration, this is]<br><br>I believe the issue is with TLB. I dont think it can deal with more then 1 Asterisk station connecting to it<br>from the same IP address to the same UDP port. I believe that why it supports multiple "listen" ports.<br><br>Try defining 2 UDP ports (in a comma delimited list (or something), I believe) in the tlb.conf<br>for each node, and have a unique entry for each node to connect to a different UDP port on<br>the TLB system. I think this may fix your problem.<br><br>I really am no expert on TLB things.<br><br>JIM WB6NIL<br><br><br><hr id="stopSpelling">Date: Tue, 7 Dec 2010 15:55:33 -0600<br>From: kd0eav@clear-sky.net<br>To: app_rpt-users@qrvc.com<br>Subject: [App_rpt-users] chan_tlb - Cross-Talk Issues<br><br>
<meta http-equiv="Content-Type" content="text/html; charset=unicode">
<meta name="Generator" content="Microsoft SafeHTML">
I've been working on setting up two TLB conferences that I wish to
bridge over into two Allstar Link nodes ... <br>
<br>
I've been successful at attaching both of the conferences to their
two separate Allstar nodes. My intention is to have them run
exclusively of each other - with the ability to bridge the Allstar
nodes together as needed.<br>
<br>
They are currently spread between two servers (and 3 IP
addresses)...<br>
<br>
<u><b>____Server 1_________________</b></u><br>
Allstar 27097<br>
Allstar 27521<br>
TLB - Echolink *KD0EAV* (attached to 27097)<br>
<br>
<br>
<u><b>____Server 2_________________</b></u><br>
TLB - Echolink *MISSOURI* (attached to 27521)<br>
<br>
<br>
The issue is that when I have both 27097 and 27521 on the same
server, ANY traffic from 27097 will appear on the *MISSOURI*
conference (only attached to 27521)... and any traffic on 27521
will appear on *KD0EAV* (only attached to 27097)... even though they
ARE NOT in ANY WAY bridged together. BUT - this is only true for
traffic which is on the AllStar side of things... if somebody
responds to me on the TLB conference it is NOT routed back over. It
only flows one way... FROM Allstar TO TLB... It shows in TLB to be
from the other Asterisk node.<br>
<br>
<br>
<br>
<br>
<u><b>____Server 1 Allstar tlb.conf_______</b></u><br>
<tt>[tlb0]<br>
call=Allstar 27097 ; Call of the app_rpt station<br>
port=44966 ; Start of UDP port range (this port, port
+ 1)<br>
astnode=27097 ; app_rpt node associated with this
instance (for incoming connections)<br>
context=radio-secure ; Asterisk context for incoming
connections<br>
codec=GSM ; Default CODEC to be used<br>
ipaddr=208.110.93.103 ; Bind2IP address<br>
<br>
[tlb1]<br>
call=Allstar 27521 ; Call of the app_rpt station<br>
port=44968 ; Start of UDP port range (this port, port
+ 1)<br>
astnode=27521 ; app_rpt node associated with this
instance (for incoming connections)<br>
context=radio-secure ; Asterisk context for incoming
connections<br>
codec=GSM ; Default CODEC to be used<br>
ipaddr=208.110.93.103 ; Bind2IP address<br>
<br>
[nodes]<br>
1424491 = *KD0EAV*,208.110.93.108,44966<br>
1452514 = *MISSOURI*,216.229.80.7,44968</tt><br>
<br>
<br>
<br>
<br>
<u><b>____Server 1 TLB tlb.conf__________</b></u><br>
<tt>Bind2IP = 208.110.93.108<br>
RTP_Port = 44966<br>
StartupCmd = connect -r -n -f -p 44966 208.110.93.103</tt><br>
<br>
<br>
<br>
<u><b>____Server 2 TLB tlb.conf__________</b></u><br>
<tt>Bind2IP = 216.229.80.7<br>
RTP_Port = 44968<br>
StartupCmd = connect -r -n -f -p 44968 208.110.93.103</tt><br>
<br>
<br>
<br>
Thanks for all your work on this!! It held up to quite a lot of
abuse last night....<br>
<br>
73<br>
<br>
- Jeremy, KD0EAV<br>
<br>
<br>_______________________________________________
App_rpt-users mailing list
App_rpt-users@qrvc.com
http://qrvc.com/mailman/listinfo/app_rpt-users </body>
</html>