Re: [Ekiga-devel-list] Registrar compliance

Damien Sandras a écrit :
> Le dimanche 06 septembre 2009 à 14:25 +0200, yannick a écrit :
>> Eugen Dedu a écrit :
>>> 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)...
> The problem is that each REGISTER will be tried twice in case of
> failure. There is no dedicated error code for the "too many contacts"
> problem.
> I will perhaps try the automated method only if we can not register for
> a reason which is different than those cases:
> - timeout
> - transport error
> - forbidden

That would be nice.

In the cases we have, there is a 500:
SIP/2.0 500 Service Unavailable
Via: SIP/2.0/UDP;received=;branch=z9hG4bK1c25676e-3a97-de11-8e1e-0022fa93d416;rport=5060

Server: ecomPhoneServer
From: <sip:222365341 hlas 802 cz>;tag=2c0c7d66-3a97-de11-8e1e-0022fa93d416
Call-ID: 705f7c66-3a97-de11-8e1e-0022fa93d416 bradford
To: <sip:222365341 hlas 802 cz>;tag=482965bfc53a503a3279ddc55b12e697.f882
P-Registrar-Error: Too many registered contacts
Content-Length: 0

and a 403:
SIP/2.0 403 Keine RFC1918-IPs erlaubt
Via: SIP/2.0/UDP;branch=z9hG4bK04c5cbff-541d-de11-9f94-001b9e55716e;rport=61224
Server: UI OpenSER
<sip:499419999999 sip 1und1 de>;tag=d88bc7ff-541d-de11-9f94-001b9e55716e
Call-ID: 2cde27fe-541d-de11-9f94-001b9e55716e clarissa-laptop
<sip:499419999999 sip 1und1 de>;tag=329cfeaa6ded039da25ff8cbb8668bd2.ad0d
Content-Length: 0

> I don't think adding a new setting is a good idea. I don't think keeping
> a database of broken registrars is a good idea either.

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