The following issue has been RESOLVED. 
====================================================================== 
https://bugtracker.iptel.org/view.php?id=70 
====================================================================== 
Reported By:                vbroz
Assigned To:                stefan
====================================================================== 
Project:                    SEMS
Issue ID:                   70
Category:                   SBC
Reproducibility:            always
Severity:                   minor
Priority:                   low
Status:                     resolved
Resolution:                 fixed
Fixed in Version:           master
====================================================================== 
Date Submitted:             2012-02-06 00:47 CET
Last Modified:              2012-02-06 16:28 CET
====================================================================== 
Summary:                    REDIS connection - blacklist CC module - first
(blacklisted in redis) call after redis is disconnected passes SBC
Description: 
playing a bit with redis and blacklist, I've met this behavior with
unavailable redis (please see attached log and pcap)

1) redis is running
2) sems is started -> connects to redis (port 8094) successfully
3) 1st call -> query to redis -> response with "1" -> call blacklisted ->
403 replied => OK
4) kill (or stop using CTRL+C) redis -> redis sends [FIN, ACK], sems only
acknowledge it with [ACK], but does not terminate the connection
5) 2nd call -> SEMS tries to send query to redis [PSH, ACK], but no redis
running -> [RST] -> sems is trying to establish the connection to 8094
again, but...
6) even if the query to redis was not successful, SEMS continue with
processing INVITE and sends it to the destination -> call established and
terminated
7) 3rd call -> SEMS directly responds with 500 Server Internal Error => OK

So the problem is that the first call that comes after "redis termination"
is passed throught SBC and it should not be (because in Redis it is
blacklisted). It should be replied with 500, I guess.

Thanks,
-Vlada 
====================================================================== 

---------------------------------------------------------------------- 
 (0000108) stefan (manager) - 2012-02-06 16:28
 https://bugtracker.iptel.org/view.php?id=70#c108 
---------------------------------------------------------------------- 
should be fixed in: 
81d0a75 b/f: cc redis BL: if server unavailable, refuse (or let through) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2012-02-06 00:47 vbroz          New Issue                                    
2012-02-06 00:47 vbroz          File Added: sems_redis_cc_blacklist.tar.gz      
             
2012-02-06 16:28 stefan         Note Added: 0000108                          
2012-02-06 16:28 stefan         Status                   new => resolved     
2012-02-06 16:28 stefan         Fixed in Version          => master          
2012-02-06 16:28 stefan         Resolution               open => fixed       
2012-02-06 16:28 stefan         Assigned To               => stefan          
======================================================================
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev

Reply via email to