So with a LACP (802.3ad) trunk presented as bond0 I can throw as many as I want at it?
From: [email protected] [mailto:[email protected]] On Behalf Of Michael Picher Sent: Sunday, June 24, 2012 5:01 AM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] voicemail and autoattendant 408 timeout You can bond interfaces today... As long as the interfaces present themselves to the Linux system as a single network interface. You can then have connections to multiple switches for a diverse path. Thanks, Mike On Sun, Jun 24, 2012 at 12:00 AM, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> wrote: I'd love to know more about this, as I see that this issue has been "fixed" ( http://track.sipfoundry.org/browse/XX-8692 ) but I haven't run across any documentation to dive deep into it. I've played with 4.6 beta (when is the expected stable release btw?) a month or so ago before deploying 4.4. I remember seeing in sipxsupervisor that it had iptables/firewall support. Will the 4.6 version be able to bond to specified interfaces? Thanks, Matt From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Tony Graziano Sent: Saturday, June 23, 2012 4:35 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] voicemail and autoattendant 408 timeout You really need to understand how sipx works with projecting and managing configuration files. There is a way to do this via the .vm files but you will need to take care to understand how to deal with the upgrade/update process as well. On Sat, Jun 23, 2012 at 1:27 PM, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> wrote: So I've noticed! On a reboot it blew away the freeswitch modifications I had entered. I'm curious what would happen if I make them immutable? From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Tony Graziano Sent: Saturday, June 23, 2012 12:59 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] voicemail and autoattendant 408 timeout Therein lies your problem. At no time has multiple NIC's ever been supported or recommended. I would suggest you drop back down to one NIC. The issue you are having WILL reintroduce iteself as the system runs, I guarantee it. On Sat, Jun 23, 2012 at 10:20 AM, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> wrote: 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<http://sipx.hmherbs.com>, domain as sipx.hmherbs.com<http://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<http://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<http://192.168.2.0/24> subnet (iptables -t nat -A POSTROUTING -o eth0 -s 192.168.2.0/24<http://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<http://10.1.10.0/24>, 192.168.1.0/24<http://192.168.1.0/24>, and 192.168.2.0/24<http://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]<mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430<tel:434.984.8430> sip: [email protected]<mailto:[email protected]> Fax: 434.465.6833<tel:434.465.6833> ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013!<http://sipxcolab2013.eventbrite.com/?discount=tony2013%22> LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426<tel:434.984.8426> sip: [email protected]<mailto:[email protected]> Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-users mailing list [email protected]<mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430<tel:434.984.8430> sip: [email protected]<mailto:[email protected]> Fax: 434.465.6833<tel:434.465.6833> ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013!<http://sipxcolab2013.eventbrite.com/?discount=tony2013%22> LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426<tel:434.984.8426> sip: [email protected]<mailto:[email protected]> Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-users mailing list [email protected]<mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square Suite 201 Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> linkedin<http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro> www.ezuce.com<http://www.ezuce.com> ------------------------------------------------------------------------------------------------------------ There are 10 kinds of people in the world, those who understand binary and those who don't.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
