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

[Julien Puydt <jpuydt free fr>]

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".

> 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.

> - 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?

Snark