Bug#691261: Phone PBX rejects refresh registration because of incorrect "expires" field in Contact header

[Eugen Dedu]

On 23/10/12 21:41, Ramón García Fernández wrote:
> I looked at the source of latest libopal, and it looks like it behaves in the same way. But I did not test it
>
> -----Mensaje original-----
> De: Eugen Dedu [mailto:Eugen.Dedu at pu-pm.univ-fcomte.fr]
> Enviado el: martes, 23 de octubre de 2012 21:19
> Para: Robert Jongbloed
> CC: Ramón García Fernández
> Asunto: Phone PBX rejects refresh registration because of incorrect "expires" field in Contact header
>
> Hi Robert,
>
> Here is a bug report with a patch, could you please take a look?

Here is Robert's answer:

This looks like the server is confused about REGISTER and SUBSCRIBE. 
According to spec:

       8. The registrar returns a 200 (OK) response.  The response MUST
          contain Contact header field values enumerating all current
          bindings.  Each Contact value MUST feature an "expires"
          parameter indicating its expiration interval chosen by the
          registrar.  The response SHOULD include a Date header field.

so what the registrar sends back is supposed to be the expiration 
interval, but what it is sending is the "time to go" in that interval, 
which is what is sent in a SUBSCRIBE.

That said, as usual,we have to work around the issues of other people. 
Unfortunately, the patch from Ramon, is form an older version of OPAL 
and can no longer be applied,

There is a fix, but it is too hard for me to do right now, maybe when I 
get back home. Though, the only consequence is a couple of extra packets 
as it gets a "too short" error and retries.

*Robert Jongbloed*
OPAL/OpenH323/PTLib Architect and Co-founder.
/Traveling, so email responses may be slow!/

-- 
Eugen