[reSIProcate] bad responses in TransactionState pedantic stack
If resip is acting as a UAC in pedantic stack mode and we receive a
response that can't be parsed, what should the stack do? For NITs,
there isn't really a problem if you drop it on the floor since the
stack will timeout and send a 408. For Invite transactions the
solution is not so clear.
I can think of a few options:
1) drop the response on the floor but do NOT continue processing -
this may have cleanup issues since the app will never know to end the
session.
2) notify the TU through an event that the session is borked. e.g. we
could generate a dummy response and pass it to the TU
3) pedantic stack considered harmful - just don't do it.
Note: I think the stack currently passes the partially parsed response
up to the TU. This seems really bad!
--
Jason