B2BuaHelper: Problem while linking & unlinking sip sessions

[AyhanKemal]

Hi all,

In our application we use B2buaHelper for link, unlink our
SipSessions.

The flow is as described below:



1- Call is setup (ClientA<->ClientB) with 2 sipSessions, lets say SS1
(ClientA <-> SipApp) and SS2 (SipApp<->ClientB)
(1478de0c... -> SS1, 33103999... -> SS2)


2011-03-08 15:44:42,712 DEBUG
[org.mobicents.servlet.sip.message.B2buaHelperImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-8)
(1478de0c:MjE4NzIwNzJiN2Y1OWVlNDUwMjE2N2ZhZDRjNDY2ZTk.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity) tied to session
(33103999_b61a9482_ea2cdf3a-2233-4c70-9648-0d61bd943f7a:c60578801acf59b1...@192.168.20.107:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity)
2011-03-08 15:44:42,712 DEBUG
[org.mobicents.servlet.sip.message.B2buaHelperImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-8)
(33103999_b61a9482_ea2cdf3a-2233-4c70-9648-0d61bd943f7a:c60578801acf59b1...@192.168.20.107:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity) tied to session
(1478de0c:MjE4NzIwNzJiN2Y1OWVlNDUwMjE2N2ZhZDRjNDY2ZTk.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity)



2- When another invite comes from a sipclient for call transfer (Lets
say a new SipSession as SS3) we want to transfer our call
as SS3<->SS2 and still the same call (ClientA<->ClientB). So we need
to unlink sipSessions (SS1, SS2) and invalidate SS1.
(7b35ef21... -> SS3)



if (<SS1>.isValid() && <SS1>.getState() !=
SipSession.State.TERMINATED) {
if (logger.isDebugEnabled()) {
logger.debug(" for Call Id: " + callId + " SipSession:
" + <SS1>.getId()
+ " is valid. Unlink and invalidate it.");
}
//Unlink sipSession
helper.unlinkSipSessions(<SS1>);
}
...
<SS1>.invalidate();
...
if (incomingSession.isValid()) {
//Invalidate Terminated SipSession
incomingSession.invalidate();
}
...

2011-03-08 15:45:17,050 DEBUG
[org.mobicents.servlet.sip.core.session.SipSessionImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-17) readyToInvalidate flag is set to
true
2011-03-08 15:45:17,051 DEBUG
[org.mobicents.servlet.sip.core.session.SipSessionImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-17) the following sip session
(1478de0c:MjE4NzIwNzJiN2Y1OWVlNDUwMjE2N2ZhZDRjNDY2ZTk.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity) has its state updated to TERMINATED
2011-03-08 15:45:17,051 DEBUG
[org.mobicents.servlet.sip.core.session.SipSessionImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-17) the following sip session
(1478de0c:MjE4NzIwNzJiN2Y1OWVlNDUwMjE2N2ZhZDRjNDY2ZTk.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity) is ready to be invalidated
2011-03-08 15:45:17,051 DEBUG
[org.mobicents.servlet.sip.core.session.SipSessionImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-17) the following sip session
(1478de0c:MjE4NzIwNzJiN2Y1OWVlNDUwMjE2N2ZhZDRjNDY2ZTk.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity) has its state updated to TERMINATED

2011-03-08 15:45:17,112 DEBUG
[org.mobicents.servlet.sip.message.B2buaHelperImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-17) Linked Session found :
(33103999_b61a9482_ea2cdf3a-2233-4c70-9648-0d61bd943f7a:c60578801acf59b1...@192.168.20.107:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity) for this session
(1478de0c:MjE4NzIwNzJiN2Y1OWVlNDUwMjE2N2ZhZDRjNDY2ZTk.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity)
2011-03-08 15:45:17,112 DEBUG [tr.com.argela.vcc.fsm.SessionUpdate]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-17) for Call Id: 4
SipSession:
(33103999_b61a9482_ea2cdf3a-2233-4c70-9648-0d61bd943f7a:c60578801acf59b1...@192.168.20.107:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity) is valid. Unlink and invalidate it.
2011-03-08 15:45:17,112 INFO
[org.mobicents.servlet.sip.core.session.SipSessionImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-17) Invalidating the sip session
(1478de0c:MjE4NzIwNzJiN2Y1OWVlNDUwMjE2N2ZhZDRjNDY2ZTk.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity)
2011-03-08 15:45:17,113 DEBUG
[org.mobicents.servlet.sip.core.session.SipManagerDelegate] (Mobicents-
SIP-Servlets-UDPMessageChannelThread-17) Removing a sip session with
the key :
(1478de0c:MjE4NzIwNzJiN2Y1OWVlNDUwMjE2N2ZhZDRjNDY2ZTk.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity)



