RFC5626 non-standard behaviour

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

 



On Thu, Oct 6, 2011 at 3:15 AM, Gustavo Garcia Bernardo <ggb at tid.es> wrote:
> Thank you very much for the info Benny.
>
> I think the problematic points for interoperability are 3 (should set Flow-Timer header received from server) and 4 (because server will receive less keepalives than expected and could consider the connection as failed). ?I'll probably try to implement then and send a patch for your consideration.
>

One of the easier workaround is to shorten the keep alive interval to
say slightly less than half of what your server setting is, I think
that should cover problem no 3 and 4.

> I tried to use pjsip_endpt_send_raw_to_uri and got an assertion fail in os_core_unix.c Ln 1256:
> ?pj_assert(mutex->owner == pj_thread_this());
>
> Any idea of what is the problem?
>

There's no way to tell without seeing the stack trace.

 Benny



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux