I did the update myself yesterday without that issue. I did need to change the login type for user sipxchange in /etc/passwd to use /bin/bash (instead of nologin). Also ensure for these purposes that iptables is not running and that selinux if disabled.
On Fri, Dec 17, 2010 at 7:01 AM, Chitra <[email protected]> wrote: > > Hi We tried to do yum update today from 0.4.4 to 0.0.4.5.1. Yum update was > succesful( this was by using the command yum install sipxecs). > But it has a problem i.e. it comes up with "SIPXPROXY=FAILED" in the linux > machine. > We had logged a bug earlier for the same and the issue no is: XX9243. > Please look into it and do the needful. > > Thanks, > Chitra.M.S. > > > > [email protected] wrote: > > Send sipx-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://list.sipfoundry.org/mailman/listinfo/sipx-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sipx-dev digest..." > > > ------------------------------ > > [please change the subject line when replying] > > ------------------------------ > > Today's Topics: > > 1. Re: Not able to do yum update from 0.4.4 to 0.0.4.5.1 > ([email protected]) > 2. Re: Not able to do yum update from 0.4.4 to 0.0.4.5.1 > (Douglas Hubler) > 3. Re: Not able to do yum update from 0.4.4 to 0.0.4.5.1 > ([email protected]) > 4. Dial plan / FreeSWITCH question (Laurentiu Ceausescu) > 5. Re: Dial plan / FreeSWITCH question (Michal Bielicki) > 6. Re: Dial plan / FreeSWITCH question (Laurentiu Ceausescu) > > > > ------------------------------ > > Subject: > Re: [sipx-dev] Not able to do yum update from 0.4.4 to 0.0.4.5.1 > From: > [email protected] > Date: > Wed, 15 Dec 2010 17:18:13 +0000 (UTC) > To: > sipXecs developer discussions > <[email protected]><[email protected]> > To: > sipXecs developer discussions > <[email protected]><[email protected]> > Upon further reflection, a better way would probably be to just take out > the part where it does "chkconfig --add freeswitch" in the postinstall > script for freeswitch-1.0.7-trunk. > > ----- Original Message ----- > From: [email protected] > To: "sipXecs developer discussions" > <[email protected]><[email protected]> > Sent: Wednesday, December 15, 2010 10:27:36 AM > Subject: Re: [sipx-dev] Not able to do yum update from 0.4.4 to 0.0.4.5.1 > > Perhaps the chkconfig comment in /etc/rc.d/init.d/freeswitch should default > to off? > > ------------------------------ > > Subject: > Re: [sipx-dev] Not able to do yum update from 0.4.4 to 0.0.4.5.1 > From: > Douglas Hubler <[email protected]> <[email protected]> > Date: > Wed, 15 Dec 2010 12:28:40 -0500 > To: > sipXecs developer discussions > <[email protected]><[email protected]> > To: > sipXecs developer discussions > <[email protected]><[email protected]> > On Wed, Dec 15, 2010 at 10:27 AM, <[email protected]> wrote: > >> Not sure if this is related, but I noticed that when the >> freeswitch-1.0.7-trunk RPM gets installed, the service is automatically >> chkconfig'ed on for runlevels 3, 4 and 5. This should be disabled, since >> freeswitch is run from sipxsupervisor instead of standalone from init. >> >> > yes, this is correct however i am trying to upload a build that has this > fix. > > What the fix I went with was to now not modify freeswitch in any way for > sipx's integration. When you install freeswitch, its you would get if > anyone was to download freeswitch and install it. e.g. i removed > sipx-freeswitch and now build freeswitch almost straight from FS git. Now > the wrapper packages sipXfreeSwitch has a post install and an rpm trigger to > undo the chkconfig. > > > > ------------------------------ > > Subject: > Re: [sipx-dev] Not able to do yum update from 0.4.4 to 0.0.4.5.1 > From: > [email protected] > Date: > Wed, 15 Dec 2010 17:53:20 +0000 (UTC) > To: > sipXecs developer discussions > <[email protected]><[email protected]> > To: > sipXecs developer discussions > <[email protected]><[email protected]> > OK, awesome. That definitely sounds like the way to go if you want to keep > the freeswitch RPM "stock" as it comes. > > ----- Original Message ----- > From: "Douglas Hubler" <[email protected]> <[email protected]> > To: "sipXecs developer discussions" > <[email protected]><[email protected]> > Sent: Wednesday, December 15, 2010 12:28:40 PM > Subject: Re: [sipx-dev] Not able to do yum update from 0.4.4 to 0.0.4.5.1 > > yes, this is correct however i am trying to upload a build that has this > fix. > > What the fix I went with was to now not modify freeswitch in any way for > sipx's integration. When you install freeswitch, its you would get if > anyone was to download freeswitch and install it. e.g. i removed > sipx-freeswitch and now build freeswitch almost straight from FS git. Now > the wrapper packages sipXfreeSwitch has a post install and an rpm trigger to > undo the chkconfig. > > ------------------------------ > > Subject: > [sipx-dev] Dial plan / FreeSWITCH question > From: > Laurentiu Ceausescu <[email protected]> <[email protected]> > Date: > Thu, 16 Dec 2010 13:00:24 +0200 > To: > sipXecs developer discussions > <[email protected]><[email protected]> > To: > sipXecs developer discussions > <[email protected]><[email protected]> > Hi, > > I set up a conference "myConf" with 333 as extension and 1234 as pin. > > In sipX_context.xml, my dial plan looks like .. > <extension name="333"> > <condition field="destination_number" expression="^myConf$"> > <action application="set" data="*supplied_pin*=${sip_h_X-ConfPin}"/> > <action application="bridge" data="loopback/app=conference:myc...@333 > +1234"/> > </condition> > </extension> > > I noticed that '*supplied_pin*' is not set in the conference context > (mod_conference.c from FreeSWITCH). > Is there any way so setup this variable in conference context? > > Thanks, > Laurentiu > > ------------------------------ > > Subject: > Re: [sipx-dev] Dial plan / FreeSWITCH question > From: > Michal Bielicki > <[email protected]><[email protected]> > Date: > Thu, 16 Dec 2010 12:14:05 +0100 > To: > sipXecs developer discussions > <[email protected]><[email protected]> > To: > sipXecs developer discussions > <[email protected]><[email protected]> > Since you want it in the B-Leg you need to export it and not set it > so > > <action application="export" data="*supplied_pin* > =${sip_h_X-ConfPin}"/> > > > should do the trick after the set line you did. > > Am 16.12.2010 um 12:00 schrieb Laurentiu Ceausescu: > > Hi, > > I set up a conference "myConf" with 333 as extension and 1234 as pin. > > In sipX_context.xml, my dial plan looks like .. > <extension name="333"> > <condition field="destination_number" expression="^myConf$"> > <action application="set" data="*supplied_pin*=${sip_h_X-ConfPin}"/> > > <action application="bridge" > data="loopback/app=conference:myc...@333+1234"/> > </condition> > </extension> > > I noticed that '*supplied_pin*' is not set in the conference context > (mod_conference.c from FreeSWITCH). > Is there any way so setup this variable in conference context? > > Thanks, > Laurentiu > _______________________________________________ > sipx-dev mailing list > > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > *Michal Bielicki* > Geschäftsführer / CEO > > *Seventh Signal Ltd. & Co. KG* > Weigandufer 45, Büro 115, D-12059 Berlin > Voice: +49 30 60988730 > > Amtsgericht Charlottenburg HRA 44413 B > Ust.-ID: DE266981999 > Geschäftsführer: Michal Bielicki > Persönlich Haftende Gesellschafterin: > Seventh Signal Ltd, 69 Great Hampton St. Birmingham, > B18 6EW, GB, Company Nr.: 06889439 > WWW.: http://www.seventhsignal.de > > > ------------------------------ > > Subject: > Re: [sipx-dev] Dial plan / FreeSWITCH question > From: > Laurentiu Ceausescu <[email protected]> <[email protected]> > Date: > Thu, 16 Dec 2010 14:06:59 +0200 > To: > sipXecs developer discussions > <[email protected]><[email protected]> > To: > sipXecs developer discussions > <[email protected]><[email protected]> > it works > Thanks Michal > > On Thu, Dec 16, 2010 at 1:14 PM, Michal Bielicki < > [email protected]> wrote: > >> Since you want it in the B-Leg you need to export it and not set it >> so >> >> <action application="export" data="*supplied_pin* >> =${sip_h_X-ConfPin}"/> >> >> >> should do the trick after the set line you did. >> >> Am 16.12.2010 um 12:00 schrieb Laurentiu Ceausescu: >> >> Hi, >> >> I set up a conference "myConf" with 333 as extension and 1234 as pin. >> >> In sipX_context.xml, my dial plan looks like .. >> <extension name="333"> >> <condition field="destination_number" expression="^myConf$"> >> <action application="set" data="*supplied_pin* >> =${sip_h_X-ConfPin}"/> >> >> <action application="bridge" >> data="loopback/app=conference:myc...@333+1234"/> >> </condition> >> </extension> >> >> I noticed that '*supplied_pin*' is not set in the conference context >> (mod_conference.c from FreeSWITCH). >> Is there any way so setup this variable in conference context? >> >> Thanks, >> Laurentiu >> _______________________________________________ >> sipx-dev mailing list >> >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> >> >> *Michal Bielicki* >> Geschäftsführer / CEO >> >> *Seventh Signal Ltd. & Co. KG* >> Weigandufer 45, Büro 115, D-12059 Berlin >> Voice: +49 30 60988730 >> >> Amtsgericht Charlottenburg HRA 44413 B >> Ust.-ID: DE266981999 >> Geschäftsführer: Michal Bielicki >> Persönlich Haftende Gesellschafterin: >> Seventh Signal Ltd, 69 Great Hampton St. Birmingham, >> B18 6EW, GB, Company Nr.: 06889439 >> WWW.: http://www.seventhsignal.de >> >> >> _______________________________________________ >> sipx-dev mailing list >> >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> > > ------------------------------ > > _______________________________________________ > sipx-dev mailing list > [email protected] > http://list.sipfoundry.org/mailman/listinfo/sipx-dev > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net <http://support.myitdepartment.net>Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
