GNOME Bugzilla – Bug 599554
Missing voice mail indicator (MWI) for SIP accounts
Last modified: 2013-01-26 13:14:06 UTC
"When using Ekiga 2.0.12 from Intrepid with Asterisk, an extension with new voice mail waiting shows a count of the messages waiting in the status bar at the bottom of the window. However when upgraded to Ekiga 3.2.0 on Jaunty there is no longer any indication of messages waiting. Both fail to display anything in the Voice Mails column of the Accounts dialog." SIP messages comparing 2.0.12 and 3.2.0: http://launchpadlibrarian.net/34253496/SIP.txt "I've installed Ekiga 3.2.6~ppa~jaunty1 from your PPA as requested and re-tested. There's still no indication anywhere of voice mail. I'm still not sure where I should see it in the 3.2 code stream but it's not on the status bar (next to the "signal strength" indicator), in the call log, in the Accounts dialog or anywhere on the tray icon. I've tested logging into an account which already has new messages and missing a call so that I get a new message while on-line. Neither give any indication a message is waiting." Downstream bug in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/459147
I confirm this commit : 28e50e3dbb1bf65ac956e92b6f95b9c3a088a2fd (among others) severely broke that feature. Julien, I don't understand what you were trying to do. And the commit looks unfinished. (the commit message tells that mwi has been moved out of the core classes, but it seems the signal is still there, but the account window does not get it). Can you have a look and finish it ? Thank you.
The situation was the following : the mwi was making sense only for the opal sip accounts, but was implemented in the whole account stack. So I removed it from the account stack and (supposedly, according to that bug report) made it available in two places : - the opal account code pushes the information to the status line in the main window ; - the opal account code shows how many messages are waiting for that account in the status column of the account window. Sigh... I'll try to have a look, when I find the time.
Just a side remark: - working code matters more than where a method is placed - many protocols out there support message waiting indications (I'm thinking to SIP, H323, Jabber, MSN, Yahoo, ...) - having a signal that does nothing in one case is better than having 3 typecasts everywhere we want to get notifications (e.g. if we have 3 types of accounts that support MWI and the signal/method is not in the base class)
I checked the actual changes, so I could tell more precisely what is supposed to happen when you have a message waiting : - it is shown in the account status and hence should be visible in the account window ; - you get an audio event about it. And as far as I remember, when an account get registered, its status is shown on the main window status line. Could you confirm that is the case?
That's correct. I think that at some point we also had a message in the statusbar indicating the totalk number of voicemails for *all* accounts (ie a sum).
Hi, Any plan to fix it in the stable branch (i.e. for 3.2.7) ? Best regards, Yannick
Well, if you want a total, I guess the simpler is that the sip-endpoint should emit a notification about the total number.
I'm the original reporter from downstream at https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/459147. I see this bug is now waiting for information but it isn't clear what. Can I help at all?
Is this a duplicate of bug #588186 ?
*** Bug 690183 has been marked as a duplicate of this bug. ***
This bug appears only if you do not have vmexten option set in asterisk configuration file. A workaround has just been committed to make MWI work even if this option is not set. http://opalvoip.svn.sourceforge.net/viewvc/opalvoip?view=revision&revision=29005