3- Then link sipSessions (SS3, SS2) for transferred call that is
ongoing for ClientA and ClientB both without any interruption.

helper.linkSipSessions(<SS2>, <SS3>);


2011-03-08 15:45:17,116 DEBUG
[org.mobicents.servlet.sip.message.B2buaHelperImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-17)
(7b35ef21:ZDQ5NjE0YTYzM2M3OGNiNDMxYmY4OTI2NWZiYzA0OGU.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity) tied to session
(33103999_b61a9482_ea2cdf3a-2233-4c70-9648-0d61bd943f7a:c60578801acf59b1...@192.168.20.107:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity)
2011-03-08 15:45:17,116 DEBUG
[org.mobicents.servlet.sip.message.B2buaHelperImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-17)
(33103999_b61a9482_ea2cdf3a-2233-4c70-9648-0d61bd943f7a:c60578801acf59b1...@192.168.20.107:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity) tied to session
(7b35ef21:ZDQ5NjE0YTYzM2M3OGNiNDMxYmY4OTI2NWZiYzA0OGU.:ea2cdf3a-2233-4c70-9648-0d61bd943f7a:Voice
Call Continuity)


4-

A- When we get a BYE request FROM ClientA (for SS3) we need to find
SS2 to send BYE request by the code below. After execution of the code
<SS2> sipSession is null. So we cannot send BYE request to this
session.

B2buaHelper helper = request.getB2buaHelper();
SipSession <SS3> = request.getSession();
SipSession <SS2> = helper.getLinkedSession(<SS3>); //<SS2> is null


B- When we get a BYE request FROM ClientB (for SS2) linkedSession
SS3 CAN BE FOUND!!! with the same way. Then the application sends BYE
request to ClientA
and for the 200-OK response the application tries to send this
response to ClientB. We normally use pendingMessages for SS2 but we
have a null pointer exception
before that. It seems that sipStack invalidates out appSession &
sipSession without our intervention. The related parts of the server
log is below,



