Re: NPE: When CANCEL a call

Victor,


Take a look at examples/cancel for the correct flow. You have to send 
200 OK to the cancel so that the transaction state machine on the client 
side of the cancel transaction can match the respose with the request 
and avoid resending the CANCEL.  You have to do this no matter if the 
cancel arives on time or not.


Incidentally, do update your source code again. Jeroen and I have made a 
few changes since yesterday.


Regards

Ranga
Victor Hugo Ros Villegas wrote:

> Hi!
>
> Now there isn't NullPointerException, but when the SIP Client who 
> makes the call  tries to CANCEL before the called user Accepts or 
> Refuses the Invitation -> The next information appears continously on 
> my SLEE command window:
>
> <![CDATA[CANCEL sip:[email protected] <mailto:sip:[email protected]> 
> SIP/2.0
> Via: SIP/2.0/UDP 192.168.0.1:9450 <http://192.168.0.1:9450>;received= 
> 192.168.0.1 <http://192.168.0.1>;rport=1125
> Max-Forwards: 70
> From: "mobicents2" <sip:[email protected] 
> <mailto:sip:[email protected]>>;tag=4a9d0469a70d412883cd5804e505e62
> c;epid=bc2dcff4bc
> To: <sip:[email protected] <mailto:sip:[email protected]>>
> Call-ID: [email protected] 
> <mailto:[email protected]>
> CSeq: 1 CANCEL
> User-Agent: RTC/1.2
> Content-Length: 0
>
> ]]>
> </message>
> 08:53:16,906 INFO  [SbbEntity] invoking event handler onTimerEvent on 
> org.mobice
> nts.slee.services.sip.proxy.JainSipProxySbbImpl ID 
> SbbID[ProxySbb#NIST#1.0] sbbE
> ntity org.mobicents.slee.runtime.SbbEntity@d4f13a currentEvent 
> SleeEventImpl.toS
> tring() = {
>  eventID = 
> EventTypeID[javax.slee.facilities.TimerEvent#javax.slee#1.0], #1
>  activitycontext  = ff8df270f4fc292f:-3e70ad47:10ad4f850cc:-7ff0
>  eventObject = 
> org.mobicents.slee.runtime.facilities.TimerEventImpl@1586ed7
>  address = null
>  activity = 
> org.mobicents.slee.runtime.facilities.NullActivityImpl@121dba8}
> 08:53:18,375 INFO  [STDOUT] <message
> from="192.168.0.1:9450 <http://192.168.0.1:9450>"
> to="192.168.0.155:5060 <http://192.168.0.155:5060>"
> time="1146034398375"
> isSender="false"
> transactionId="-1439719789"
> callId="[email protected] 
> <mailto:[email protected]>"
> firstLine="CANCEL sip:[email protected] <mailto:sip:[email protected]> 
> SIP/2.0"
> debugLine="1107"
> >
>
> This means that the called user is not receiving the CANCEL from user 
> who was calling him so the called user doesn't receive an ACK and 
> sends a CANCEL again and so on ...
>
> Summarizing, the problem is when an you send an INVITE, and before the 
> user who is being Invited reponds you send a CANCEL.
>
> Regards,
>
> Victor



-- 
M. Ranganathan 

Advanced Networking Technologies Division,
National Institute of Standards and Technology (NIST),
100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899. 
tel:301 975 3664 , fax:301 590 0932 http://w3.antd.nist.gov/
Advanced Networking Technologies For the People!