[App_rpt-users] Curious messages

Fri May 22 01:41:24 UTC 2009

On May 18, 2009, at 9:11 AM, <hwstar at rodgers.sdcoxmail.com> <hwstar at rodgers.sdcoxmail.com 
 > wrote:

>>
>> From: Randy Hammock <rhammock at ca.rr.com>
>> Date: 2009/05/18 Mon AM 08:50:16 PDT
>> To: app_rpt-users at qrvc.com
>> Subject: [App_rpt-users] Curious messages
>>
>> Have not loaded chan_irlp 0.27 yet so (knowing it is probably a one
>> change from from 0.26 to 0.27 (irlp message handler), I observed the
>> following string of NOTICE messages on the asterisk CLI when I
>> disconnected from reflector 9250:
>>
>> app-rpt*CLI> rpt fun 2036 *149250
>> [May 18 08:24:25] WARNING[23843]: file.c:1205 waitstream_core:
>> Unexpected control subclass '13'
>> [May 18 08:24:25] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:27] WARNING[23877]: file.c:1205 waitstream_core:
>> Unexpected control subclass '13'
>> [May 18 08:24:29] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:30] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:33] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:36] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:38] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:40] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:43] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:45] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:49] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:50] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:53] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:57] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:24:58] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:25:01] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> [May 18 08:25:04] NOTICE[1114]: chan_irlp.c:1125 irlp_reader: irlp
>> node attempted connect from 24.234.4.194 with no node info
>> app-rpt*CLI>
>>
>>
>> -- This message was NOT sent by an iPhone or Blackberry
>> Randy Hammock KC6HUR
>> http://kc6hur.net/~rhammock/
>> http://irlp.kc6hur.net/
>> If there are no horses in heaven, then when I die, I want to go where
>> they went.
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at qrvc.com
>> http://qrvc.com/mailman/listinfo/app_rpt-users
>>
>
> We are aware of this. It seems either we don't know the "secret  
> handshake" to properly say "bye" to a reflector, or it is SOP for  
> the reflector to continue sending stuff after a disconnect. We're  
> not quite sure why refectors do this.
> It's irritating because, of the way the IRLP scripts are coded this  
> can cause false disconnects if someone disconnects from a reflector,  
> and then rapidly connects to something else.

Steve, Jim,

IRLP is pretty crude about how it does the disconnect from reflectors.  
It merely kills the ispeaker and imike processes so that there is no  
longer anything to receive/send packets from/to the reflector. I guess  
something eventually times out. This is the only thing it can do since  
there is no TCP command channel between nodes and reflectors.

Normal node to node connections disconnect by sending a "disconnect"  
command across the TCP command channel (fifosend).

Not sure what can be done fix this. Since reflectors are receive from  
one, send to many type systems. They literally use firewall rules to  
control which node is the talker and blocks the rest from coming in.  
As there is no TCP channel and the UDP port is blocked if someone else  
is sending, there is no way to a disconnect message in otherwise.

-- This message was NOT sent by an iPhone or Blackberry
Randy Hammock KC6HUR
http://kc6hur.net/~rhammock/
http://irlp.kc6hur.net/
If there are no horses in heaven, then when I die, I want to go where  
they went.