2011-03-08 17:09:12,372 DEBUG
[tr.com.argela.vcc.servlets.VccCallHandler] (Mobicents-SIP-Servlets-
UDPMessageChannelThread-59) For Call Id: 6 Caller:
01514...@192.168.2.176 has a leg object
2011-03-08 17:09:12,372 DEBUG [tr.com.argela.vcc.fsm.CallReleased]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Success response
received for Call Id: 6 for BYE appSessionId: (e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity) and Sip Call Id:
MTM5ZDBiMzM2NWEzYjQ5OTdiNzdjZjVmMGI0MmRjNTk.
2011-03-08 17:09:12,373 INFO
[org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Invalidating the
following sip application session (e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity)
2011-03-08 17:09:12,373 INFO
[org.mobicents.servlet.sip.core.session.SipSessionImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-59) Invalidating the sip session
(61695038_b61a9482_e3b18293-86b2-4204-b9ac-1150c72689eb:
0718d2f91bd32824...@192.168.20.107:e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity)
2011-03-08 17:09:12,373 DEBUG
[org.mobicents.servlet.sip.core.session.SipManagerDelegate] (Mobicents-
SIP-Servlets-UDPMessageChannelThread-59) Removing a sip session with
the key : (61695038_b61a9482_e3b18293-86b2-4204-b9ac-1150c72689eb:
0718d2f91bd32824...@192.168.20.107:e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity)
2011-03-08 17:09:12,373 DEBUG
[org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Trying to remove
sip session SessionBasedClusteredSipSession[id:
61695038_b61a9482_e3b18293-86b2-4204-b9ac-1150c72689eb:
0718d2f91bd32824...@192.168.20.107 lastAccessedTime:
1299596915807 version: 3 lastOutdated: 0]
2011-03-08 17:09:12,373 DEBUG
[org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Removed sip
session (61695038_b61a9482_e3b18293-86b2-4204-b9ac-1150c72689eb:
0718d2f91bd32824...@192.168.20.107:e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity) from sip app session
(e3b18293-86b2-4204-b9ac-1150c72689eb:Voice Call Continuity)
2011-03-08 17:09:12,373 DEBUG
[org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Sip application
session already invalidated (e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity)
2011-03-08 17:09:12,373 DEBUG
[org.mobicents.servlet.sip.core.session.SipSessionImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-59) 1 ongoing transactions still
present in the following sip session
(61695038_b61a9482_e3b18293-86b2-4204-b9ac-1150c72689eb:
0718d2f91bd32824...@192.168.20.107:e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity) on invalidation
2011-03-08 17:09:12,373 DEBUG
[org.mobicents.servlet.sip.message.TransactionApplicationData]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) cleaning up the
application data
2011-03-08 17:09:12,373 DEBUG
[gov.nist.javax.sip.stack.SIPTransaction] (Mobicents-SIP-Servlets-
UDPMessageChannelThread-59) Transaction:setState 5
gov.nist.javax.sip.stack.SIPServerTransaction@c54db4bd branchID =
z9hG4bK-d8754z-1c1eab5ab65b4973-1---d8754z-0718dzsd isClient = false
2011-03-08 17:09:12,374 DEBUG
[gov.nist.javax.sip.stack.SIPTransaction] (Mobicents-SIP-Servlets-
UDPMessageChannelThread-59) [CommonLoggerLog4j.java:59]
[CommonLogger.java:108][SIPTransaction.java:595]
[SIPServerTransaction.java:1575][SIPServerTransaction.java:1685]
[SipSessionImpl.java:823][ClusteredSipSession.java:456]
[SipApplicationSessionImpl.java:572][SipApplicationSessionImpl.java:
545][ClusteredSipApplicationSession.java:442][CallReleased.java:146]
[VccCallHandler.java:573][SipServlet.java:268][SipServlet.java:327]
[MessageDispatcher.java:326][ResponseDispatcher.java:355]
[DispatchTask.java:55][ResponseDispatcher.java:386]
[SipApplicationDispatcherImpl.java:840][EventScanner.java:296]
[SipProviderImpl.java:196][DialogFilter.java:1480]
[SIPClientTransaction.java:643][SIPClientTransaction.java:550]
[SIPClientTransaction.java:1550][UDPMessageChannel.java:583]
[UDPMessageChannel.java:492][UDPMessageChannel.java:297][Thread.java:
662]
2011-03-08 17:09:12,374 DEBUG [gov.nist.javax.sip.stack.SIPDialog]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Setting dialog
state for
gov.nist.javax.sip.stack.ConfirmedReplicationSipDialog@454c8132newState
= 3
2011-03-08 17:09:12,374 DEBUG [gov.nist.javax.sip.stack.SIPDialog]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59)
[CommonLoggerLog4j.java:59][CommonLogger.java:108][SIPDialog.java:1411]
[AbstractHASipDialog.java:633][SIPDialog.java:2078]
[SipSessionImpl.java:865][ClusteredSipSession.java:456]
[SipApplicationSessionImpl.java:572][SipApplicationSessionImpl.java:
545][ClusteredSipApplicationSession.java:442][CallReleased.java:146]
[VccCallHandler.java:573][SipServlet.java:268][SipServlet.java:327]
[MessageDispatcher.java:326][ResponseDispatcher.java:355]
[DispatchTask.java:55][ResponseDispatcher.java:386]
[SipApplicationDispatcherImpl.java:840][EventScanner.java:296]
[SipProviderImpl.java:196][DialogFilter.java:1480]
[SIPClientTransaction.java:643][SIPClientTransaction.java:550]
[SIPClientTransaction.java:1550][UDPMessageChannel.java:583]
[UDPMessageChannel.java:492][UDPMessageChannel.java:297][Thread.java:
662]
2011-03-08 17:09:12,374 DEBUG [gov.nist.javax.sip.stack.SIPDialog]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59)
gov.nist.javax.sip.stack.ConfirmedReplicationSipDialog@454c8132 old
dialog state is Confirmed Dialog
2011-03-08 17:09:12,374 DEBUG [gov.nist.javax.sip.stack.SIPDialog]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59)
gov.nist.javax.sip.stack.ConfirmedReplicationSipDialog@454c8132 New
dialog state is Terminated Dialog
2011-03-08 17:09:12,374 DEBUG
[org.mobicents.servlet.sip.message.TransactionApplicationData]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) cleaning up the
application data
2011-03-08 17:09:12,374 DEBUG
[org.mobicents.servlet.sip.message.SipServletMessageImpl] (Mobicents-
SIP-Servlets-UDPMessageChannelThread-59) Setting transaction null on
message BYE sip:192.168.20.107:5080;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.20.107:5065;branch=z9hG4bK-
d8754z-1c1eab5ab65b4973-1---d8754z-0718dzsd

