linphone-users
[Top][All Lists]
Advanced

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

Re: [Linphone-users] Truncated response to SIP Options message


From: Klaus Darilion
Subject: Re: [Linphone-users] Truncated response to SIP Options message
Date: Fri, 21 May 2010 15:23:01 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4



Am 21.05.2010 14:52, schrieb damico:
It's jaK!!!  :) ... eXosip's udp keep alive.

udp_tl_keepalive() on eXtl_udp.c

Indeed. IMO that should be fixed in eXosip to send CRLF (which is common practice).

regards
Klaus


Regards

--Michele

Il 21/05/2010 09:27, Keith Jacobs ha scritto:
Interesting,

I do see some messages with CRLF but these four bytes are always
6A-61-4B-00 on port 5060. Could they also be some form of unofficial
message?

Keith

On 20/05/10 18:04, Klaus Darilion wrote:
Hi Keith!

Those 4 bytes are probably CRLFCRLF and are used as light-weight
keep-alive.

Actually CRLF keep alive over UDP is not standardized, but it is a
defacto-standard implemented by many client and supported by almost
any server software.

regards
Klaus

Am 20.05.2010 16:50, schrieb Keith Jacobs:
Whilst sniffing the traffic between several hundred Linphone endpoints
and an Asterisk server I see that whenever the Asterisk sends out a
'SIP
Options' message to any client, the client first responds with an
invalid SIP message (to port 5060 but only 4 bytes of data) followed by
a correct response some 10ms later. Does anyone know what this is all
about? Can it be stopped?

Thanks
Keith

_______________________________________________
Linphone-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/linphone-users


_______________________________________________
Linphone-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/linphone-users


_______________________________________________
Linphone-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/linphone-users



reply via email to

[Prev in Thread] Current Thread [Next in Thread]