GitLab

nua_stack.c: update the status returned to the client if there is an error while responding to a request.

The problem was reported by Michael Jerris and Joshua Engelbrecht.

darcs-hash:20070412150916-65a35-11224eb7b9e80765716b5c15a8467e8d5158f19c.gz

The status returned to the client is not updated if there is an internal
error while generating the response.

darcs-hash:20070412150751-65a35-5420e496a957f334c6a6347a14417eea12417aa5.gz

darcs-hash:20070412143718-65a35-9ecabdc32a50bdbbf87a3caf5594c6770edc0010.gz

darcs-hash:20070412141540-55b16-12ad15d4ad95839cd529a1b14b706f09a9e89abd.gz

darcs-hash:20070412141040-55b16-f87a88bb0fdb1a2a6b6e02951385f34e6323fe49.gz

darcs-hash:20070412090346-65a35-0cbb7fb79ffd37c72ad785fad67724c31b902c58.gz

darcs-hash:20070412090042-65a35-26e480da19bb4183219157d16f194242d661ca3e.gz

darcs-hash:20070412065034-65a35-094a336c4ab4349d438a3ad62525e8228b2f846a.gz

nua_session.c: when sending/receiving an UPDATE while session is ready use callstate calling/received

When UPDATE is sent during an established session, indicate progress with
callstate nua_callstate_calling in nua_i_state event. Likewise, when UPDATE
is received, but responding to it is left up to application, indicate
progress with callstate nua_callstate_received (instead of
nua_callstate_ready).

darcs-hash:20070412064815-65a35-985f0c5b7f3f891e19036f5d4a13d7e110c71953.gz

darcs-hash:20070411174533-65a35-072d0a66e7ad3565a976c451697c79f1e501b876.gz

The problem and crash with session timers was reported by Fabio Margarido.

Now following RFC 4028 more closely. There are test cases for UAS and UAC
refreshing the session with INVITE and UPDATE, and a test case where UPDATE
is filtered away until non-refreshing party sends BYE.

The re-INVITE/UPDATE refresh is sent around middle of expiration time (e.g.,
if expiration time is 3600 seconds, it is sent 1795..1805 seconds after the
previous refresh).

The non-refreshing party now sends a BYE request before two thirds of
session expiration time has elapsed without session refresh request.

darcs-hash:20070411174513-65a35-229d09a2e5371b5a88c9430f80da637b4c2bb6be.gz

nua: if nua_authenticate() does not contain new credentials, respond with 904 to the challenged request

This is a partial fix to the sf.net bug #1685249.

darcs-hash:20070411174316-65a35-0b66b87fcbcb9c9041b6499017f7e799e17f8ace.gz

darcs-hash:20070411174228-65a35-59b77a7bb315e00e028a3582443e810d35f71558.gz

test_call_reject.c: added test for infinite redirection loop.

darcs-hash:20070411165150-65a35-480a03250af7be6e893bcf2db58e7eb25bafbfed.gz

Now auc_all_credentials() returns 0 if the username and password has not
been changed. Now authentication client can avoid looping if application
insists in giving it bad username/password again.

Plugin method auc_clear() is available only when SOFIA_EXTEND_AUTH_CLIENT
has been defined to non-zero before #include
<sofia-sip/auth_client_plugin.h>.

darcs-hash:20070411155509-65a35-dfd16db949bf8795b14c4bc9033a3a433c4606ad.gz

nua_notifier.c, nua_subnotref.c: fixed timeout of nua_notify(), fixed handling of unsolicited NOTIFYs.

test_simple.c: added test case for subscription timeout, nua_method() with NUTAG_DIALOG(2).

darcs-hash:20070411134416-65a35-c5769e80202a17de328bd194ba2abcf92acd6823.gz

darcs-hash:20070411134343-65a35-97615034faee7add7f1c69e76455fb820bf2a13d.gz

darcs-hash:20070411110543-65a35-6a2129c3e3ef9cd108d8e2fb76ac5dcab9d16835.gz

Updated documentation (linking to NUTAG_WITH_THIS()).

darcs-hash:20070411134238-65a35-c53c36242d30145f3815f60539fd6c566fa6f9b0.gz

NUTAG_DIALOG(0): nua_method() reqest does not change dialog state
NUTAG_DIALOG(1): nua_method() is target-refresh request
NUTAG_DIALOG(2): nua_method() request creates a dialog

darcs-hash:20070411133849-65a35-cb4f3646fd53797b9646cc2f61fdf1d0b2e0949d.gz

darcs-hash:20070411110653-65a35-fc81753d830dadde021bddebd3c3a4889cbf5860.gz

darcs-hash:20070411110630-65a35-81d2d2bc030c0c65e6860023a844a2aad238aa28.gz

darcs-hash:20070411110506-65a35-deb1f5e48cde85d35cab471e5671d9844073222e.gz

test_proxy.[hc], test_100rel.c: fixed session timer negotiation by proxy (add "Require: timer" when needed)

darcs-hash:20070410201140-65a35-d24ea772ce850dc265d6ade7ec4f3af96d798767.gz

darcs-hash:20070410200413-65a35-ba4ffafd73488b9e7c11a1acbf302be563e081d6.gz

darcs-hash:20070410154351-88462-9a17d7bcdd988cd88afd10a9b371427e2a1265d5.gz

darcs-hash:20070410154342-88462-9bb7624af9ae3a5bbbb059bbb5024c01d560c464.gz

darcs-hash:20070410154241-88462-72aa581b8e57600e045b1a859d3a7cf398cff3e9.gz

darcs-hash:20070405063713-65a35-bbaae45ac29e6fac3dbc6ca301d0b7b5107310a3.gz

darcs-hash:20070403090030-65a35-e57fd9c35a89759ac5292d1cef541d243c4420c7.gz

The outbound used to add an extra contact to the unregistration request.

darcs-hash:20070403082632-65a35-8dbc19cbe0d3932dbb22e34a64ce062366d4c4b7.gz

darcs-hash:20070402121824-65a35-6f1d7742981d795396fa1ea73e8f512f4ef2a5e3.gz

darcs-hash:20070402121804-65a35-3c1703b8bf680950e06a776fff8a877b4452e8e9.gz

Problem reported by Mikhail Zabaluev.

darcs-hash:20070402121138-65a35-2379eec37d07af8488fda2388facdff91e817588.gz

The outbound should restart even after an error response to REGISTER (e.g.,
because the registrar rejected the Contact with an private IP address).

darcs-hash:20070402121110-65a35-3d64672b7c7de9d7f74cf9206d35bccaa975a392.gz

darcs-hash:20070402092927-65a35-02d83a40919fef68ebfd488569219ea46b957a7c.gz

darcs-hash:20070402092733-65a35-a1558ba98391f969022676a0bb9ac24a8b76973f.gz

darcs-hash:20070328152151-88462-bdae1b55538f4798ca8e72337efc3906c2151d1f.gz

darcs-hash:20070328152007-55b16-c74764c53aac747cb02b4cd86a83b5c512edec46.gz

run_test_sdp: trying to figure the location of test messages in better way, returning 77 when failing

darcs-hash:20070326165101-65a35-bb4860f0ba9b18c919156d6cbe7a33aa4ebde216.gz