Raphael Coeffic writes: > The correct behavior would be to let AmSipDialog generate the 200 ACK > (which would, at the same time, enable a couple of other nice > call-flows). Unfortunatly, this is not supported by the unixsockctrl and > binrpcctrl plugins. Whereby this could be enabled very easely in > binrpcctrl (SER support for this is already implemented), the > unixsockctrl would need a lot more work.
makes no sense to do lot of work on unixsockctrl, which will be deprecated anyway. > - (1) keep the correct state machine, send ACKs from AmSipDialog break > unixsockctrl support and modify binrpcctrl to support sending ACKs. i vote for this pill. if it means dropping unixsockctrl already now, then be it. > - (2) modify the state machine and simulate SER's behavior in sipctrl. > This modification should be canceled after we dropped unixsockctrl and > enable support for ACKs in SEMS applications. i don't know how much work this would be. perhaps too much and may be a source of new bugs. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
