[reSIProcate] INFO being processed using same transaction state as BYE

[Justin Matthews]

Hello,

	After a call has been established, if an INFO message is received by
resip (UAS) and then a BYE is received immediately afterwards without the TU
processing the INFO, the BYE is ignored.
(TransactionState::processServerNonInvite ~line 795)

This is happening because resip determines that the transaction ID's of the
two messages are the same.  The transaction state is TRYING because of the
previous INFO.

The INFO message has the same branch parameter as the BYE in the top via,
but the method names are different. (RFC 3261 17.2.3)  Is resip handling
this correctly?

Here is the entire call sequence:

UAC (grandstream)  <->  UAS (resip/dum/myapp)
INVITE------------------>
TRYING<-----------------
200 OK<-----------------
ACK--------------------->
INFO-------------------->
BYE--------------------->
<NO response from resip>

Thanks,

-Justin