Via: SIP/2.0/UDP 192.168.20.107:5060;branch=z9hG4bK-
d8754z-1c1eab5ab65b4973-1---d8754z-0718d

Via: SIP/2.0/UDP 192.168.2.48:5060;branch=z9hG4bK-
d8754z-1c1eab5ab65b4973-1---d8754z-;rport=5060;received=192.168.2.48

Max-Forwards: 69

Contact: <sip:+1234015...@192.168.2.48>

To: "Ayhan Kemal" <sip:
01514...@192.168.2.176>;tag=61695038_b61a9482_e3b18293-86b2-4204-
b9ac-1150c72689eb

From: <sip:+1234015...@192.168.2.48>;tag=6370131b

Call-ID: 0718d2f91bd32824...@192.168.20.107

CSeq: 2 BYE

User-Agent: X-Lite release 1103d stamp 53117

Reason: SIP;description="User Hung Up"

Content-Length: 0




2011-03-08 17:09:12,374 INFO
[org.mobicents.servlet.sip.core.session.SipSessionImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-59) Invalidating the sip session
(9d337b7a:MTM5ZDBiMzM2NWEzYjQ5OTdiNzdjZjVmMGI0MmRjNTk.:e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity)
2011-03-08 17:09:12,374 DEBUG
[org.mobicents.servlet.sip.core.session.SipManagerDelegate] (Mobicents-
SIP-Servlets-UDPMessageChannelThread-59) Removing a sip session with
the key :
(9d337b7a:MTM5ZDBiMzM2NWEzYjQ5OTdiNzdjZjVmMGI0MmRjNTk.:e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity)
2011-03-08 17:09:12,374 DEBUG
[org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Trying to remove
sip session SessionBasedClusteredSipSession[id:
9d337b7a:MTM5ZDBiMzM2NWEzYjQ5OTdiNzdjZjVmMGI0MmRjNTk.
lastAccessedTime: 1299596933717 version: 2 lastOutdated: 0]
2011-03-08 17:09:12,374 DEBUG
[org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Removed sip
session
(9d337b7a:MTM5ZDBiMzM2NWEzYjQ5OTdiNzdjZjVmMGI0MmRjNTk.:e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity) from sip app session
(e3b18293-86b2-4204-b9ac-1150c72689eb:Voice Call Continuity)
2011-03-08 17:09:12,374 DEBUG
[org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Sip application
session already invalidated (e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity)
2011-03-08 17:09:12,374 DEBUG
[org.mobicents.servlet.sip.core.session.SipSessionImpl] (Mobicents-SIP-
Servlets-UDPMessageChannelThread-59) 1 ongoing transactions still
present in the following sip session
(9d337b7a:MTM5ZDBiMzM2NWEzYjQ5OTdiNzdjZjVmMGI0MmRjNTk.:e3b18293-86b2-4204-
b9ac-1150c72689eb:Voice Call Continuity) on invalidation
2011-03-08 17:09:12,374 DEBUG
[org.mobicents.servlet.sip.message.TransactionApplicationData]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) cleaning up the
application data
2011-03-08 17:09:12,374 DEBUG
[gov.nist.javax.sip.stack.SIPTransaction] (Mobicents-SIP-Servlets-
UDPMessageChannelThread-59) Transaction:setState 5
gov.nist.javax.sip.stack.SIPClientTransaction@287310ae branchID =
z9hG4bKe3b18293-86b2-4204-b9ac-1150c72689eb_b61a9482_1136074473395103
isClient = true
2011-03-08 17:09:12,374 DEBUG
[gov.nist.javax.sip.stack.SIPTransaction] (Mobicents-SIP-Servlets-
UDPMessageChannelThread-59) [CommonLoggerLog4j.java:59]
[CommonLogger.java:108][SIPTransaction.java:595]
[SIPClientTransaction.java:1372][SIPClientTransaction.java:1398]
[SipSessionImpl.java:823][ClusteredSipSession.java:456]
[SipApplicationSessionImpl.java:572][SipApplicationSessionImpl.java:
545][ClusteredSipApplicationSession.java:442][CallReleased.java:146]
[VccCallHandler.java:573][SipServlet.java:268][SipServlet.java:327]
[MessageDispatcher.java:326][ResponseDispatcher.java:355]
[DispatchTask.java:55][ResponseDispatcher.java:386]
[SipApplicationDispatcherImpl.java:840][EventScanner.java:296]
[SipProviderImpl.java:196][DialogFilter.java:1480]
[SIPClientTransaction.java:643][SIPClientTransaction.java:550]
[SIPClientTransaction.java:1550][UDPMessageChannel.java:583]
[UDPMessageChannel.java:492][UDPMessageChannel.java:297][Thread.java:
662]
2011-03-08 17:09:12,375 DEBUG
[org.mobicents.servlet.sip.message.TransactionApplicationData]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) cleaning up the
application data
2011-03-08 17:09:12,375 DEBUG
[org.mobicents.servlet.sip.message.SipServletMessageImpl] (Mobicents-
SIP-Servlets-UDPMessageChannelThread-59) Setting transaction null on
message BYE sip:01514...@192.168.2.176:5060 SIP/2.0

CSeq: 1 BYE

From: "dtf" <sip:
08502...@turktelekom.com.tr>;tag=40209284_b61a9482_e3b18293-86b2-4204-
b9ac-1150c72689eb

To: "Ayhan Kemal" <sip:01514...@192.168.2.176>;tag=9d337b7a

Call-ID: MTM5ZDBiMzM2NWEzYjQ5OTdiNzdjZjVmMGI0MmRjNTk.

Max-Forwards: 70

Route: <sip:192.168.20.107:5065;transport=udp;lr>

Route: <sip:192.168.20.107:5060;transport=udp;lr>

Via: SIP/2.0/UDP 192.168.20.107:5080;branch=z9hG4bKe3b18293-86b2-4204-
b9ac-1150c72689eb_b61a9482_1136074473395103

Content-Length: 0




2011-03-08 17:09:12,375 DEBUG
[org.mobicents.servlet.sip.core.session.SipManagerDelegate] (Mobicents-
SIP-Servlets-UDPMessageChannelThread-59) Removing a sip application
session with the key : (e3b18293-86b2-4204-b9ac-1150c72689eb:Voice
Call Continuity)
2011-03-08 17:09:12,375 INFO
[org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) The following sip
application session (e3b18293-86b2-4204-b9ac-1150c72689eb:Voice Call
Continuity) has been invalidated
2011-03-08 17:09:12,375 DEBUG [tr.com.argela.vcc.fsm.CallReleased]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) For Call Id: 6
SipApplicationSession: (e3b18293-86b2-4204-b9ac-1150c72689eb:Voice
Call Continuity) is invalidated.
2011-03-08 17:09:12,375 ERROR
[tr.com.argela.vcc.servlets.VccCallHandler] (Mobicents-SIP-Servlets-
UDPMessageChannelThread-59) Exception occured:
java.lang.NullPointerException
at
org.mobicents.servlet.sip.message.B2buaHelperImpl.getPendingMessages(B2buaHelperImpl.java:
565)
at tr.com.argela.vcc.fsm.CallReleased.callAnswered(CallReleased.java:
88)
at
tr.com.argela.vcc.servlets.VccCallHandler.doSuccessResponse(VccCallHandler.java:
573)
at javax.servlet.sip.SipServlet.doResponse(SipServlet.java:268)
at javax.servlet.sip.SipServlet.service(SipServlet.java:327)
at
org.mobicents.servlet.sip.core.dispatchers.MessageDispatcher.callServlet(MessageDispatcher.java:
326)
at org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher
$1.dispatch(ResponseDispatcher.java:355)
at
org.mobicents.servlet.sip.core.dispatchers.DispatchTask.dispatchAndHandleExceptions(DispatchTask.java:
55)
at
org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher.dispatchMessage(ResponseDispatcher.java:
386)
at
org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl.processResponse(SipApplicationDispatcherImpl.java:
840)
at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:
296)
at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:
196)
at gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:
1480)
at
gov.nist.javax.sip.stack.SIPClientTransaction.nonInviteClientTransaction(SIPClientTransaction.java:
643)
at
gov.nist.javax.sip.stack.SIPClientTransaction.processResponse(SIPClientTransaction.java:
550)
at
gov.nist.javax.sip.stack.SIPClientTransaction.processResponse(SIPClientTransaction.java:
1550)
at
gov.nist.javax.sip.stack.UDPMessageChannel.processMessage(UDPMessageChannel.java:
583)
at
gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:
492)
at
gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:
297)
at java.lang.Thread.run(Thread.java:662)
2011-03-08 17:09:12,376 DEBUG
[org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-59) Not forwarding the
response statefully. It was either an endpoint or a B2BUA, ie an
endpoint too SIP/2.0 200 OK


