diff -r 80ef3a206772 -r 48780e181b38 Symbian3/SDK/Source/GUID-A29FD82C-B3CC-5862-8DAB-1398A61D8B1F.dita
--- a/Symbian3/SDK/Source/GUID-A29FD82C-B3CC-5862-8DAB-1398A61D8B1F.dita Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-A29FD82C-B3CC-5862-8DAB-1398A61D8B1F.dita Tue Jul 20 12:00:49 2010 +0100
@@ -62,7 +62,7 @@
Managing HTTP digest security settings
CSIP, MSIPObserver,
CSIPConnection and MSIPConnectionObserver
-
+
An application creates a single instance of the CSIP class,
and implements the callback functions defined by MSIPObserver.
The CSIP uses the MSIPObserver functions.
@@ -76,14 +76,14 @@
application can have many CSIPConnection objects, but each
of them must have a different IAP.
Registration
services
-
+
An existing CSIPConnection is required to create
an instance of CSIPRegistrationBinding. The CSIPRegistrationBinding class
provides services for registration, updating the registration, and deregistration.
This class also provides instructions to the SIP stack to automatically refresh
the registration, and to query and set the outbound proxy used by the registration.
SIP dialog
associations
-
+
CSIPDialogAssocBase is the base class for SIP
dialog associations, such as CSIPInviteDialogAssoc, CSIPSubscribeDialogAssoc, CSIPReferDialogAssoc and CSIPNotifyDialogAssoc. The CSIPDialogAssocBase class
is used to obtain the associated SIP dialog, for the associated CSIPDialog instance,
@@ -104,7 +104,7 @@
an application to define and send NOTIFY requests.
Sent and received
network requests
-
+
When a SIP request is sent to the network, the SIP Client API implementation
creates a CSIPClientTransaction object and returns it to
the application. A CSIPClientTransaction object represents
@@ -122,7 +122,7 @@
the transaction type. Some operations are only allowed when the transaction
is in a certain state. Note: The SIP Client API creates instances of CSIPClientTransaction and CSIPServerTransaction and they cannot be created by the application.
SIP
message related classes
-
+
When a SIP request is sent to the network, the SIP Client API implementation
creates a CSIPClientTransaction object and returns it to
the application. A CSIPClientTransaction object represents
@@ -140,7 +140,7 @@
transaction type. Some operations are only allowed when the transaction is
in a certain state. Note: The SIP Client API creates instances of CSIPClientTransaction and CSIPServerTransaction and they cannot be created by the application.
Automatically
refreshing a SIP request
-
+
The SIP stack automatically refreshes a SIP request using the CSIPRefresh object. REGISTER, SUBSCRIBE and a request outside the dialog are refreshed. After
sending a refresh request, the application queries the state of the refresh
from CSIPRefresh.
CSIPRefresh provides
@@ -148,7 +148,7 @@
dialog. The CSIPRegistrationBinding and CSIPSubscribeDialogAssoc classes
are used to update and terminate a refreshed REGISTER or SUBSCRIBE.
Managing HTTP digest security
settings
-
+
An application must create an instance of the CSIP class
to use CSIPHttpDigest. The CSIPHttpDigest class
manages HTTP digest security settings and contains only static functions.