I did manually remove it and reinstall it (sipxivr), prior to replacing the two files manually. The sipxivr that did not work was installed by that rpm.
On Sat, Aug 11, 2012 at 4:52 PM, George Niculae <[email protected]> wrote: > > On Aug 11, 2012 11:45 PM, "Tony Graziano" <[email protected]> > wrote: > > > > I checked all my packages to make sure they matched the repo before > digging into this. > > > > If I have the rpm's that are the latest in the stable repo (and I do), I > would suggest it either has the wrong sipxivr.jar (maybe sipxivr.sh too) > packaged in the rpm. > > > > If that commit is 9 months old how do you determine when it was > committed in the build? > > > > > > Packages contains all code committed until > > > https://github.com/dhubler/sipxecs/commit/aac6d8db08f44b8747f1d30612eef4d866b01ee9 > > (rpm name is g + aac6d8 that is first 6 letters from commit's hash) > > I still think you're running old sipxivr.jar file, maybe you try to > manually remove it before yum update. > > George > > > > > On Sat, Aug 11, 2012 at 4:35 PM, George Niculae <[email protected]> > wrote: > >> > >> > >> On Aug 11, 2012 11:31 PM, "Tony Graziano" <[email protected]> > wrote: > >> > > >> > I believe you because my sipxcommons is: > >> > > >> > Package Details > >> > Description > >> > Common server side Java packages and supporting third-parth JAR's for > sipX > >> > Package > >> > sipxcommons > >> > Class > >> > Productivity/Telephony/SIP/Servers > >> > Version > >> > 4.4.0-418.gaac6d8 > >> > Vendor > >> > SIPfoundry > >> > Architecture > >> > x86_64 > >> > Installed > >> > 11/Aug/2012 13:08 > >> > >> Yep, latest published is sipxcommons-4.4.0-418.gaac6d8.x86_64.rpm > >> > >> Wonder how yum update could miss this... > >> > >> George > >> > >> > On Sat, Aug 11, 2012 at 4:26 PM, George Niculae <[email protected]> > wrote: > >> >> > >> >> That's related more to this commit > https://github.com/dhubler/sipxecs/commit/e19470bb65522aa52845eafbf283ff63f7c3b55b > >> >> > >> >> I suspect sipxcommons didn't updated on your system, can you check > version? > >> >> > >> >> George > >> >> > >> >> On Aug 11, 2012 11:10 PM, "Tony Graziano" < > [email protected]> wrote: > >> >> > > >> >> > My AA and VM does not work after yum'ing to the latest 4.4 code. > This system had two files on it that had been used to handle testing of > faxes in pdf form from earlier this year (sipxivr.jar and sipxivr.sh). > These were replaced when the update occured and are the most recent/current > version like I thought it should be. > >> >> > > >> >> > I can call into the conference server, but the AA and VM no longer > works. There is nothing in sofia/freeswitch or sipxproxy log and the best > indicator I have is that there is a localization being called in the > sipxivr script that is not supposed to be there. I uninstalled and > reinstalled sipxivr, but I still have the same issue. I suspect there is a > problem with the latest 4.4 build because I have this issue only on systems > built after this was introduced: > >> >> > > >> >> > http://track.sipfoundry.org/browse/XX-10220 > >> >> > > >> >> > Here is the relevant log snippet from sipxivr: > >> >> > > >> >> > > >> >> > > "2012-08-11T19:06:21.633000Z":341:sipXivr:ERR:pbx.voice.mydomain.com: > Thread-7:00000000:sipxivr:"SipXivr::run" > >> >> > java.lang.NoSuchMethodError: > org.sipfoundry.commons.freeswitch.Localization.<init>(Ljava/lang/String;Ljava/lang/String;Ljava/util/HashMap;Lorg/sipfoundry/commons/freeswitch/FreeSwitchConfigurationInterface;Lorg/sipfoundry/commons/freeswitch/FreeSwitchEventSocketInterface;)V > >> >> > at org.sipfoundry.faxrx.FaxRx.loadConfig(FaxRx.java:106) > >> >> > at org.sipfoundry.faxrx.FaxRx.run(FaxRx.java:122) > >> >> > at org.sipfoundry.sipxivr.SipXivr.run(SipXivr.java:165) > >> >> > at java.lang.Thread.run(Thread.java:679) > >> >> > > "2012-08-11T19:06:21.633000Z":342:sipXivr:DEBUG:pbx.voice.mydomain.com:Thread-7:00000000:sipxivr:"SipXivr::run > Ending SipXivr thread with client Socket[addr=/172.16.246.2 > ,port=44510,localport=8084]" > >> >> > > ^T"2012-08-11T19:07:42.509000Z":343:sipXivr:DEBUG:pbx.voice.mydomain.com:SslListener0-3:00000000:sipxivr:"Messages::newMessages > m_usage for /var/sipxdata/mediaserver/data/mailstore/209/ is 1" > >> >> > > "2012-08-11T19:07:42.510000Z":344:sipXivr:DEBUG:pbx.voice.mydomain.com:SslListener0-3:00000000:sipxivr:"Messages::releaseMessages > m_usage for /var/sipxdata/mediaserver/data/mailstore/209/ is 0" > >> >> > > "2012-08-11T19:07:42.510000Z":345:sipXivr:INFO:pbx.voice.mydomain.com:SslListener0-3:00000000:sipxivr:"Mwistatus::doGet > [email protected]" > >> >> > > "2012-08-11T19:07:54.180000Z":346:sipXivr:DEBUG:pbx.voice.mydomain.com:SslListener0-3:00000000:sipxivr:"Messages::newMessages > m_usage for /var/sipxdata/mediaserver/data/mailstore/204/ is 1" > >> >> > > "2012-08-11T19:07:54.180000Z":347:sipXivr:DEBUG:pbx.voice.mydomain.com:SslListener0-3:00000000:sipxivr:"Messages::releaseMessages > m_usage for /var/sipxdata/mediaserver/data/mailstore/204/ is 0" > >> >> > > "2012-08-11T19:07:54.181000Z":348:sipXivr:INFO:pbx.voice.mydomain.com:SslListener0-3:00000000:sipxivr:"Mwistatus::doGet > [email protected]" > >> >> > > >> >> > --- > >> >> > > >> >> > Since one cannot downgrade (previous version RMP's are no longer > posted), is there an easier way to get around this? I had to get to a > system with the build date of: > >> >> > > >> >> > Package Details > >> >> > Description > >> >> > IVR subystem that uses FreeSWITCH as a media server. > >> >> > Package > >> >> > sipxivr > >> >> > Class > >> >> > Productivity/Telephony/SIP/Servers > >> >> > Version > >> >> > 4.4.0-382.g16f5 > >> >> > Vendor > >> >> > SIPfoundry > >> >> > Architecture > >> >> > x86_64 > >> >> > Installed > >> >> > 18/May/2012 11:47 > >> >> > > >> >> > And replace the sipxivr.jar and sipxivr.sh files and restart media > server to get the AA and VM working again. > >> >> > > >> >> > I think this is a bug... > >> >> > > >> >> > > >> >> > -- > >> >> > ~~~~~~~~~~~~~~~~~~ > >> >> > 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/ > >> >> > >> >> > >> >> _______________________________________________ > >> >> 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/ > >> > >> > >> _______________________________________________ > >> 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/ > > _______________________________________________ > 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! <http://sipxcolab2013.eventbrite.com/?discount=tony2013> -- 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/
