Tony / All,
I've started over completely from scratch as you suggested, but I was still
having this issue. I eventually found the problem, so I'll share in case
anybody runs into this. I ran (as root)
$ service sipxecs stop
$ sipxconfig.sh --database drop
$ sipxconfig.sh --database create
$ sipxecs-setup-system
Ran through the installer again. Set hostname as sipx.hmherbs.com, domain as
sipx.hmherbs.com. sipxecs is providing DNS and DHCP.
$ reboot
Logged into sipXsupervisor, added the phones and users back in manually. Ran a
test call to 101, same thing was happening evident in
/var/log/sipxecs/sipXproxy.log :
"2012-06-23T12:13:39.324672Z":175:KERNEL:ERR:sipx.hmherbs.com:SipClientTcp-173:41585940:SipXProxy:"OsSocket::write
26 (70.88.18.153:15060 :-1) send returned -1, errno=32 'Broken pipe'"
"2012-06-23T12:13:39.324728Z":176:SIP:ERR:sipx.hmherbs.com:SipClientTcp-173:41585940:SipXProxy:"SipClientWriteBuffer[SipClientTcp-173]::writeMore
OsSocket::write() returned -1, errno = 32"
I knew it had to do something with binding that port. I do have a non-standard
interface setup :
[root@sipx ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:25:90:6A:ED:54
inet addr:70.88.18.153 Bcast:70.88.18.155 Mask:255.255.255.252
inet6 addr: fe80::225:90ff:fe6a:ed54/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9245 errors:0 dropped:0 overruns:0 frame:0
TX packets:10261 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1093753 (1.0 MiB) TX bytes:5985658 (5.7 MiB)
Interrupt:177 Memory:fe9e0000-fea00000
eth0:0 Link encap:Ethernet HWaddr 00:25:90:6A:ED:54
inet addr:10.1.10.11 Bcast:10.1.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:177 Memory:fe9e0000-fea00000
eth1 Link encap:Ethernet HWaddr 00:25:90:6A:ED:55
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::225:90ff:fe6a:ed55/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:382 errors:0 dropped:0 overruns:0 frame:0
TX packets:146 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:48535 (47.3 KiB) TX bytes:28435 (27.7 KiB)
Interrupt:169 Memory:feae0000-feb00000
eth1:0 Link encap:Ethernet HWaddr 00:25:90:6A:ED:55
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:169 Memory:feae0000-feb00000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:46014 errors:0 dropped:0 overruns:0 frame:0
TX packets:46014 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:25541472 (24.3 MiB) TX bytes:25541472 (24.3 MiB)
iptables is running a masquerade for the 192.168.2.0/24 subnet (iptables -t nat
-A POSTROUTING -o eth0 -s 192.168.2.0/24 -j MASQUERADE), but not restricting
anything at all on the sipxecs interfaces. Phones are on the 1.0/24 subnet
(eth1), and public WAN (eth0). Netstat ($ netstat -tulpn |grep 15060 ) was
showing port 15060 (freeswitch) bound to 10.1.10.11. I disabled IPV6,
rebooted... still the same problem. I then manually edited
/etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml, and changed this
section :
<!--
Defaults changed, mlk 6.23.12
<param name="rtp-ip" value="$${local_ip_v4}"/>
<param name="sip-ip" value="$${local_ip_v4}"/>
-->
<param name="rtp-ip" value="0.0.0.0"/>
<param name="sip-ip" value="0.0.0.0"/>
<!--
Defaults changed, mlk 6.23.12
<param name="ext-rtp-ip" value="auto-nat"/>
<param name="ext-sip-ip" value="auto-nat"/>
-->
<param name="ext-rtp-ip" value="70.88.18.153"/>
<param name="ext-sip-ip" value="70.88.18.153"/>
$ service sipxecs restart
I check netstat, now it's listening on 70.88.18.153 port 15060. I dial 101 to
test and I don't see the bind error message in sipXproxy.log but I'm still not
hearing the voicemail attendant. The freeswitch logs show the call as being
answered. I noticed it was looking for the default intranet subnets (duh..
forgot that step earlier), so I went back into sipxsupervisor and changed the
subnets to all 10.1.10.0/24, 192.168.1.0/24, and 192.168.2.0/24, restarted, and
tested again. Sure enough, it works!
Short and sweet... if you have multiple interfaces, check that freeswitch is
binding to the appropriate interface. If it's not, force it to and tell
sipxsupervisor about your subnets.
-Matt
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
