8 | | - PJSUA_DESTROY_NO_RX_MSG: allow sending outgoing messages (such as unregistration, event unpublication, BYEs, unsubscription, etc.), but do not wait for responses. This is useful to perform "best effort" clean up without delaying the shutdown process waiting for responses. |
9 | | - PJSUA_DESTROY_NO_TX_MSG: do not send any outgoing messages at all. This flag is useful if application knows that the network which the messages are to be sent on is currently down. This option implies PJSUA_DESTROY_NO_RX_MSG flag. |
| 8 | - PJSUA_DESTROY_NO_RX_MSG: allow sending outgoing messages (such as unregistration, event unpublication, BYEs, unsubscription, etc.), but do not wait for responses. This is useful to perform "best effort" clean up without delaying the shutdown process waiting for responses. But note that if the requests are challenged with authentication (and usually they are), this would not accomplish much if any. |
| 9 | - PJSUA_DESTROY_NO_TX_MSG: do not send any outgoing messages at all. This flag is useful if application knows that the network which the messages are to be sent on is currently down. |
| 10 | - PJSUA_DESTROY_NO_NETWORK: combination of the two above. |