| 1 | | Currently call id allocation is done by searching for empty slot from zero, so it will most likely to reuse call id of previous calls. Round robin allocation probably is more desirable. |
| | 1 | Currently call id allocation is done by searching for empty slot from zero, so it will most likely to reuse call id of previous calls. This may cause problem when application defer call disconnection processing to an application worker thread, since when the application worker thread is handling the event, it's possible that another call arrives and uses the same call ID as the previously disconnected call. |
| | 2 | |
| | 3 | Although approach of using worker thread like this is probably not a good idea, PJSUA-LIB can help avoiding this problem a bit (not completely!) by allocating the call id in round robin fashion. Note that even with the round robin call id allocation, application will still encounter the same problem when there is only one call id slot left in PJSUA-LIB. So the only way to get rid of this problem completely is by solving this problem in application code. |
| | 4 | |
![(please configure the [header_logo] section in trac.ini)](/repos/chrome/site/pj.jpg)