...
...
...

2011-03-08 17:09:12,710 ERROR
[org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl]
(Mobicents-SIP-Servlets-UDPMessageChannelThread-60) Unexpected
exception while processing request BYE sip:
192.168.20.107:5080;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.20.107:5065;branch=z9hG4bK-
d8754z-1c1eab5ab65b4973-1---d8754z-0718dzsd

Via: SIP/2.0/UDP 192.168.20.107:5060;branch=z9hG4bK-
d8754z-1c1eab5ab65b4973-1---d8754z-0718d

Via: SIP/2.0/UDP 192.168.2.48:5060;branch=z9hG4bK-
d8754z-1c1eab5ab65b4973-1---d8754z-;rport=5060;received=192.168.2.48

Max-Forwards: 69

Contact: <sip:+1234015...@192.168.2.48>

To: "Ayhan Kemal" <sip:
01514...@192.168.2.176>;tag=61695038_b61a9482_e3b18293-86b2-4204-
b9ac-1150c72689eb

From: <sip:+1234015...@192.168.2.48>;tag=6370131b

Call-ID: 0718d2f91bd32824...@192.168.20.107

CSeq: 2 BYE

User-Agent: X-Lite release 1103d stamp 53117

Reason: SIP;description="User Hung Up"

Content-Length: 0




