[arm-allstar] IAXRPT

[Doug Crompton]

OK, In the original post I missed it was iaxrpt.

Make sure you have the account setup correctly in iaxrpt. The host has to
contain the port if it is not 4569 -  ipaddress:port

Also make sure the passwords match in the account and iax.conf file and are
set in both iax.conf files

Again having the Asterisk client open in a window for the server you are
trying to connect to will tell you if it even got there and if it did any
errors. It is also helpful to have two windows open - the client  for the
server you are connecting from and the client for the server you are
connecting to. Then you can see both ends of the picture.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Sat, Sep 8, 2018 at 1:56 PM "Glenn via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> "Doug Crompton via ARM-allstar" wrote:
> > Glenn,
> >
> >     I am really not understanding what you are saying as it seems you
> > contradict yourself.  You say you can connect to either one or link them
> > together but then go on to say you cannot connect x to y.
> >
> > We need more information about what is happening. You need to check the
> > routes between the servers. To do this go into the client - item 11 from
> > the menu - at the CLI prompt type  rpt lookup node   where node is the
> node
> > of the other server on your LAN you are connecting to. It should show
> > something like this -
> >
> > CLI>rpt lookup 40001
> > Node: 40000, Method:   DNS, Actual: LOCAL, Data:
> > radio at 192.168.0.151:4568/40001,NONE
> >
> > These are fake nodes but it shows that the route to 40001 from 40000 is
> via
> > IP 192.168.0.151 at port 4568. If no port is shown it is the default
> 4569.
> >
> > You need  to do this at BOTH ends looking at the node that end is
> > connecting to. The routing path  should be correct including the port.
> >
> > If that is correct then you need to monitor in the client while you
> connect
> > from the other end. It will give you debug information that would be
> > helpful about the problem.
> >
> > This has been discussed before if your router has hairpin loopback then
> you
> > should not have to define local routing in the [nodes] section of
> rpt.conf
> > but if you are using the loopback method you will need to have port
> > forwarding for each server in your router. Defining node connections to
> > each other locally should always work in either case. In the loopback
> > method the router based on port forwarding rules and the IP routes one
> > local server to the other. When using local routing in Allstar it never
> > goes to the router but instead goes directly to the other server on your
> > LAN.
> >
> > Report back what you find.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Sat, Sep 8, 2018 at 9:50 AM "Glenn via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> > This is what I have...
> > from node 48541
> > glenn*CLI> rpt lookup 47954
> > Node: 48541, Method:   DNS, Actual: LOCAL, Data:
> > radio at 192.168.1.113:4569/47954,NONE
> > Node:  1999, Method:   DNS, Actual: LOCAL, Data:
> > radio at 192.168.1.113:4569/47954,NONE
> > glenn*CLI>
> >
> > from node 47954
> > AllStar1*CLI> rpt lookup 48541
> > Node: 47954, Method:   DNS, Actual: LOCAL, Data:
> > radio at 192.168.1.131:4568/48541,NONE
> > Node:  1999, Method:   DNS, Actual: LOCAL, Data:
> > radio at 192.168.1.131:4568/48541,NONE
> > AllStar1*CLI>
> the windows IAXPRT will connect to node 47954 but will not connect to 48541
>
> Glenn k5cod
>
>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org