Le jeudi 11 septembre 2008 à 20:32 +0200, Loïc Minier a écrit :
> On Thu, Sep 11, 2008, yannick wrote:
> > This has been fixed. Try the new packages from today.
> Will do. Or I guess I should jhbuild my own to make sure I don't lag
> WRT fixed bugs.
Ekiga is a small team of volunteer. I took the responsibility to provide
Ubuntu packages, but computers is not my business: I'm teacher in a
french primary school. I built new packs last night on my spare time and
could only upload them this evening when coming back from work. One of
our dev reworked the build process and I had to adapt to this huge
change. Unfortunately it took more time than i hoped. Now, I hope to be
able to update the packs almost daily. (and i plan to add Gutsy this
evening, including LPAI+H264 codec). This also explain why the packages
are not polished as they could be. I'm working on several parts of the
> > > - popup on startup about network settings which need to be configured
> > > manually; looks like it was an issue with either ufw or some vm stuff
> > > I have installed, clearing iptables rules fixed it
> > Ekiga is not designed to bypass security unlike Skype... It should work
> > without any configuration most of the time.
> I think ekiga should report what the actual issue; all I got was an
> error about network problems. The link to the wiki is a good idea.
I let Damien answer to this.
> Concerning ufw, ekiga might need to ship an ufw config to open certain
> ports. Concerning vm stuff, I reported later that what happened is
> that Ekiga actually tried REGISTERing from two IP addresses
> concurrently, I don't see how sending two REGISTERs can ever be a good
I was not aware an Ubuntu package could open some ports of ufw. This is
something I will dig out
I let Damien answer for the 2 REGISTERs as it is his code.
> > If Ubuntu is kind enough to provide a proxy for VoIP, it could work all
> > the times... The same apply to Empathy using protocols like SIP.
> What do you mean by Ubuntu and a proxy? You mean a proxy on some
> public servers in *.ubuntu.com? Not sure how it would help traversing
> firewalls and routers.
e.g. Jabber protocol use a central server which act as a proxy, MSN
network do the same, etc.
The point is there is several type of NATs, and some of them (symmetric
ones) are impossible to reach if you do not have your own public IP. A
proxy on the internet solve this issue. Technically this technic is
named TURN in the IETF work, see here for more details:
I was referring to a TURN server which might be provided by Ubuntu. This
will mean any SIP client implementing ICE (which include TURN and STUN)
will be able to work all the time.
> > > - doesn't show v4l device name in setup wizard when listing audio and
> > > video input devices
> > The V4L API is deprecated since *years* in the kernel. V4L2 is the
> > standard for Linux.
> > Still, some driver, like yours (gspca) did not upgraded to the new API.
> > This is mostly a packaging issue; installing the package
> > "libpt-2.3-plugins-v4l" provide V4L support.
> When I wrote "v4l" above, I was really thinking v4l2 as I didn't expect
> that a driver which was just merged in the mainline would still use
> v4l... but indeed I only installed libpt-2.3-plugins-v4l2 from ekiga's
> snapshots. Bizarrely, I did get video in ekiga from the webcam.
I wonder if there is some compatibility library in between V4l and V4L2
in ubuntu. Not sure...
> > But adding this support will pop up 2 choices for most webcams users:
> > V4L and V4L2, which doesn't mean anything for the average user...
> I see.
> > Please report a bug against your driver which do not support the
> > standard for Linux.
> Hmm it strikes that this should be already known since the driver was
> just merged to mainline.
Webcam is one of the nightmare of Linux users, e.g.:
http://brainstorm.ubuntu.com/idea/97/ is #11 most popular ideas ever...
> > > - locking assertion failures on console in libxcb :-/
> > Please try the latest package, or report the bug upstream.
> Well it was the latest this morning! Sure, I'll report the bug.
I wish I had more time for Ekiga... Thank you!
> > > - icon is almost exactly the same as empathy in notification area
> > Well, we have those icons since something like early 2007 in our SVN...
> > They are easy to understand and based on traffic light. There is no copy
> > here.
> It might been in your SVN for so long, it's not what's used in the
> current version of the Ubuntu ekiga packages, and I could until now
> distinguish ekiga from gossip / empathy. :-/
Well, Ubuntu used its own set of icon for Ekiga. Nothing prevent to
change the new icons in Ubuntu, and maybe propose it to upstream?
If we consider the question deeply, I personally do think dedicated
clients to one protocol like Gossip or Ekiga is the right way to go.
Empathy brings compatibility to the GNU/Linux desktop at the price of
reducing a rich feature set to a small set of one to one feature.
I hope one day, one standard will win, no matter if it is SIP, or XMPP,
or some mix of them. Several protocols for the same type of feature is
just bad and hurts usability deeply. The future of SIP, or XMPP, is some
kind of desktop and internet/mobile integrated groupware.
Having a distinguish set of icon for each application is just a
workaround for a need that cannot really get its satisfaction.
Please consider the real potential of SIP or XMPP and help bring those
rich features integrated in the desktop. I do believe this will be a
greater help in the long run.
> > > - "Chat" menu to "Quit" is weird, probably not GNOME HIG compliant
> > It is compliant, see:
> > http://library.gnome.org/devel/hig-book/stable/menus-standard.html.en#the-file-menu
> > especially:
> > "If your application does not operate on documents, name this item for
> > the type of object it displays. For example, many games should have a
> > Game instead of a File menu. However, place the Quit menu item last on
> > this menu nonetheless."
> The Game example makes sense to me, but I still feel disturbed by Chat
> > Quit, especially since I don't use ekiga for "chat" but really for
> "calls" or "conferences", but I understand why you settled for Chat and
> put Quit in there. Still feels kind of weird to me. :-/
Ekiga 3.0 aims to provide audio calls, video calls or text conversation
with presence support. You should consider SIP for what it is: a
protocol for rich instant communication using several medias (text,
audio and video). SIP aims to do the same features as XMPP.
"Chat" seems the appropriate word for what ekiga 3.0 will be able to do.
"Call" do not sounds right for text messages.
It is an artificial definition to try to separate XMPP client like
gossip for "chat" and SIP client like EKiga for "Call".
The issue is we have several protocols aiming the same set of feature,
because there is only one need: to chat with contacts, using several
ways: text, audio and video (and maybe even more in the future...).
> > > - "Account" menu in Accounts window doesn't look like a menu (no
> > > underscore); not easy to see where to add an account
> > This has been fixed, please test last package.
> (it was the last one when I tried ;-)
> But I'll give it another shot.
> > > - When actually using SIP: "Cannot copy from empty list to master RTP
> > > session list" error
> > I reported it here, and it is fixed:
> > http://bugzilla.gnome.org/show_bug.cgi?id=545366
> > Please try the new packages...
> Same remark...
> Loïc Minier
> Ubuntu-mobile mailing list
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Me joindre en téléphonie IP / vidéoconférence ?
Logiciel de VoIP Ekiga : http://www.ekiga.org
Ubuntu-mobile mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile