Re: [Ekiga-devel-list] Registrar compliance

Michael Rickmann wrote:
> Yesterday Robert checked commit 23341 into Opal stable which allows
> Ekiga to deal with registrars which do not allow RFC1918-IPs and which
> may possibly help in complex interface situations as reported in
> . To use Opal's
> capabilities I have adapted my patch to Ekiga stable (attached) with
> which you have to place the string %limit into the account name. For me
> it works for a noRFC provider. Regarding the various possibilities of
> non-compliant registrars a simple boolean "is_limited" is rather simple
> minded. On the other hand have we only one method to deal with these
> registrars at the moment. How shall I proceed?

I would say: let's stay with this simple method for the moment.  When
the 2nd case appears, we will think at a general solution.

On master, it tempted limited also when the classical registration did
not work.  Shouldn't we do the same for stable?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]