Re: [Ekiga-devel-list] Restoring presence in the SIP code

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

On 23/09/10 15:28, Julien Puydt wrote:
> Le 23/09/2010 15:18, Eugen Dedu a écrit :
> > On 23/09/10 15:09, Julien Puydt wrote:
> > > My guess is that piece of code in sip-endpoint.cpp (around line 1045) :
> > > SIPURL sip_uri = SIPURL (user);
> > > sip_uri.Sanitise (SIPURL::ExternalURI);
> > > std::string _uri = sip_uri.AsString ();
> > > doesn't do what it is supposed to do!
> >
> > Is it a bug in opal, or in ekiga, or is it normal to have such an URI?
>
> I think it is a bug in the SIPURL class... I really think _uri should
> end up as "sip:foo ekiga net".

If you are sure, please contact Robert.

> > We have two choices:
> > - either we fix this (with the patch in the previous e-mail, which is a
> > hack)
>
> It is a little ugly, too.

But it allows to create an *unstable* release...

> > - or we wait someone :o) to write ekiga code to use the current API, but
> > there is no known time bound limit here
>
> Where is the new api documented?

I do not know, I have looked at http://www.opalvoip.org/docs/opal-v3_8, 
but I have not found useful information.

You can ask Robert, or look yourself in the samples/ directory of opal 
(do some grep).  I noticed that now contacts (in roster) are not treated 
individually, but as a group.

--
Eugen