Issue 2362 in mobicents: Forked responses are not passed SipServlet

[mobicents]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 2362 by alexander.kozlov.IV: Forked responses are not passed  
SipServlet
http://code.google.com/p/mobicents/issues/detail?id=2362

What steps will reproduce the problem?
I tried to write unit test when I sent INVITE to forked proxy,
but responses with different to-tag are marked as Retransmission.

DEBUG Mobicents-SIP-Servlets-UDPMessageChannelThread-3  
org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl.processResponse(SipApplicationDispatcherImpl.java:782)  
- Response SIP/2.0 180 Ringing
To: <sip:forking@127.0.0.1:5056>;tag=tag2
Via: SIP/2.0/UDP  
127.0.0.1:5070;branch=z9hG4bK58bcef55-87bc-440f-90ba-3c0d3212438f_8a1e29b3_16255907
CSeq: 1 INVITE
Call-ID: 16d9b66dffc37c0fc83000a9582b43e4@127.0.0.1
From:  
<sip:1@127.0.0.1:5070>;tag=38143681_8a1e29b3_58bcef55-87bc-440f-90ba-3c0d3212438f
Contact: <sip:forking@127.0.0.1:5056>
Content-Length: 0


DEBUG Mobicents-SIP-Servlets-UDPMessageChannelThread-3  
org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl.processResponse(SipApplicationDispatcherImpl.java:802)  
- is Forked Response false
DEBUG Mobicents-SIP-Servlets-UDPMessageChannelThread-3  
org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl.processResponse(SipApplicationDispatcherImpl.java:803)  
- is Retransmission true

.........................

DEBUG Mobicents-SIP-Servlets-UDPMessageChannelThread-6  
org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl.processResponse(SipApplicationDispatcherImpl.java:782)  
- Response SIP/2.0 200 OK
To: <sip:forking@127.0.0.1:5056>;tag=tag2
Via: SIP/2.0/UDP  
127.0.0.1:5070;branch=z9hG4bK58bcef55-87bc-440f-90ba-3c0d3212438f_8a1e29b3_16255907
CSeq: 1 INVITE
Call-ID: 16d9b66dffc37c0fc83000a9582b43e4@127.0.0.1
From:  
<sip:1@127.0.0.1:5070>;tag=38143681_8a1e29b3_58bcef55-87bc-440f-90ba-3c0d3212438f
Contact: <sip:forking@127.0.0.1:5056>
Content-Length: 0

DEBUG Mobicents-SIP-Servlets-UDPMessageChannelThread-6  
org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl.processResponse(SipApplicationDispatcherImpl.java:802)  
- is Forked Response false
DEBUG Mobicents-SIP-Servlets-UDPMessageChannelThread-6  
org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl.processResponse(SipApplicationDispatcherImpl.java:803)  
- is Retransmission true

I looked one more time, and I found

DEBUG Mobicents-SIP-Servlets-UDPMessageChannelThread-6  
org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher.dispatchMessage(ResponseDispatcher.java:123)  
- application data is null, it means that this is a forked response, please  
enable stack property support for it through  
gov.nist.javax.sip.MAX_FORK_TIME_SECONDS

So, why is it equals to zero by default ?

When I set it to 60, I got all responses as expected...
Is it safe to change this value to non-zero ?

What version of the product are you using? On what operating system?
Mobicents Sip Servlets #1078 r16815.

(Previously I wrote this to Issue 2354, but I decided to create separate  
issue)

Attachments:
        logs.txt  389 KB