Another note, If I turn off the port forwarding on the router under the NAT menu, I can now only get outbound connections, however inbound connections don't work.So if I turn my firewall rules off, outbound all the sudden starts working.On Sun, Jul 17, 2016 at 8:30 PM, Skyler F <electricity440@gmail.com> wrote:This is my first time using the MikroTik router, and I don't know what I could have wrong in the outbound NAT of my router. Can anybody give me an idea of where to look in winbox or routerOS to see what is wrong?Skyler--On Sun, Jul 17, 2016 at 7:58 PM, David McGough <kb4fxc@inttek.net> wrote:
Skyler,
Indication 13 is a AST_CONTROL_RADIO_UNKEY message. I think that's just a
side effect of the out-bound connection not getting established properly.
I think you've got a out-bound NAT configuration issue on the MikroTik.
73, David KB4FXC
On Sun, 17 Jul 2016, Skyler F wrote:
> So I try to make an outbound call on my AllStar machine under a mikrotik
> router, and I get "Connection Failed". The /tmp/rpt_extnodes is fine, and
> it is reporting to AllStars nodelist and the stats server. Iax2 show
> registry is good.
>
> When I make an inbound connection to the node, it connects right up,
> however, when I make an outbound conenction, I get this big error on any
> node :
>
> channel.c:2447 ast_indicate_data: Unable to handle indication 13 for
> 'IAX2/173.82.59.253:4569-10526'
>
> The strange thing is that if an initial inbound connection is made, it is
> fine for outbound connections on that particular node number.
>
>
> So,
>
> 1) no outbound, only inbound AllStar connections
> 2) Outbound works to the particular node only if an initial inbound
> connection is made.
>
> This problem just started, and I have no idea what would be causing it. I
> DO have two nodes on the same IP, they are on different ports and I have
> the ports forwarded to the specefic devices respectively.
> 73
> Skyler KD0WHB
>
>
>
--