> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Cuneyt M > Sent: Monday, September 07, 2009 2:34 PM > > Dear All, > > I have few critical issues with latest dev version (ISO) > which is updated to-date via unstable repo.
"Latest" = what? (it's a moving target...) > > Taking into account its development version, the issues i am > having are rather critical which i hope to resolve with your help. > > 1) If someone leaves a voicemail, it doesnt get delivered to > users's mailbox. Nothing in there. > I have checked the /tmp folder and i can see tons of > tmp_voicemail...wav files with supposedly right (sipxchange) > permissions. It seems to me that voicemail is recorded but > process fails to move from tmp folder to user's mailbox As > this is quite critical, how can i fix it? > I believe this is the issue reported in XX-6383 and fixed in 16353. > 2) With latest updates from unstable repo, i've received the > sipxopenfire, branches and Shared Line Agent service > introduced. However the SIP Registrar started failing every > now and then (takes 10-15 minutes for it to fail after each > restart) with "No Details" shown under the Server->Services-> > interface. SIP Registrar fails almost at the same time as the > Shared Line Appearance service. > In fact Shared Line Appearance service fails every 5 minutes > whether SIP Registrar is running or fails. > > To clarify, i don't use any Shared Line Appearance (BLF etc.) > on any phones - just pure single extension assignment per > each phone. And before the last yum update the system was > running without any problems or fails on the services. > I dont recall Shared Line Appearance being there earlier and > I cant seem to find a way to disable it (assuming that is > causing SIP Registrar to fail). Shared Appearance Agent is a new service added in 15911 (early July). It supports shared lines on Polycom sets (not quite the same as BLF). Are you upgrading or doing a fresh install? Upgrades are not supported within a release, so some files may not have been generated properly. Try Send Profiles for the server. A missing configuration file is one reason that the SAA will exit (and it does not give a message then, which it should). All failed services will eventually settle into a 5 minute retry period, so the two failures might not be related. If you see core files in the log directory, please create a JIRA and attach a snapshot. Carolyn _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
