Houston.... we have a problem! So here is the issue for which i am looking for a solution:
Let's SEMS sends an INVITE out for which it receives a 100 or 183 very quickly. Now the transaction state is switched to "Proceeding". The issue is that the RFC does not specify any timer for this state. So, if the UAS on the other never send a final reply, we will wait for ever... So the question is: should it be useful to let the application choose how long it would wait for a final reply? And if a each 1xx reply would reset this timer or not? I heard of some SNOM phones sending 180 very few seconds for ever if the user never picks up the phone. If the timer hits, we are supposed to send a CANCEL. Should it be sent by the sipctrl plugin? I believe yes... in which case the app would just get the final for the INVITE (if the phone is still alive) or a locally generated 408. Any thoughts/proposals on that? -Raphael. _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
