[SIP Beyond VoIP] sip-subscribe-rls does not wait for final NOTIFY

Juha Heinanen jh at tutpro.com
Sun Sep 9 08:30:37 CEST 2012


another issue with sip-subscribe-rls is that when control-d is pressed,
it exists immediately after receiving 200 OK to SUBSCRIBE:

012-09-09 09:18:53.347670: SENDING: Packet 5, +0:00:22.984722
192.98.103.10:40870 -(SIP over tcp)-> 192.98.103.10:5060
SUBSCRIBE sip:rls at 127.0.0.1:5082;transport=tcp;alias=192.98.103.1~57248~2 SIP/2.0
Via: SIP/2.0/tcp 192.98.103.10:40870;rport;branch=z9hG4bKPjd8ca68a8-3565-4ddf-ad98-0bf09ccc789b
Max-Forwards: 70
From: <sip:jh at test.fi>;tag=fa2c2f05-1bb7-49fc-bf68-9c5e9b06fe0c
To: <sip:jh-buddies at test.fi>;tag=d2291894436686dad1ecbcc9302b8f5e-5b2d
Contact: <sip:ibdmnpwk at 192.98.103.10:46870;transport=tcp>
Call-ID: dfc91dbf-f80d-4603-98a9-9d1ebea68f23
CSeq: 15197 SUBSCRIBE
Route: <sip:192.98.103.10;transport=tcp;lr;r2=on;ftag=fa2c2f05-1bb7-49fc-bf68-9c5e9b06fe0c>
Route: <sip:192.98.103.1:5070;transport=tcp;lr;r2=on;ftag=fa2c2f05-1bb7-49fc-bf68-9c5e9b06fe0c>
Event: presence
Expires: 0
Accept: multipart/related, application/rlmi+xml, application/pidf+xml
Allow-Events: presence
User-Agent: sipsimple 0.30.0
Content-Length:  0

--

2012-09-09 09:18:53.347799: RECEIVED: Packet 6, +0:00:22.984851
192.98.103.10:5060 -(SIP over tcp)-> 192.98.103.10:40870
SIP/2.0 200 OK
Via: SIP/2.0/tcp 192.98.103.10:40870;rport=40870;branch=z9hG4bKPjd8ca68a8-3565-4ddf-ad98-0bf09ccc789b
From: <sip:jh at test.fi>;tag=fa2c2f05-1bb7-49fc-bf68-9c5e9b06fe0c
To: <sip:jh-buddies at test.fi>;tag=d2291894436686dad1ecbcc9302b8f5e-5b2d
Call-ID: dfc91dbf-f80d-4603-98a9-9d1ebea68f23
CSeq: 15197 SUBSCRIBE
Expires: 0
Contact: <sip:rls at 127.0.0.1:5082;alias=192.98.103.1~57248~2;transport=tcp>
Require: eventlist
Server: OpenXg Presence/XCAP Server  (3.3.1 (x86_64/linux))
Content-Length: 0

--

Unsubscribed from 192.98.103.10:5060;transport=tcp
$

sip-subscribe-rls does not wait until NOTIFY arrives that causes sip
proxy to complain about failing to forward NOTIFY over already
terminated tcp session:

Sep  9 09:18:56 siika /usr/sbin/sip-proxy[31340]: INFO: Routing in-dialog NOTIFY <sip:ibdmnpwk at 192.98.103.10:46870;transport=tcp> from <sip:jh-buddies at test.fi> to <sip:192.98.103.10:40870;transport=tcp>
Sep  9 09:18:56 siika /usr/sbin/sip-proxy[31340]: ERROR: tm [../../forward.h:171]: msg_send: ERROR: tcp_send failed
Sep  9 09:18:56 siika /usr/sbin/sip-proxy[31340]: ERROR: tm [t_fwd.c:1383]: ERROR: t_send_branch: sending request on branch 0 failed
Sep  9 09:18:56 siika /usr/sbin/sip-proxy[31340]: INFO: Failed to relay in-dialog request NOTIFY <sip:ibdmnpwk at 192.98.103.10:46870;transport=tcp>

i haven't checked, but i'm pretty sure that some rfc tells subscriber to
wait until final NOTIFY has arrived and replied to.  at least some other
presence clients that i have tried do so.

-- juha


More information about the SIPBeyondVoIP mailing list