Typically when I do any type of yum update on sipx, I use the following procedure:
1. Stop sipx services: sipxagent -d stop_sipxecs 2. Update via YUM: yum update 3. If new kernel, then reboot, otherwise, start sipx services: sipxagent -d start_sipxecs Once sipxconfig UI is reachable, do: System>Server>[Check the server updated] and click "Send Profiles". On Tue, Sep 25, 2012 at 8:31 AM, darthzejdr <[email protected]> wrote: > Done the yum things, went into telephony, turned registrar on, clicked > apply, went to servers and send profiles. > > Still no 5060 or 5061 rules in ipconfig. > > Rebooted server and the rules are there :) > > Thank you > > [root@sipx1 ~]# iptables --list-rules > -P INPUT DROP > -P FORWARD DROP > -P OUTPUT ACCEPT > -N syn-flood > -A INPUT -s 192.168.0.46/32 -i eth0 -j ACCEPT > -A INPUT -i eth0 -p tcp -m tcp --dport 80 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -p tcp -m tcp --dport 443 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -p udp -m udp --dport 53 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -p tcp -m tcp --dport 21 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -p tcp -m tcp --dport 20 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -p tcp -m tcp --dport 50000:50050 -m state --state > NEW,ESTABLISHED -j ACCEPT > -A INPUT -i eth0 -p udp -m udp --dport 30000:31000 -m state --state > NEW,ESTABLISHED -j ACCEPT > -A INPUT -i eth0 -p tcp -m tcp --dport 5060 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -p tcp -m tcp --dport 5061 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -p udp -m udp --dport 5060 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -p tcp -m tcp --dport 22 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -p udp -m udp --dport 69 -m state --state NEW,ESTABLISHED > -j ACCEPT > -A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT > -A INPUT -p icmp -j ACCEPT > -A INPUT -i lo -j ACCEPT > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of George Niculae > Sent: Tuesday, September 25, 2012 1:49 PM > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] TLS port problem > > On Tue, Sep 25, 2012 at 2:43 PM, darthzejdr <[email protected]> wrote: >> Ive done yum update, but atm i have a different problem. I've disabled >> sip registrar, and that removed all the rules from firewall. The >> problem is after i reenabled the registrar, the rules aren't getting added > to iptables. >> I tried restarting the servers, disabling and enabling the firewall, >> even removing the second server from cluster. Nothing helps > > Do a yum clean all and then yum update, I published another RPM minutes ago. > Let me know if it gets updated > > Thanks > George > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 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! -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
