Tom Smith
-
2014-03-26
- assigned_to: Tom Smith
The purpose of SipPortFSM is to track the call state to aid in terminating the call (e.g., via SipPortTeardownFSM). It should not take on the role of "protocol enforcer," since the container already does this.
Considering this, add a defensive "catch-all" transition to SipPortFSM to handle any messages that are not explicitly handled by the underlying port-tracking state machine(s).