Outbound call problem! Unable to handle indication 13

Electricity440 · July 18, 2016, 1:43am

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,

no outbound, only inbound AllStar connections
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

···

Skyler Fennell
amsatnet.info

KDØWHB

electricity440@gmail.com

David_McGough · July 18, 2016, 1:58am

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

Electricity440 · July 18, 2016, 2:30am

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
>
>
>

--
Skyler Fennell
amsatnet.info
KDØWHB
electricity440@gmail.com

Electricity440 · July 18, 2016, 2:59am

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,

no outbound, only inbound AllStar connections

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

–
Skyler Fennell
amsatnet.info

KDØWHB

electricity440@gmail.com

Skyler Fennell
amsatnet.info

KDØWHB

electricity440@gmail.com

Electricity440 · July 18, 2016, 3:24am

A third note, I am able to connect to other AllStar nodes that are not on ports 4569 or 4570 (the ports I use for AllStar link)

···

On Sun, Jul 17, 2016 at 8:59 PM, Skyler F electricity440@gmail.com wrote:

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:

–
Skyler Fennell
amsatnet.info

KDØWHB

electricity440@gmail.com

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,

no outbound, only inbound AllStar connections

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

–
Skyler Fennell
amsatnet.info

KDØWHB

electricity440@gmail.com

Skyler Fennell
amsatnet.info

KDØWHB

electricity440@gmail.com

Ve3ei · July 18, 2016, 10:43am

Do you have the first line in your NAT Firewall rules of srcnat
---- action=masquarade ?

You can do this in firewall-nat in winbox or command line

Eric - ve3ei

···

On 17/07/2016 11:24 PM, Skyler F wrote:

    A third note, I am able to connect to other AllStar
nodes that are not on ports 4569 or 4570 (the ports I use for
AllStar link)

      On Sun, Jul 17, 2016 at 8:59 PM, Skyler
F electricity440@gmail.com
wrote:
          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

                                  >

                                  >

                                  >

–
Skyler
Fennell
amsatnet.info

KD�WHB

electricity440@gmail.com

–
Skyler Fennell
amsatnet.info

KD�WHB

electricity440@gmail.com

–
Skyler Fennell
amsatnet.info

KD�WHB

electricity440@gmail.com




_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

David_McGough · July 18, 2016, 10:46am

Hi Skyler,

It's definitely a NAT problem, based on your description.

However, I'm not a MikroTik guru, I use only Linux (iptables) firewalls
for these applications, which are trivial to setup..But, setting up the
MikroTik should be easy, too.

I know similar MikroTik topics have come up in the past, perhaps someone
else on the list will elaborate?

73, David KB4FXC

···

On Sun, 17 Jul 2016, Skyler F wrote:

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
>> >
>> >
>> >
>>
>>
>
>
> --
> Skyler Fennell
> amsatnet.info
> KDØWHB
> electricity440@gmail.com
>