Re: [Ekiga-devel-list] Registrar compliance

Eugen Dedu a écrit :
> yannick wrote:
>> Michael Rickmann a écrit :
>>> 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?
>>> Michael
>> Hi,
>> Is it possible to have this automated?
>> I'm aware of at least 2 registrar answers:
>> Server: ecomPhoneServer
>> P-Registrar-Error: Too many registered contacts
>> (from the above URL)
>> and
>> SIP/2.0 403 Keine RFC1918-IPs erlaubt
>> Server: UI OpenSER
>> (from here: )
> Another idea is to have a database of such registrars.

Where? on the web or inside ekiga? I would prefer something which do not
require user action (fully automated)...

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