The messages point to email. I think updating one version at a time is prudent. I would have tested at 4.20 before updating to 4.21.
In turning off email messaging, I might also remove user information as a test, then re-enter it upon enabling to see of that gives any success. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: Tony Graziano <[email protected]> To: [email protected] <[email protected]>; [email protected] <[email protected]> Sent: Thu Aug 19 19:22:15 2010 Subject: Re: [sipx-users] Voicemail does not work after update - nullpointer exception in SipxIVR after updat The major changes were made to iser xml files for unified messaging. Perhaps disable/enable that on a user will yield some success. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: [email protected] <[email protected]> To: [email protected] <[email protected]> Sent: Thu Aug 19 18:28:15 2010 Subject: Re: [sipx-users] Voicemail does not work after update - nullpointerexceptionin SipxIVR after updat Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <[email protected]> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <50721> Message-ID: <[email protected]> Good day, I have what appears to be a problem similar to René's. There seems to be a missing voicemail parameter that causes the VM service to abort the connection with this error message. (from /var/log/sipxpbx/sipxivr.log) "2010-08-18T21:44:19.325000Z" :10:sipXivr:INFO:ourpbxserver.com:Thread-5:00000000:sipxivr: "SipXivr::run Accepting call-id NXY4MDQxMPlhZ4djYjgxNTM1N283ZDVjYzhmZjaiNWU. from mailto:[email protected] to mailto:[email protected]:15060"; "2010-08-18T21:44:20.389000Z" :11:sipXivr:INFO:ourpbxserver.com:Thread-5:00000000:sipxivr: "Starting voicemail for mailbox \"240\" action=\"deposit" "2010-08-18T21:44:20.391000Z":12:sipXivr:ERR:ourpbxserver.com:Thread-5:00000000:sipxivr: "SipXivr::run" java.lang.NullPointerException at org.sipfoundry.voicemail.EmailFormatter.init(EmailFormatter. java:81) at org.sipfoundry.voicemail.EmailFormatter.getEmailFormatter(Em ailFormatter.java:60) at org.sipfoundry.voicemail.Deposit.<init>(Deposit.java:118) at org.sipfoundry.voicemail.VoiceMail.voicemail(VoiceMail.java: 206) at org.sipfoundry.voicemail.VoiceMail.run(VoiceMail.java:163) at org.sipfoundry.sipxivr.SipXivr.run(SipXivr.java:152) at java.lang.Thread.run(Thread.java:636) I have a CentOS 5 server on which I had installed sipXecs 4.2.0. I did some basic testing, imported my users from a server with version 4.0.1, connected to an ITSP and everything seemed OK. I upgraded to 4.2.0 to 4.2.1 and the VM system will not work. I tried disabling/enabling VM for the server and for all users but that did not solve the problem. I created a new user, but it still has the same issue. The Job Status is not showing any problems when I enabled/disabled a user's VM or the server's VM service. The voicemail dial plan is the system's default. I also tried turning on/off a user's Unified Messaging Voicemail notification, but no luck. I have ensured that the sipx user sipxchange owns all files in /var/sipxdata and /etc/sipxpbx. Is there some setting that I need to update or check? Thank you for any help that you can provide. Best Regards, Kimball [quote title=Tony Graziano wrote on Tue, 10 August 2010 02:50]Actually, I remember this I think... It had to do with extra xml settings in config that had not populated in VM settings, because there are more parameters than there were before. I "believe" a workaround I had at the time was to disable Vm for a user, then re-enable it. Can you try that for one user and doublecheck their VM settings in sipxconfig and ensure there are no failed jobs first? When you did your update to 4.2.1, did you make sure VM worked, or that it was simply running as a service without errors? On Tue, Aug 10, 2010 at 3:51 AM, Rene Pankratz <mailto:[email protected][/email]>wrote: > Hello List members. > > I did the following steps in my update: updated my old > SipX 4.0.4 to 4.2.1 > and archived the Config & Vm via webinterface. > Then i did a clean install of Sipx 4.2.1-018930 and > restored Config & VM. > > Unfortunately the Voicemail system does not work any > more. I can login but > when I try to play a message the VM hangs up. > > The following error is shown in sipxivr.log: > > ... Login successful ... > > "2010-08-10T07:44:26.975000Z" > :1772:sipXivr:INFO:sipx1.voip.ikt-bs.de:Thread-59:00000000:s > ipxivr: "Menu::menu > Collected digits=(1)" > > "2010-08-10T07:44:26.977000Z":1773:sipXivr:ERR:sipx1.voip.ikt-bs.de: > Thread-59:00000000:sipxivr:"SipXivr::run" > java.lang.NullPointerException > at > > org.sipfoundry.voicemail.VmMessage.getTimestamp(VmMessage.ja > va:674) > at > org.sipfoundry.voicemail.Messages$2.compare(Messages.java:22 > 8) > at > org.sipfoundry.voicemail.Messages$2.compare(Messages.java:22 > 4) > at java.util.Arrays.mergeSort(Arrays.java:1270) > at java.util.Arrays.sort(Arrays.java:1210) > at > java.util.Collections.sort(Collections.java:159) > at > org.sipfoundry.voicemail.Messages.getFolder(Messages.java:22 > 4) > at > org.sipfoundry.voicemail.Messages.getInbox(Messages.java:195 > ) > at > > org.sipfoundry.voicemail.Retrieve.playMessages(Retrieve.java > :394) > at > org.sipfoundry.voicemail.Retrieve.main_menu(Retrieve.java:34 > 1) > at > > org.sipfoundry.voicemail.Retrieve.retrieveVoiceMail(Retrieve > .java:85) > at > org.sipfoundry.voicemail.VoiceMail.voicemail(VoiceMail.java: > 219) > at > org.sipfoundry.voicemail.VoiceMail.run(VoiceMail.java:163) > at > org.sipfoundry.sipxivr.SipXivr.run(SipXivr.java:152) > at java.lang.Thread.run(Thread.java:619) > > Any Ideas how to fix this? > > René > _______________________________________________ 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/
