[App_rpt-users] chan_tlb - Cross-Talk Issues

Jim Duuuude telesistant at hotmail.com
Tue Dec 7 17:11:38 EST 2010


[In Yoda voice... mmmmm, very peculiar configuration, this is]

I believe the issue is with TLB. I dont think it can deal with more then 1 Asterisk station connecting to it
from the same IP address to the same UDP port. I believe that why it supports multiple "listen" ports.

Try defining 2 UDP ports (in a comma delimited list (or something), I believe) in the tlb.conf
for each node, and have a unique entry for each node to connect to a different UDP port on
the TLB system. I think this may fix your problem.

I really am no expert on TLB things.

JIM WB6NIL


Date: Tue, 7 Dec 2010 15:55:33 -0600
From: kd0eav at clear-sky.net
To: app_rpt-users at qrvc.com
Subject: [App_rpt-users] chan_tlb - Cross-Talk Issues



  


    
  
  
    I've been working on setting up two TLB conferences that I wish to
    bridge over into two Allstar Link nodes ... 

    

    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.

    

    They are currently spread between two servers (and 3 IP
    addresses)...

    

    ____Server 1_________________

    Allstar 27097

    Allstar 27521

    TLB - Echolink *KD0EAV* (attached to 27097)

    

    

    ____Server 2_________________

    TLB - Echolink *MISSOURI* (attached to 27521)

    

    

    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.

    

    

    

    

    ____Server 1 Allstar tlb.conf_______

    [tlb0]

      call=Allstar 27097      ; Call of the app_rpt station

      port=44966              ; Start of UDP port range (this port, port
      + 1)

      astnode=27097           ; app_rpt node associated with this
      instance (for incoming connections)

      context=radio-secure    ; Asterisk context for incoming
      connections

      codec=GSM               ; Default CODEC to be used

      ipaddr=208.110.93.103   ; Bind2IP address

      

      [tlb1]

      call=Allstar 27521      ; Call of the app_rpt station

      port=44968              ; Start of UDP port range (this port, port
      + 1)

      astnode=27521           ; app_rpt node associated with this
      instance (for incoming connections)

      context=radio-secure    ; Asterisk context for incoming
      connections

      codec=GSM               ; Default CODEC to be used

      ipaddr=208.110.93.103   ; Bind2IP address

      

      [nodes]

      1424491 = *KD0EAV*,208.110.93.108,44966

      1452514 = *MISSOURI*,216.229.80.7,44968

    

    

    

    

    ____Server 1 TLB tlb.conf__________

    Bind2IP = 208.110.93.108

      RTP_Port = 44966

      StartupCmd = connect -r -n -f -p 44966 208.110.93.103

    

    

    

    ____Server 2 TLB tlb.conf__________

    Bind2IP = 216.229.80.7

      RTP_Port = 44968

      StartupCmd = connect -r -n -f -p 44968 208.110.93.103

    

    

    

    Thanks for all your work on this!! It held up to quite a lot of
    abuse last night....

    

    73

    

    - Jeremy, KD0EAV

    

  


_______________________________________________
App_rpt-users mailing list
App_rpt-users at qrvc.com
http://qrvc.com/mailman/listinfo/app_rpt-users 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20101207/1614f57d/attachment.html>


More information about the App_rpt-users mailing list