[arm-allstar] connection request failed

George Csahanin george at dyb.com
Tue Jan 17 08:16:03 EST 2017


I've had that happen if there's a network issue or DNS issue, all being 
external to your location. But digging further:

*Here's what I get:*

2360*CLI> rpt fun 2360 *342838
[Jan 17 07:50:30] WARNING[14134]: chan_iax2.c:9221 socket_process: *Call 
rejected by 67.214.200.168: No such context/extension*
     -- Hungup 'IAX2/67.214.200.168:4569-3753'
     -- Hungup 'Zap/pseudo-27800860'
     -- Hungup 'Zap/pseudo-22885631'
     -- <Zap/pseudo-474528162> Playing 'rpt/node' (language 'en')
     -- <Zap/pseudo-474528162> Playing 'digits/4' (language 'en')
     -- <Zap/pseudo-474528162> Playing 'digits/2' (language 'en')
     -- <Zap/pseudo-474528162> Playing 'digits/8' (language 'en')
     -- <Zap/pseudo-474528162> Playing 'digits/3' (language 'en')
     -- <Zap/pseudo-474528162> Playing 'digits/8' (language 'en')
     -- <Zap/pseudo-474528162> Playing 'rpt/connection_failed' (language 
'en')
     -- Hungup 'Zap/pseudo-474528162'
2360*CLI>

*Trying nmap to look at ports on that node:*

[root at 2360 ~]# nmap -sT -p 4568-4575 67.214.200.168

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2017-01-17 07:52 EST
Interesting ports on dhcp-b4-75-e-c6-6-11.cpe.eaglecable.net 
(67.214.200.168):
PORT     STATE    SERVICE
4568/tcp filtered unknown
*4569/tcp closed*   unknown
4570/tcp filtered unknown
4571/tcp filtered unknown
4572/tcp filtered unknown
4573/tcp filtered unknown
4574/tcp filtered unknown
4575/tcp filtered unknown

Nmap finished: 1 IP address (1 host up) scanned in 12.230 seconds

I'd guess the port forwarding on the cable modem isn't correct.

GeorgeC W2DB

2360


On 1/17/2017 7:50 AM, "Eric Harrison via arm-allstar" wrote:
> Having problems with connection fail on connecting to node 42838 using udp port 4568 in iax.conf  from other Allstar nodes.
> My node 42838 resolves as 67.214.200.168:4569/67.214.200.168  in the /tmp/rpt_extnodes files. So if other allstar node user are receiving
> this info they should be able to connect. Any ideas to the reasoning for failed connections?
>    Eric (N7JYS)
> Marshall's Communications
> _______________________________________________
>
> 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

-- 
George Csahanin
47 Mt. Ararat Ln
Toms River, NJ 08753
732-255-2388 home
401-338-0568 cel
http://dyb.com



More information about the arm-allstar mailing list