RFC5626 non-standard behaviour

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

 



Hi,

I'm trying to use pjsip support of RFC5626 for TCP and I found the following inconsistencies with the standard:

1. PJSIP keepalives are CRLF instead of the recommended CRLFCRLF
2. PJSIP doesn't process the pong response from the server to decide if the connection is broken or not.
3. keep_alive timeout for TCP is always set 90 seconds, and the value of acc.ka_interval in pjsua is only used for UDP
4. Any activity on the TCP transport resets the keep_alive timer and it shouldn't
5. There are no method to request sending the keepalive from the application layer (this is needed to send keepalives from an iphone app while in background)

Do you agree with these issues or did I misunderstand something?  Are there any plans to implement it according to the spec?

Thank you,
G.

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx


[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