Found a bug in NICT SM

[phoenix6789]

Hi,

I've been attempting to use transactions for my scenario but I keep
getting an error message about a TransitionUndefinedException. I
wasn't sure who the culprit was...but I tracked the occurrence of the
problem to the end of my scenario for the BYE - 200 OK. Based on the
current NICT SM, I always get TIMER E and TIMER F being fired. When I
modify the NICT txn_received() method to force the SM into
@sm.provisional, and then @sm.final on receipt of the 2XX everything
is fine.

I believe you can't always expect to get 100 Trying for the BYE, it's
an optional message that cuts down on re-transmissions of the BYE
request until the final response comes in.

Can you confirm if this is a bug or not, and a possible solution? For
now, I've added a line in the NICT class to progress the @sm to
provisional and then final on receipt of a 2XX-6XX. This is OK for my
scenario, but probably not an ideal solution.

thanks,

Dave Adams.

[phoenix6789]

I was able to scope down this problem a little further, and I changed
my original "solution". I thought my original hack was working but it
caused the world to destabilize in a different way that I wasn't
expecting. My original problem description still holds. The NICT SM
works fine for REG 100 200, but for my INFO-200 and BYE-200, I'm
getting te and tf timers firing off because I'm not receiving 100 or
1XX messages for my INFO or BYE messages in my scenario. My new hack
is working nicely now. In the case of an INFO or BYE message, I
simply don't start the te or tf timer in the _send_request() method in
the transaction\NICT class.

I think it's still a bug, but looking to you guys for a better
solution than my hack.

regards,

Dave Adams.

[nishant bansal]

Hi Dave,

 Could you please share your script and log files that you have.

 Regards,

Nishant

--
You received this message because you are subscribed to the Google Groups "Sipper" group.
To post to this group, send email to sip...@googlegroups.com.
To unsubscribe from this group, send email to sipper+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sipper?hl=en.

--
Cheers

[phoenix6789]

I'm not able to share the scenario at this point. What I'll try and
do is create a mock scenario that exhibits the same behavior and that
with you instead.

Dave.

> > sipper+un...@googlegroups.com<sipper%2Bunsu...@googlegroups.com>