I have a CentOs5 Asterisk installation ver 1.6.
The Asterisk installation is on IP 192.168.0.202
and a Twinkle Softphone is on 192.168.0.2.
I can’t get Twinkle to make a call to, or register with Asterisk.
I have a test dialplan on the Asterisk server that I want to dial into. The dial plan is functioning when dialed from the CLI (CLI> console dial 1001).
# cat extensions.conf
[default]
exten => 1001,1,Answer()
exten => 1001,2,Playback(hello-world)
exten => 1001,3,Hangup()
...
I am new to Asterisk so I don’t know if I have the Twinkle set up wrong or if it’s an Asterisk issue, or what.
I noticed the following in twinkle.log:
+++ 27-10-2010 22:38:57.994886 INFO NORMAL ::listen_udp
Received ICMP from: 192.168.0.202
ICMP type: 3
ICMP code: 10
Destination of packet causing ICMP: 192.168.0.202:5060
Socket error: 113 No route to host
---
Any help appreciated.
Are there settings I should be checking with:
CLI> Sip show settings
?
Lastly–Firewall:
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere
ACCEPT udp -- anywhere anywhere udp dpt:sip
ACCEPT udp -- anywhere anywhere udp dpts:ndmp:dnp
ACCEPT udp -- anywhere anywhere udp dpts:terabase:4999
ACCEPT udp -- anywhere anywhere udp dpt:iax
ACCEPT tcp -- anywhere anywhere tcp dpt:5038
Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp any
ACCEPT esp -- anywhere anywhere
ACCEPT ah -- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
Nmap
$ nmap -v -p 5060 -PN 192.168.0.202
Starting Nmap 4.53 ( http://insecure.org ) at 2010-10-28 11:00 EDT
Initiating Parallel DNS resolution of 1 host. at 11:00
Completed Parallel DNS resolution of 1 host. at 11:00, 0.00s elapsed
Initiating Connect Scan at 11:00
Scanning bubbles (192.168.0.202) [1 port]
Completed Connect Scan at 11:00, 0.00s elapsed (1 total ports)
Host bubbles (192.168.0.202) appears to be up ... good.
Interesting ports on bubbles (192.168.0.202):
PORT STATE SERVICE
5060/tcp filtered sip
Read data files from: /usr/share/nmap
Nmap done: 1 IP address (1 host up) scanned in 0.036 seconds
Thanks,
Frank