org.mobicents.servlet.sip.core.dispatchers.DispatcherException: Cannot
find the corresponding sip application session to this subsequent
request BYE sip:192.168.20.107:5080;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.20.107:5065;branch=z9hG4bK-
d8754z-1c1eab5ab65b4973-1---d8754z-0718dzsd

Via: SIP/2.0/UDP 192.168.20.107:5060;branch=z9hG4bK-
d8754z-1c1eab5ab65b4973-1---d8754z-0718d

Via: SIP/2.0/UDP 192.168.2.48:5060;branch=z9hG4bK-
d8754z-1c1eab5ab65b4973-1---d8754z-;rport=5060;received=192.168.2.48

Max-Forwards: 69

Contact: <sip:+1234015...@192.168.2.48>

To: "Ayhan Kemal" <sip:
01514...@192.168.2.176>;tag=61695038_b61a9482_e3b18293-86b2-4204-
b9ac-1150c72689eb

From: <sip:+1234015...@192.168.2.48>;tag=6370131b

Call-ID: 0718d2f91bd32824...@192.168.20.107

CSeq: 2 BYE

User-Agent: X-Lite release 1103d stamp 53117

Reason: SIP;description="User Hung Up"

Content-Length: 0



, it may already have been invalidated or timed out
at
org.mobicents.servlet.sip.core.dispatchers.SubsequentRequestDispatcher.dispatchMessage(SubsequentRequestDispatcher.java:
208)
at
org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl.processRequest(SipApplicationDispatcherImpl.java:
701)
at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:
230)
at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:
196)
at gov.nist.javax.sip.DialogFilter.processRequest(DialogFilter.java:
1303)
at
gov.nist.javax.sip.stack.SIPServerTransaction.processRequest(SIPServerTransaction.java:
847)
at
gov.nist.javax.sip.stack.UDPMessageChannel.processMessage(UDPMessageChannel.java:
540)
at
gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:
492)
at
gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:
297)
at java.lang.Thread.run(Thread.java:662)

[Jean Deruelle]

Can you open an issue at http://code.google.com/p/mobicents/issues/entry?template=Mobicents%20Sip%20Servlets%20Template ?

[Jean Deruelle]

please attach the full server.log and jain sip log at DEBUG level for 1 complete failing call so that we can trace what is happening

Thanks 

Jean

[Ayhan Kemal Baykal]

Issue opened as:

Issue 2422: B2BuaHelper problem while link - unnlink sessions

2011/3/9 Jean Deruelle <jean.d...@gmail.com>:

[Jean Deruelle]

Thanks, we have quite a backlog of opened issues but will try to catch up ASAP