[reSIProcate] DnsResult blacklistLast,greylistLast question.

palladin p-aladin at yandex.ru
Thu Nov 28 03:00:40 CST 2013


Dear resiprocate devels,
resiprocate version 1.8.8

I use proxy,built above resip stack. In particular, there are a fiew 
intermediate proxy servers: N1,N2,N3.

I've met next issue:
1) there is an active session.
2) some client starts one more session,sending malformed sip message to 
proxy1, proxy1 retransmits that message to Proxy2 and proxy2 responds 
with 500 Server internal error. Proxy1 tries to retransmit that message 
several times and after the last one it penalizes given transport by 
black listing.
3) At the same time session from item1 has not been finished yet. If any 
participant from session1 will send any sip message - TransportSelector 
will generate TransportFailure or TCP transport will be selected if it 
is configured - as result session1 becomes broken/hung.

I think UAC penalization - is good idea,but proxy penalization leads to 
undefined behaviour.

Considering this I  would like to ask a few questions,if you don't mind:
1) Is it possible to add some exception list to 
DnsResult::blackListLast/DnsResult::greyListLast stuff?
2) Could you please take a look on provided patch,which provides some 
kind of solution?

Appreciate in advance.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: penalty_exception.patch
Type: text/x-patch
Size: 105786 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20131128/af1e6376/attachment.bin>


More information about the resiprocate-devel mailing list