Re: [App_rpt-users] Error Message When Attempting to Connect to my hub
David there is a lot there but, do you by chance update via webmin ? if so, or even in any case, you might just do a update and recompile and see where that leaves you. Also, when you are trying to connect out, to outside node would that be a internal to a node on other server behind your nat or external allstar outside your nat. Do you have correct "port forwarding" to static addresses even if managed by router by mac id etc ? Would need it at "cable modem/router" and a external router if you are using one. One last thing... did you just switch to comcasts new dual wi-fi modem ? Perhaps someone else will nail it but I can't see it from what is stated. ...mike/kb8jnm
-------- Original Message -------- Subject: Re: [App_rpt-users] Error Message When Attempting to Connect to my hub From: "David Dean K0PWO" <david@k0pwo.com> Date: Sun, December 28, 2014 12:00 pm To: "'Jim Duuuude'" <telesistant@hotmail.com>, "'Allstar app_rpt-users Group'" <app_rpt-users@ohnosec.org>
This morning I followed the advice given by several members on the list. I added in the nodes section of both system
40968 = radio@192.168.20.1/40963,NONE <mailto:radio@192.168.20.1/40963,NONE> on the hub box
41488 = radio@192.168.20.1/41488,NONE <mailto:radio@192.168.20.1/41488,NONE> on the repeater box
And I still get connection failed error messages
Some back ground on what I have
* Comcast internet
* The Comcast supplied modem/router is bridged for modem gateway only
* ASUS RT-AC68U Router which feeds a Cisco Switch which both boxes are currently plugged into
* Node 41488 is my hub node and has port forwarding for port 4572 which it is assigned and configured
* NODE 40968 is my repeater node and port forwarding for port 4569 which it is assigned and configured
* Both machines for the moment have ssh of 222 (default) set
* 41488 (my hub) is using static ip (on my LAN) of 192.168.20.235
* 40968 (my repeater) is using static ip (on my LAN) of 192.168.20.243
The repeater was working fine up until about a month ago when It quit connecting to any nodes.
This morning I reset my router and reconfigured anything – no change
This morning I reformatted my repeater box and reconfigured using the Allstar Portal – no change
When I attempt to connect my repeater to my hub, which is on the same LAN with the node settings added that are listed above I get this error message on the CLI
[Dec 28 08:37:53] WARNING[2500]: chan_iax2.c:4328 handle_call_token: Address 192 .168.20.243 failed CallToken hash inspection
[Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_token: Address 192 .168.20.243 failed CallToken hash inspection
[Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_token: Address 192 .168.20.243 failed CallToken hash inspection
K0PWO_Hub*CLI> [Dec 28 08:37:53] WARNING[2500]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection
K0PWO_Hub*CLI> [Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection
No such command '[Dec 28 08:37:53] WARNING[2500]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands)
No such command '[Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands)
K0PWO_Hub*CLI> [Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection[Dec 28 08:37:53] WAR NING[2500]: chan_iax2.c:4328 handle_call_token: Address 192.168.20.243 failed Ca llToken hash inspection
K0PWO_Hub*CLI> [Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection
No such command '[Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection[Dec 28 08:37:53] W ARNING[2500]: chan_iax2.c:4328 handle_call_token: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands)
No such command '[Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands)
K0PWO_Hub*CLI> [Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspectionexit
No such command '[Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspectionexit' (type 'help [ Dec 28' for other possible commands)
Once again, anybody have any ideas on what is wrong?
Thank you for any help provided.
David<hr>_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users 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.
on the hub box put 40968 = radio@192.168.20.243:4569/40968,NONE on the repeater box put 41488 = radio@192.168.20.235:4572/41488,NONE Don't forget to make sure your iax.conf has the appropriate changed "bindport" to match the above. reboot your router. reboot both systems. After a few minutes, it should work. Chuck On Sun, Dec 28, 2014 at 11:28 AM, <mike@midnighteng.com> wrote:
David there is a lot there but,
do you by chance update via webmin ?
if so, or even in any case, you might just do a update and recompile and see where that leaves you.
Also, when you are trying to connect out, to outside node would that be a internal to a node on other server behind your nat or external allstar outside your nat.
Do you have correct "port forwarding" to static addresses even if managed by router by mac id etc ? Would need it at "cable modem/router" and a external router if you are using one.
One last thing... did you just switch to comcasts new dual wi-fi modem ?
Perhaps someone else will nail it but I can't see it from what is stated.
...mike/kb8jnm
-------- Original Message -------- Subject: Re: [App_rpt-users] Error Message When Attempting to Connect to my hub From: "David Dean K0PWO" <david@k0pwo.com> Date: Sun, December 28, 2014 12:00 pm To: "'Jim Duuuude'" <telesistant@hotmail.com>, "'Allstar app_rpt-users Group'" <app_rpt-users@ohnosec.org>
This morning I followed the advice given by several members on the list. I added in the nodes section of both system
40968 = radio@192.168.20.1/40963,NONE <mailto:radio@192.168.20.1/40963,NONE> on the hub box
41488 = radio@192.168.20.1/41488,NONE <mailto:radio@192.168.20.1/41488,NONE> on the repeater box
And I still get connection failed error messages
Some back ground on what I have
* Comcast internet
* The Comcast supplied modem/router is bridged for modem gateway only
* ASUS RT-AC68U Router which feeds a Cisco Switch which both boxes are currently plugged into
* Node 41488 is my hub node and has port forwarding for port 4572 which it is assigned and configured
* NODE 40968 is my repeater node and port forwarding for port 4569 which it is assigned and configured
* Both machines for the moment have ssh of 222 (default) set
* 41488 (my hub) is using static ip (on my LAN) of 192.168.20.235
* 40968 (my repeater) is using static ip (on my LAN) of 192.168.20.243
The repeater was working fine up until about a month ago when It quit connecting to any nodes.
This morning I reset my router and reconfigured anything – no change
This morning I reformatted my repeater box and reconfigured using the Allstar Portal – no change
When I attempt to connect my repeater to my hub, which is on the same LAN with the node settings added that are listed above I get this error message on the CLI
[Dec 28 08:37:53] WARNING[2500]: chan_iax2.c:4328 handle_call_token: Address 192 .168.20.243 failed CallToken hash inspection
[Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_token: Address 192 .168.20.243 failed CallToken hash inspection
[Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_token: Address 192 .168.20.243 failed CallToken hash inspection
K0PWO_Hub*CLI> [Dec 28 08:37:53] WARNING[2500]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection
K0PWO_Hub*CLI> [Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection
No such command '[Dec 28 08:37:53] WARNING[2500]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands)
No such command '[Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands)
K0PWO_Hub*CLI> [Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection[Dec 28 08:37:53] WAR NING[2500]: chan_iax2.c:4328 handle_call_token: Address 192.168.20.243 failed Ca llToken hash inspection
K0PWO_Hub*CLI> [Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection
No such command '[Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection[Dec 28 08:37:53] W ARNING[2500]: chan_iax2.c:4328 handle_call_token: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands)
No such command '[Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands)
K0PWO_Hub*CLI> [Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspectionexit
No such command '[Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspectionexit' (type 'help [ Dec 28' for other possible commands)
Once again, anybody have any ideas on what is wrong?
Thank you for any help provided.
David<hr>_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users 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 mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users 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.
participants (2)
-
Chuck Henderson -
mike＠midnighteng.com