« Previous -
Version 142/238
(diff) -
Next » -
Current version
Anonymous, 04/21/2011 04:02 pm
= Middleware API =
This chapter describes the ''Middleware API'' for SIP SIMPLE client SDK that can be used for developing a user interface (e.g. Graphical User Interface). The Middleware provides a ''non-blocking'' API that communicates with the user interface asynchronously by using ''Notifications''. For its configuration, the Middleware uses the [wiki:SipConfigurationAPI Configuration API].
Image(sipsimple-middleware.png, align=center, width=700)
SIPApplicationImplemented in [browser:sipsimple/application.py]
Implements a high-level application responsable for starting and stopping various sub-systems required to implement a fully featured SIP User Agent application. The SIPApplication class is a Singleton and can be instantiated from any part of the code, obtaining a reference to the same object. The SIPApplication takes care of initializing the following components: * the twisted thread * the configuration system, via the [wiki:SipConfigurationAPI#ConfigurationManager ConfigurationManager] * the core [wiki:SipCoreApiDocumentation#Engine Engine] using the settings in the configuration * the [wiki:SipMiddlewareApi#AccountManager AccountManager], using the accounts in the configuration * the [wiki:SipMiddlewareApi#SessionManager SessionManager], in order to handle incoming sessions * two [wiki:SipMiddlewareApi#AudioBridge AudioBridges], using the settings in the configuration
The attributes in this class can be set and accessed on both this class and its subclasses, as they are implemented using descriptors which keep single value for each attribute, irrespective of the class from which that attribute is set/accessed. Usually, all attributes should be considered read-only.
==== methods ====
'''!__init!__'''(''self'')::
Instantiates a new SIPApplication.'''start'''(''self'', '''config_backend''')::
Starts the {{{SIPApplication}}} which initializes all the components in the correct order. The {{{config_backend}}} is used to start the {{{ConfigurationManager}}}. If any error occurs with loading the configuration, the exception raised by the {{{ConfigurationManager}}} is propagated by this method and {{{SIPApplication}}} can be started again. After this, any fatal errors will result in the SIPApplication being stopped and unusable, which means the whole application will need to stop. This method returns as soon as the twisted thread has been started, which means the application must wait for the {{{SIPApplicationDidStart}}} notification in order to know that the application started.'''stop'''(''self'')::
Stop all the components started by the SIPApplication. This method returns immediately, but a {{{SIPApplicationDidEnd}}} notification is sent when all the components have been stopped.==== attributes ====
'''running'''::
{{{True}}} if the SIPApplication is running (it has been started and it has not been told to stop), {{{False}}} otherwise.'''alert_audio_mixer'''::
The {{{AudioMixer}}} object created on the alert audio device as defined by the configuration (by SIPSimpleSettings.audio.alert_device).'''alert_audio_bridge'''::
An {{{AudioBridge}}} where {{{IAudioPort}}} objects can be added to playback sound to the alert device.'''alert_audio_device'''::
An {{{AudioDevice}}} which corresponds to the alert device as defined by the configuration. This will always be part of the alert_audio_bridge.'''voice_audio_mixer'''::
The {{{AudioMixer}}} object created on the voice audio device as defined by the configuration (by SIPSimpleSettings.audio.input_device and SIPSimpleSettings.audio.output_device).'''voice_audio_bridge'''::
An {{{AudioBridge}}} where {{{IAudioPort}}} objects can be added to playback sound to the output device or record sound from the input device.'''voice_audio_device'''::
An {{{AudioDevice}}} which corresponds to the voice device as defined by the configuration. This will always be part of the voice_audio_bridge.==== notifications ====
'''SIPApplicationWillStart'''::
This notification is sent just after the configuration has been loaded and the twisted thread started, but before any other components have been initialized.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPApplicationDidStart'''::
This notification is sent when all the components have been initialized. Note: it doesn't mean that all components have succeeded, for example, the account might not have registered by this time, but the registration process will have started.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPApplicationWillEnd'''::
This notification is sent as soon as the {{{stop()}}} method has been called.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPApplicationDidEnd'''::
This notification is sent when all the components have been stopped. All components have been given reasonable time to shutdown gracefully, such as the account unregistering. However, because of factors outside the control of the middleware, such as network problems, some components might not have actually shutdown gracefully; this is needed because otherwise the SIPApplication could hang indefinitely (for example because the system is no longer connected to a network and it cannot be determined when it will be again).
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPApplicationFailedToStartTLS'''::
This notification is sent when a problem arises with initializing the TLS transport. In this case, the Engine will be started without TLS support and this notification contains the error which identifies the cause for not being able to start the TLS transport.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]error:[[BR]]
The exception raised by the Engine which identifies the cause for not being able to start the TLS transport.SIP sessions are supported by the {{{sipsimple.session.Session}}} class and independent stream classes, which need to implement the {{{sipsimple.streams.IMediaStream}}} interface. The {{{Session}}} class takes care of the signalling, while the streams offer the actual media support which is negotiated by the {{{Session}}}. The streams which are implemented in the SIP SIMPLE middleware are provided in modules within the {{{sipsimple.streams}}} package, but they are accessible for import directly from {{{sipsimple.streams}}}. Currently, the middleware implements two types of streams, one for RTP data, with a concrete implementation in the {{{AudioStream}}} class, and one for MSRP sessions, with concrete implementations in the {{{ChatStream}}}, {{{FileTransferStream}}} and {{{DesktopSharingStream}}} classes. However, the application can provide its own stream implementation, provided they respect the {{{IMediaStream}}} interface.
The {{{sipsimple.streams}}} module also provides a mechanism for automatically registering media streams in order for them to be used for incoming sessions. This is explained in more detail in [wiki:SipMiddlewareApi#MediaStreamRegistry MediaStreamRegistry].
=== SessionManager ===
Implemented in [browser:sipsimple/session.py]
The {{{sipsimple.session.SessionManager}}} class is a singleton, which acts as the central aggregation point for sessions within the middleware.
Although it is mainly used internally, the application can use it to query information about all active sessions.
The SessionManager is implemented as a singleton, meaning that only one instance of this class exists within the middleware. The SessionManager is started by the SIPApplication and takes care of handling incoming sessions and closing all sessions when SIPApplication is stopped.
==== attributes ====
'''sessions'''::
A property providing a copy of the list of all active {{{Sesssion}}} objects within the application, meaning any {{{Session}}} object that exists globally within the application and is not in the {{{NULL}}} or {{{TERMINATED}}} state.==== methods ====
'''!__init!__'''(''self'')::
Instantiate a new {{{SessionManager}}} object.'''start'''(''self'')::
Start the {{{SessionManager}}} in order to be able to handle incoming sessions. This method is called automatically when SIPApplication is started. The application should not call this method directly.'''stop'''(''self'')::
End all connected sessions. This method is called automatically when SIPApplication is stopped. The application should not call this method directly.=== Session ===
Implemented in [browser:sipsimple/session.py]
A {{{sipsimple.session.Session}}} object represents a complete SIP session between the local and a remote endpoints. Both incoming and outgoing sessions are represented by this class.
A {{{Session}}} instance is a stateful object, meaning that it has a {{{state}}} attribute and that the lifetime of the session traverses different states, from session creation to termination.
State changes are triggered by methods called on the object by the application or by received network events.
These states and their transitions are represented in the following diagram:
Image(/raw-attachment/wiki/SipCoreApiDocumentation/sipsimple-core-invite-state-machine.png)
Although these states are crucial to the correct operation of the {{{Session}}} object, an application using this object does not need to keep track of these states, as a set of notifications is also emitted, which provide all the necessary information to the application.
The {{{Session}}} is completely independent of the streams it contains, which need to be implementations of the {{{sipsimple.streams.IMediaStream}}} interface. This interface provides the API by which the {{{Session}}} communicates with the streams. This API should not be used by the application, unless it also provides stream implementations or a SIP INVITE session implementation.
==== methods ====
'''!__init!__'''(''self'', '''account''')::
Creates a new {{{Session}}} object in the {{{None}}} state.
[[BR]]''account'':[[BR]]
The local account to be associated with this {{{Session}}}.'''connect'''(''self'', '''to_header''', '''routes''', '''streams''', '''is_focus'''={{{False}}}, '''subject'''={{{None}}})::
Will set up the {{{Session}}} as outbound and propose the new session to the specified remote party and move the state machine to the {{{outgoing}}} state.
Before contacting the remote party, a {{{SIPSessionNewOutgoing}}} notification will be emitted.
If there is a failure or the remote party rejected the offer, a {{{SIPSessionDidFail}}} notification will be sent.
Any time a ringing indication is received from the remote party, a {{{SIPSessionGotRingIndication}}} notification is sent.
If the remote party accepted the session, a {{{SIPSessionWillStart}}} notification will be sent, followed by a {{{SIPSessionDidStart}}} notification when the session is actually established.
This method may only be called while in the {{{None}}} state.
[[BR]]''to_header'':[[BR]]
A {{{sipsimple.core.ToHeader}}} object representing the remote identity to initiate the session to.
[[BR]]''routes'':[[BR]]
An iterable of {{{sipsimple.util.Route}}} objects, specifying the IP, port and transport to the outbound proxy.
These routes will be tried in order, until one of them succeeds.
[[BR]]''streams'':[[BR]]
A list of stream objects which will be offered to the remote endpoint.
[[BR]]''is_focus'':[[BR]]
Boolean flag indicating if the {{{isfocus}}} parameter should be added to the {{{Contact}}} header according to RFC 4579.
[[BR]]''subject'':[[BR]]
Session subject. If not None a {{{Subject}}} header will be added with the specified value.'''send_ring_indication'''(''self'')::
Sends a 180 provisional response in the case of an incoming session.'''accept'''(''self'', '''streams''')::
Calling this methods will accept an incoming session and move the state machine to the {{{accepting}}} state.
When there is a new incoming session, a {{{SIPSessionNewIncoming}}} notification is sent, after which the application can call this method on the sender of the notification.
After this method is called, {{{SIPSessionWillStart}}} followed by {{{SIPSessionDidStart}}} will be emitted, or {{{SIPSessionDidFail}}} on an error.
This method may only be called while in the {{{incoming}}} state.
[[BR]]''streams'':[[BR]]
A list of streams which needs to be a subset of the proposed streams which indicates which streams are to be accepted. All the other proposed streams will be rejected.'''reject'''(''self'', '''code'''={{{603}}}, '''reason'''={{{None}}})::
Reject an incoming session and move it to the {{{terminating}}} state, which eventually leads to the {{{terminated}}} state.
Calling this method will cause the {{{Session}}} object to emit a {{{SIPSessionDidFail}}} notification once the session has been rejected.
This method may only be called while in the {{{incoming}}} state.
[[BR]]''code'':[[BR]]
An integer which represents the SIP status code in the response which is to be sent. Usually, this is either 486 (Busy) or 603 (Decline/Busy Everywhere).
[[BR]]''reason'':[[BR]]
The string which is to be sent as the SIP status reason in the response, or None if PJSIP's default reason for the specified code is to be sent.'''accept_proposal'''(''self'', '''streams''')::
When the remote party proposes to add some new streams, signaled by the {{{SIPSessionGotProposal}}} notification, the application can use this method to accept the stream(s) being proposed.
After calling this method a {{{SIPSessionGotAcceptProposal}}} notification is sent, unless an error occurs while setting up the new stream, in which case a {{{SIPSessionHadProposalFailure}}} notification is sent and a rejection is sent to the remote party. As with any action which causes the streams in the session to change, a {{{SIPSessionDidRenegotiateStreams}}} notification is also sent.
This method may only be called while in the {{{received_proposal}}} state.
[[BR]]''streams'':[[BR]]
A list of streams which needs to be a subset of the proposed streams which indicates which streams are to be accepted. All the other proposed streams will be rejected.'''reject_proposal'''(''self'', '''code'''={{{488}}}, '''reason'''={{{None}}})::
When the remote party proposes new streams that the application does not want to accept, this method can be used to reject the proposal, after which a {{{SIPSessionGotRejectProposal}}} or {{{SIPSessionHadProposalFailure}}} notification is sent.
This method may only be called while in the {{{received_proposal}}} state.
[[BR]]''code'':[[BR]]
An integer which represents the SIP status code in the response which is to be sent. Usually, this is 488 (Not Acceptable Here).
[[BR]]''reason'':[[BR]]
The string which is to be sent as the SIP status reason in the response, or None if PJSIP's default reason for the specified code is to be sent.'''add_stream'''(''self'', '''stream''')::
Proposes a new stream to the remote party.
Calling this method will cause a {{{SIPSessionGotProposal}}} notification to be emitted.
After this, the state machine will move into the {{{sending_proposal}}} state until either a {{{SIPSessionGotAcceptProposal}}}, {{{SIPSessionGotRejectProposal}}} or {{{SIPSessionHadProposalFailure}}} notification is sent, informing the application if the remote party accepted the proposal. As with any action which causes the streams in the session to change, a {{{SIPSessionDidRenegotiateStreams}}} notification is also sent.
This method may only be called while in the {{{connected}}} state.'''remove_stream'''(''self'', '''stream''')::
Stop the stream and remove it from the session, informing the remote party of this. Although technically this is also done via an SDP negotiation which may fail, the stream will always get remove (if the remote party refuses the re-INVITE, the result will be that the remote party will have a different view of the active streams than the local party).
This method may only be called while in the {{{connected}}} state.'''cancel_proposal'''(''self'')::
This method cancels a proposal of adding a stream to the session by sending a CANCEL request. A {{{SIPSessionGotRejectProposal}}} notification will be sent with code 487.'''hold'''(''self'')::
Put the streams of the session which support the notion of hold on hold.
This will cause a {{{SIPSessionDidChangeHoldState}}} notification to be sent.
This method may be called in any state and will send the re-INVITE as soon as it is possible.'''unhold'''(''self'')::
Take the streams of the session which support the notion of hold out of hold.
This will cause a {{{SIPSessionDidChangeHoldState}}} notification to be sent.
This method may be called in any state and will send teh re-INVITE as soon as it is possible.'''end'''(''self'')::
This method may be called any time after the {{{Session}}} has started in order to terminate the session by sending a BYE request.
Right before termination a {{{SIPSessionWillEnd}}} notification is sent, after termination {{{SIPSessionDidEnd}}} is sent.==== attributes ====
'''state'''::
The state the object is currently in, being one of the states from the diagram above.'''account'''::
The {{{sipsimple.account.Account}}} or {{{sipsimple.account.BonjourAccount}}} object that the {{{Session}}} is associated with.
On an outbound session, this is the account the application specified on object instantiation.'''direction'''::
A string indicating the direction of the initial negotiation of the session.
This can be either {{{None}}}, "incoming" or "outgoing".'''transport'''::
A string representing the transport this {{{Session}}} is using: {{{"udp"}}}, {{{"tcp"}}} or {{{"tls"}}}.'''start_time'''::
The time the session started as a {{{datetime.datetime}}} object, or {{{None}}} if the session was not yet started.'''stop_time'''::
The time the session stopped as a {{{datetime.datetime}}} object, or {{{None}}} if the session has not yet terminated.'''on_hold'''::
Boolean indicating whether the session was put on hold, either by the local or the remote party.'''remote_user_agent'''::
A string indicating the remote user agent, if it provided one.
Initially this will be {{{None}}}, it will be set as soon as this information is received from the remote party (which may be never).'''local_identity'''::
The {{{sipsimple.core.FrozenFromHeader}}} or {{{sipsimple.core.FrozenToHeader}}} identifying the local party, if the session is active, {{{None}}} otherwise.'''remote_identity'''::
The {{{sipsimple.core.FrozenFromHeader}}} or {{{sipsimple.core.FrozenToHeader}}} identifying the remote party, if the session is active, {{{None}}} otherwise.'''streams'''::
A list of the currently active streams in the {{{Session}}}.'''proposed_streams'''::
A list of the currently proposed streams in the {{{Session}}}, or {{{None}}} if there is no proposal in progress.'''conference'''::
A {{{ConferenceHandler}}} object instance (or Null). It can be later used to add/remove participants from a remote conference.'''subject'''::
The session subject as a unicode object.==== notifications ====
'''SIPSessionNewIncoming'''::
Will be sent when a new incoming {{{Session}}} is received.
The application should listen for this notification to get informed of incoming sessions.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''streams'':[[BR]]
A list of streams that were proposed by the remote party.'''SIPSessionNewOutgoing'''::
Will be sent when the application requests a new outgoing {{{Session}}}.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''streams'':[[BR]]
A list of streams that were proposed to the remote party.'''SIPSessionGotRingIndication'''::
Will be sent when an outgoing {{{Session}}} receives an indication that a remote device is ringing.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPSessionGotProvisionalResponse'''::
Will be sent whenever the {{{Session}}} receives a provisional response as a result of sending a (re-)INVITE.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''code'':[[BR]]
The SIP status code received.
[[BR]]''reason'':[[BR]]
The SIP status reason received.'''SIPSessionWillStart'''::
Will be sent just before a {{{Session}}} completes negotiation.
In terms of SIP, this is sent after the final response to the {{{INVITE}}}, but before the {{{ACK}}}.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPSessionDidStart'''::
Will be sent when a {{{Session}}} completes negotiation and all the streams have started.
In terms of SIP this is sent after the {{{ACK}}} was sent or received.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''streams'':[[BR]]
The list of streams which now form the active streams of the {{{Session}}}.'''SIPSessionDidFail'''::
This notification is sent whenever the session fails before it starts.
The failure reason is included in the data attributes.
This notification is never followed by {{{SIPSessionDidEnd}}}.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''originator'':[[BR]]
A string indicating the originator of the {{{Session}}}. This will either be "local" or "remote".
[[BR]]''code'':[[BR]]
The SIP error code of the failure.
[[BR]]''reason'':[[BR]]
A SIP status reason.
[[BR]]''failure_reason'':[[BR]]
A string which represents the reason for the failure, such as {{{"user_request"}}}, {{{"missing ACK"}}}, {{{"SIP core error..."}}}.'''SIPSessionWillEnd'''::
Will be sent just before terminating a {{{Session}}}.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPSessionDidEnd'''::
Will be sent always when a {{{Session}}} ends as a result of remote or local session termination.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''originator'':[[BR]]
A string indicating who originated the termination. This will either be "local" or "remote".
[[BR]]''end_reason'':[[BR]]
A string representing the termination reason, such as {{{"user_request"}}}, {{{"SIP core error..."}}}.'''SIPSessionDidChangeHoldState'''::
Will be sent when the session got put on hold or removed from hold, either by the local or the remote party.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''originator'':[[BR]]
A string indicating who originated the hold request, and consequently in which direction the session got put on hold.
[[BR]]''on_hold'':[[BR]]
{{{True}}} if there is at least one stream which is on hold and {{{False}}} otherwise.
[[BR]]''partial'':[[BR]]
{{{True}}} if there is at least one stream which is on hold and one stream which supports hold but is not on hold and {{{False}}} otherwise.'''SIPSessionGotProposal'''::
Will be sent when either the local or the remote party proposes to add streams to the session.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''originator'':[[BR]]
The party that initiated the stream proposal, can be either "local" or "remote".
[[BR]]''streams'':[[BR]]
A list of streams that were proposed.'''SIPSessionGotRejectProposal'''::
Will be sent when either the local or the remote party rejects a proposal to have streams added to the session.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''originator'':[[BR]]
The party that initiated the stream proposal, can be either "local" or "remote".
[[BR]]''code'':[[BR]]
The code with which the proposal was rejected.
[[BR]]''reason'':[[BR]]
The reason for rejecting the stream proposal.
[[BR]]''streams'':[[BR]]
The list of streams which were rejected.'''SIPSessionGotAcceptProposal'''::
Will be sent when either the local or the remote party accepts a proposal to have stream( added to the session.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''originator'':[[BR]]
The party that initiated the stream proposal, can be either "local" or "remote".
[[BR]]''streams'':[[BR]]
The list of streams which were accepted.
[[BR]]''proposed_streams'':[[BR]]
The list of streams which were originally proposed.'''SIPSessionHadProposalFailure'''::
Will be sent when a re-INVITE fails because of an internal reason (such as a stream not being able to start).
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''failure_reason'':[[BR]]
The error which caused the proposal to fail.
[[BR]]''streams'':[[BR]]
The streams which were part of this proposal.'''SIPSessionDidRenegotiateStreams'''::
Will be sent when a media stream is either activated or deactivated.
An application should listen to this notification in order to know when a media stream can be used.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''action'':[[BR]]
A string which is either {{{"add"}}} or {{{"remove"}}} which specifies what happened to the streams the notificaton referes to
[[BR]]''streams'':[[BR]]
A list with the streams which were added or removed.'''SIPSessionDidProcessTransaction'''::
Will be sent whenever a SIP transaction is complete in order to provide low-level details of the progress of the INVITE dialog.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''originator'':[[BR]]
The initiator of the transaction, {{{"local"}}} or {{{"remote"}}}.
[[BR]]''method'':[[BR]]
The method of the request.
[[BR]]''code'':[[BR]]
The SIP status code of the response.
[[BR]]''reason'':[[BR]]
The SIP status reason of the response.
[[BR]]''ack_received'':[[BR]]
This attribute is only present for INVITE transactions and has one of the values {{{True}}}, {{{False}}} or {{{"unknown"}}}. The last value may occur then PJSIP does not let us know whether the ACK was received or not.As an example for how to use the {{{Session}}} object, the following provides a basic Python program that initiates an outgoing SIP session request see [wiki:SipSessionExample Minimalist Session Example code].
=== IMediaStream ===
Implemented in [browser:sipsimple/streams/__init__.py]
This interface describes the API which the {{{Session}}} uses to communicate with the streams. All streams used by the {{{Session}}} must respect this interface.
==== methods ====
'''!__init!__'''(''self'', ''account'')::
Initializes the generic stream instance.'''new_from_sdp'''(''cls'', ''account'', ''remote_sdp'', ''stream_index'')::
A classmethod which returns an instance of this stream implementation if the sdp is accepted by the stream or None otherwise.
[[BR]]account:[[BR]]
The {{{sipsimple.account.Account}}} or {{{sipsimple.account.BonjourAccount}}} object the session which this stream would be part of is associated with.
[[BR]]remote_sdp:[[BR]]
The {{{FrozenSDPSession}}} which was received by the remote offer.
[[BR]]stream_index:[[BR]]
An integer representing the index within the list of media streams within the whole SDP which this stream would be instantiated for.'''get_local_media'''(''self'', ''for_offer'')::
Return an {{{SDPMediaStream}}} which represents an offer for using this stream if {{{for_offer}}} is {{{True}}} and a response to an SDP proposal otherwise.
[[BR]]for_offer:[[BR]]
{{{True}}} if the {{{SDPMediaStream}}} will be used for an SDP proposal and {{{False}}} if for a response.'''initialize'''(''self'', ''session'', ''direction'')::
Initializes the stream. This method will get called as soon as the stream is known to be at least offered as part of the {{{Session}}}. If initialization goes fine, the stream must send a {{{MediaStreamDidInitialize}}} notification or a {{{MediaStreamDidFail}}} notification otherwise.
[[BR]]session:[[BR]]
The {{{Session}}} object this stream will be part of.
[[BR]]direction:[[BR]]
{{{"incoming"}}} if the stream was created because of a received proposal and {{{"outgoing"}}} if a proposal was sent. Note that this need not be the same as the initial direction of the {{{Session}}} since streams can be proposed in either way using re-INVITEs.'''start'''(''self'', ''local_sdp'', ''remote_sdp'', ''stream_index'')::
Starts the stream. This method will be called as soon is known to be used in the {{{Session}}} (eg. only called for an incoming proposal if the local party accepts the proposed stream). If starting succeeds, the stream must send a {{{MediaStreamDidStart}}} notification or a {{{MediaStreamDidFail}}} notification otherwise.
[[BR]]local_sdp:[[BR]]
The {{{FrozenSDPSession}}} which is used by the local endpoint.
[[BR]]remote_sdp:[[BR]]
The {{{FrozenSDPSession}}} which is used by the remote endpoint.
[[BR]]stream_index:[[BR]]
An integer representing the index within the list of media streams within the whole SDP which this stream is represented by.'''validate_update'''(''self'', ''remote_sdp'', ''stream_index'')::
This method will be called when a re-INVITE is received which changes the parameters of the stream within the SDP. The stream must return {{{True}}} if the changes are acceptable or {{{False}}} otherwise. If any changed streams return {{{False}}} for a re-INVITE, the re-INVITE will be refused with a negative response. This means that streams must not changed any internal data when this method is called as the update is not guaranteed to be applied even if the stream returns {{{True}}}.
[[BR]]remote_sdp:[[BR]]
The {{{FrozenSDPSession}}} which is used by the remote endpoint.
[[BR]]stream_index:[[BR]]
An integer representing the index within the list of media streams within the whole SDP which this stream is represented by.'''update'''(''self'', ''local_sdp'', ''remote_sdp'', ''stream_index'')::
This method is called when the an SDP negotiation initiated by either the local party or the remote party succeeds. The stream must update its internal state according to the new SDP in use.
[[BR]]local_sdp:[[BR]]
The {{{FrozenSDPSession}}} which is used by the local endpoint.
[[BR]]remote_sdp:[[BR]]
The {{{FrozenSDPSession}}} which is used by the remote endpoint.
[[BR]]stream_index:[[BR]]
An integer representing the index within the list of media streams within the whole SDP which this stream is represented by.'''hold'''(''self'')::
Puts the stream on hold if supported by the stream. Typically used by audio and video streams. The stream must immediately stop sending/receiving data and calls to {{{get_local_media()}}} following calls to this method must return an SDP which reflects the new hold state.'''unhold'''(''self'')::
Takes the stream off hold. Typically used by audio and video streams. Calls to {{{get_local_media()}}} following calls to this method must return an SDP which reflects the new hold state.'''deactivate'''(''self'')::
This method is called on a stream just before the stream will be removed from the {{{Session}}} (either as a result of a re-INVITE or a BYE). This method is needed because it avoids a race condition with streams using stateful protocols such as TCP: the stream connection might be terminated before the SIP signalling announces this due to network routing inconsistencies and the other endpoint would not be able to distinguish between this case and an error which caused the stream transport to fail. The stream must not take any action, but must consider that the transport being closed by the other endpoint after this method was called as a normal situation rather than an error condition.'''end'''(''self'')::
Ends the stream. This must close the underlying transport connection. The stream must send a {{{MediaStreamWillEnd}}} just after this method is called and a {{{MediaStreamDidEnd}}} as soon as the operation is complete. This method is always be called by the {{{Session}}} on the stream if at least the {{{initialize()}}} method has been called. This means that once a stream sends the {{{MediaStreamDidFail}}} notification, the {{{Session}}} will still call this method.==== attributes ====
'''type''' (class attribute)::
A string identifying the stream type (eg: {{{"audio"}}}, {{{"video"}}}).'''priority''' (class attribute)::
An integer value indicating the stream priority relative to the other streams types (higher numbers have higher priority).'''hold_supported'''::
True if the stream supports hold'''on_hold_by_local'''::
True if the stream is on hold by the local party'''on_hold_by_remote'''::
True if the stream is on hold by the remote'''on_hold'''::
True if either on_hold_by_local or on_hold_by_remote is true==== notifications ====
These notifications must be generated by all streams in order for the {{{Session}}} to know the state of the stream.
'''MediaStreamDidInitialize'''::
Sent when the stream has been successfully initialized.'''MediaStreamDidStart'''::
Sent when the stream has been successfully started.'''MediaStreamDidFail'''::
Sent when the stream has failed either as a result of calling one of its methods, or during the normal operation of the stream (such as the transport connection being closed).'''MediaStreamWillEnd'''::
Sent immediately after the {{{end()}}} method is called.'''MediaStreamDidEnd'''::
Sent when the {{{end()}}} method finished closing the stream.=== MediaStreamRegistry ===
The MediaStream registry is a collection of classes which implement {{{IMediaStream}}}. This collection is used by the {{{Session}}} to select a stream class for instantiation in the case of an incomming session. The streams are included in the collection in the descending order of their priority. Thus, streams with a higher priority will be tried first by the {{{Session}}}. This object is a Singleton so references to the same object can be obtained by a simple instantiation.
There are several pre-built streams based on the {{{IMediaStream}}} API: * {{{sipsimple.streams.rtp.AudioStream}}} - Audio stream based on RTP * {{{sipsimple.streams.msrp.ChatStream}}} - Chat stream based on MSRP * {{{sipsimple.streams.msrp.FileTransferStream}}} - File Transfer stream based on MSRP * {{{sipsimple.streams.msrp.DesktopSharingStream}}} - Desktop Sharing stream based on VNC over MSRP
Other streams which are created by the application must be registered in this registry. For a simple way of doing this, see [wiki:SipMiddlewareApi#MediaStreamRegistrar MediaStreamRegistrar].
==== methods ====
'''!__init!__'''(''self'')::
Instantiate the MediaStreamRegistry. This will be called just once when first (and only) instance is created.'''!__iter!__'''(''self'')::
This method allows the registry to be iterated through and will return classes which were registered to it.'''add'''(''self'', '''cls''')::
Add {{{cls}}} to the registry of streams. The class must implement the {{{IMediaStream}}} interface.=== MediaStreamRegistrar ===
This is a convenience metaclass which automatically registers a defined class with the {{{MediaStreamRegistry}}}. In order to use this class, one simply needs to use it as the metaclass of the new stream.
{{{
from zope.interface import implements
from sipsimple.streams import IMediaStream, MediaStreamRegistrar
class MyStream(object):
metaclass = MediaStreamRegistrar
implements(IMediaStream)[...]
}}}
=== AudioStream ===
Implemented in [browser:sipsimple/streams/rtp.py]
The {{{AudioStream}}} is an implementation of {{{IMediaStream}}} which supports audio data using the {{{AudioTransport}}} and {{{RTPTransport}}} of the SIP core. As such, it provides all features of these objects, including ICE negotiation. An example SDP created using the {{{AudioStream}}} is provided below:
{{{
Content-Type: application/sdp
Content-Length: 1093
v=0
o=- 3467525278 3467525278 IN IP4 192.168.1.6
s=blink-0.10.7-beta
c=IN IP4 80.101.96.20
t=0 0
m=audio 55328 RTP/AVP 104 103 102 3 9 0 8 101
a=rtcp:55329 IN IP4 80.101.96.20
a=rtpmap:104 speex/32000
a=rtpmap:103 speex/16000
a=rtpmap:102 speex/8000
a=rtpmap:3 GSM/8000
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:esI6DbLY1+Aceu0JNswN9Z10DcFx5cZwqJcu91jb
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:SHuEMm1BYJqOF4udKl73EaCwnsI57pO86bYKsg70
a=ice-ufrag:2701ed80
a=ice-pwd:6f8f8281
a=candidate:S 1 UDP 31 80.101.96.20 55328 typ srflx raddr 192.168.1.6 rport 55328
a=candidate:H 1 UDP 23 192.168.1.6 55328 typ host
a=candidate:H 1 UDP 23 10.211.55.2 55328 typ host
a=candidate:H 1 UDP 23 10.37.129.2 55328 typ host
a=candidate:S 2 UDP 30 80.101.96.20 55329 typ srflx raddr 192.168.1.6 rport 55329
a=candidate:H 2 UDP 22 192.168.1.6 55329 typ host
a=candidate:H 2 UDP 22 10.211.55.2 55329 typ host
a=candidate:H 2 UDP 22 10.37.129.2 55329 typ host
a=sendrecv
}}}
As an implementation of {{{IAudioPort}}}, an {{{AudioStream}}} can be added to an {{{AudioBridge}}} to send or to read audio data to/from other audio objects. It is connected to the voice {{{AudioMixer}}} ({{{SIPApplication.voice_audio_mixer}}}) so it can only be added to bridges using the same {{{AudioMixer}}}. It also contains an {{{AudioBridge}}} on the {{{bridge}}} attribute which always contains an {{{AudioDevice}}} corresponding to the input and output devices; when the stream is active (started and not on hold), the bridge also contains the stream itself and when recording is active, the stream contains a {{{WaveRecorder}}} which records audio data.
==== methods ====
'''start_recording'''(''self'', '''filename'''={{{None}}})::
If an audio stream is present within this session, calling this method will record the audio to a {{{.wav}}} file.
Note that when the session is on hold, nothing will be recorded to the file.
Right before starting the recording a {{{SIPSessionWillStartRecordingAudio}}} notification will be emitted, followed by a {{{SIPSessionDidStartRecordingAudio}}}.
This method may only be called while the stream is started.
[[BR]]''filename'':[[BR]]
The name of the {{{.wav}}} file to record to.
If this is set to {{{None}}}, a default file name including the session participants and the timestamp will be generated using the directory defined in the configuration.'''stop_recording'''(''self'')::
This will stop a previously started recording.
Before stopping, a {{{SIPSessionWillStopRecordingAudio}}} notification will be sent, followed by a {{{SIPSessionDidStopRecordingAudio}}}.'''send_dtmf'''(''self'', '''digit''')::
If the audio stream is started, sends a DTMF digit to the remote party.
[[BR]]''digit'':[[BR]]
This should a string of length 1, containing a valid DTMF digit value (0-9, A-D, * or #).==== attributes ====
'''sample_rate'''::
If the audio stream was started, this attribute contains the sample rate of the audio negotiated.'''codec'''::
If the audio stream was started, this attribute contains the name of the audio codec that was negotiated.'''srtp_active'''::
If the audio stream was started, this boolean attribute indicates if SRTP is currently being used on the stream.'''ice_active'''::
{{{True}}} if the ICE candidates negotiated are being used, {{{False}}} otherwise.'''local_rtp_address'''::
If an audio stream is present within the session, this attribute contains the local IP address used for the audio stream.'''local_rtp_port'''::
If an audio stream is present within the session, this attribute contains the local UDP port used for the audio stream.'''remote_rtp_address_sdp'''::
If the audio stream was started, this attribute contains the IP address that the remote party gave to send audio to.'''remote_rtp_port_sdp'''::
If the audio stream was started, this attribute contains the UDP port that the remote party gave to send audio to.'''remote_rtp_address_received'''::
If the audio stream was started, this attribute contains the remote IP address from which the audio stream is being received.'''remote_rtp_port_received'''::
If the audio stream was started, this attribute contains the remote UDP port from which the audio stream is being received.'''local_rtp_candidate_type'''::
The local ICE candidate type which was selected by the ICE negotiation if it succeeded and {{{None}}} otherwise.'''remote_rtp_candidate_type'''::
The remote ICE candidate type which was selected by the ICE negotiation if it succeeded and {{{None}}} otherwise.'''recording_filename'''::
If the audio stream is currently being recorded to disk, this property contains the name of the {{{.wav}}} file being recorded to.==== notifications ====
'''AudioStreamDidChangeHoldState'''::
Will be sent when the hold state is changed as a result of either a SIP message received on the network or the application calling the {{{hold()/unhold()}}} methods on the {{{Session}}} this stream is part of.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]originator:[[BR]]
A string representing the party which requested the hold change, {{{"local"}}} or {{{"remote"}}}
[[BR]]on_hold:[[BR]]
A boolean indicating the new hold state from the point of view of the originator.'''AudioStreamWillStartRecordingAudio''::
Will be sent when the application requested that the audio stream be recorded to a {{{.wav}}} file, just before recording starts.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''filename'':[[BR]]
The full path to the {{{.wav}}} file being recorded to.'''AudioStreamDidStartRecordingAudio'''::
Will be sent when the application requested that the audio stream be recorded to a {{{.wav}}} file, just after recording started.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''filename'':[[BR]]
The full path to the {{{.wav}}} file being recorded to.'''AudioStreamWillStopRecordingAudio'''::
Will be sent when the application requested ending the recording to a {{{.wav}}} file, just before recording stops.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''filename'':[[BR]]
The full path to the {{{.wav}}} file being recorded to.'''AudioStreamDidStopRecordingAudio'''::
Will be sent when the application requested ending the recording to a {{{.wav}}} file, just after recording stoped.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''filename'':[[BR]]
The full path to the {{{.wav}}} file being recorded to.'''AudioStreamDidChangeRTPParameters'''::
This notification is sent when the RTP parameters are changed, such as codec, sample rate, RTP port etc.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''AudioStreamGotDTMF'''::
Will be send if there is a DMTF digit received from the remote party on the audio stream.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''digit'':[[BR]]
The DTMF digit that was received, in the form of a string of length 1.'''AudioStreamICENegotiationStateDidChange'''::
This notification is proxied from the {{{RTPTransport}}} and as such has the same data as the {{{RTPTransportICENegotiationStateDidChange}}}.'''AudioStreamICENegotiationDidSucceed'''::
This notification is proxied from the {{{RTPTransport}}} and as such has the same data as the {{{RTPTransportICENegotiationDidSucceed}}}.'''AudioStreamICENegotiationDidFail'''::
This notification is proxied from the {{{RTPTransport}}} and as such has the same data as the {{{RTPTransportICENegotiationDidFail}}}.'''AudioStreamDidTimeout'''::
This notification is proxied from the {{{RTPTransport}}}. It's sent when the RTP transport did not receive any data after the specified amount of time (rtp.timeout setting in the {{{Account}}}).=== MSRPStreamBase ===
Implemented in [browser:sipsimple/streams/msrp.py]
The {{{MSRPStreamBase}}} is used as a base class for streams using the MSRP protocol. Within the SIP SIMPLE middleware, this hold for the {{{ChatStream}}}, {{{FileTransferStream}}} and {{{DesktopSharingStream}}} classes, however the application can also make use of this class to implement some other streams based on the MSRP protocol as a transport.
==== methods ====
Of the methods defined by the {{{IMediaStream}}} interface, only the {{{new_from_sdp}}} method is not implemented in this base class and needs to be provided by the subclasses. Also, the subclasses can defined methods of the form {{{_handle_XXX}}}, where XXX is a MSRP method name in order to handle incoming MSRP requests. Also, since this class registers as an observer for itself, it will receive the notifications it sends so subclasses can define methods having the signature {{{_NH_<notification name>(self, notification)}}} as used throughout the middleware in order to do various things at the different points within the life-cycle of the stream.
==== attributes ====
The attributes defined in the {{{IMediaStream}}} interface which are not provided by this class are: * type * priority
In addition, the following attributes need to be defined in the subclass in order for the {{{MSRPStreamBase}}} class to take the correct decisions
'''media_type'''::
The media type as included in the SDP (eg. {{{"message"}}}, {{{"application"}}}).'''accept_types'''::
A list of the MIME types which should be accepted by the stream (this is also sent within the SDP).'''accept_wrapped_types'''::
A list of the MIME types which should be accepted by the stream while wrapped in a {{{message/cpim}}} envelope.'''use_msrp_session'''::
A boolean indicating whether or not an {{{MSRPSession}}} should be used.==== notifications ====
While not technically notifications of {{{MSRPStreamBase}}}, these notifications are sent from the middleware on behalf of the {{{MSRPTransport}}} used by a stream in the former case, and anonymously in the latter.
'''MSRPTransportTrace'''::
This notification is sent when an MSRP message is received for logging purposes.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]direction:[[BR]]
The direction of the message, {{{"incoming"}}} or {{{"outgoing"}}}.
[[BR]]data:[[BR]]
The MSRP message as a string.'''MSRPLibraryLog'''::
This notification is sent anonymously whenever the MSRP library needs to log any information.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]message:[[BR]]
The log message as a string.
[[BR]]level:[[BR]]
The log level at which the message was written. One of the levels {{{DEBUG}}}, {{{INFO}}}, {{{WARNING}}}, {{{ERROR}}}, {{{CRITICAL}}} from the {{{application.log.level}}} object which is part of the {{{python-application}}} library.=== ChatStream ===
Implemented in [browser:sipsimple/streams/msrp.py]
{{{sipsimple.streams.msrp.ChatStream}}} implements session-based Instant Messaging (IM) over MSRP. This class performs the following functions:
- automatically wraps outgoing messages with Message/CPIM if that's necessary according to accept-types
- unwraps incoming Message/CPIM messages; for each incoming message, the {{{ChatStreamGotMessage}}} notification is posted
- composes iscomposing payloads and reacts to those received by sending the {{{ChatStreamGotComposingIndication}}} notification
An example of an SDP created using this class follows:
{{{
Content-Type: application/sdp
Content-Length: 283
v=0
o=- 3467525214 3467525214 IN IP4 192.168.1.6
s=blink-0.10.7-beta
c=IN IP4 192.168.1.6
t=0 0
m=message 2855 TCP/TLS/MSRP
a=path:msrps://192.168.1.6:2855/ca7940f12ddef14c3c32;tcp
a=accept-types:message/cpim text/ application/im-iscomposing+xml
a=accept-wrapped-types:*
}}}
==== methods ====
{{{
Failure-Report: partial
Success-Report: yes
}}}
'''send_composing_indication'''(''self'', ''state'', ''refresh'', ''last_active=None'', ''recipients=None'')::
Sends an is-composing message to the listed recipients.
[[BR]]state:[[BR]]
The state of the endpoint, {{{"active"}}} or {{{"idle"}}}.
[[BR]]refresh:[[BR]]
How often the local endpoint will send is-composing indications to keep the state from being reverted to {{{"idle"}}}.
[[BR]]last_active:[[BR]]
A {{{datatime.datetime}}} object representing the moment when the local endpoint was last active.
[[BR]]recipients:[[BR]]
The list of {{{CPIMIdentity}}} objects which will be used for the {{{To}}} header of the CPIM wrapper. Used to override the default which depends on the remote identity.
May only differ from the default one if the remote party supports private messages. If it does not, a {{{ChatStreamError}}} will be raised.==== notifications ====
'''ChatStreamGotMessage'''::
Sent whenever a new incoming message is received,
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]message:[[BR]]
A {{{ChatMessage}}} or {{{CPIMMessage}}} instance, depending on whether a CPIM message was received or not.'''ChatStreamDidDeliverMessage'''::
Sent when a successful report is received.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]message_id:[[BR]]
Text identifier of the message.
[[BR]]code:[[BR]]
The status code received. Will always be 200 for this notification.
[[BR]]reason:[[BR]]
The status reason received.
[[BR]]chunk:[[BR]]
A {{{msrplib.protocol.MSRPData}}} instance providing all the MSRP information about the report.'''ChatStreamDidNotDeliverMessage'''::
Sent when a failure report is received.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]message_id:[[BR]]
Text identifier of the message.
[[BR]]code:[[BR]]
The status code received.
[[BR]]reason:[[BR]]
The status reason received.
[[BR]]chunk:[[BR]]
A {{{msrplib.protocol.MSRPData}}} instance providing all the MSRP information about the report.'''ChatStreamDidSendMessage'''::
Sent when an outgoing message has been sent.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]message:[[BR]]
A {{{msrplib.protocol.MSRPData}}} instance providing all the MSRP information about the sent message.'''ChatStreamGotComposingIndication'''::
Sent when a is-composing payload is received.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]state:[[BR]]
The state of the endpoint, {{{"active"}}} or {{{"idle"}}}.
[[BR]]refresh:[[BR]]
How often the remote endpoint will send is-composing indications to keep the state from being reverted to {{{"idle"}}}. May be {{{None}}}.
[[BR]]last_active:[[BR]]
A {{{datatime.datetime}}} object representing the moment when the remote endpoint was last active. May be {{{None}}}.
[[BR]]content_type:[[BR]]
The MIME type of message being composed. May be {{{None}}}.
[[BR]]sender:[[BR]]
The {{{ChatIdentity}}} or {{{CPIMIdentity}}} instance which identifies the sender of the is-composing indication.
[[BR]]recipients:[[BR]]
The {{{ChatIdentity}}} or {{{CPIMIdentity}}} instances list which identifies the recipients of the is-composing indication.=== FileSelector ===
The {{{FileSelector}}} is used to contain information about a file tranfer using the {{{FileTransferStream}}} documented below.
==== methods ====
'''!__init!__'''(''self'', '''name'''={{{None}}}, '''type'''={{{None}}}, '''size'''={{{None}}}, '''hash'''={{{None}}}, '''fd'''={{{None}}})::
Instantiate a new {{{FileSelector}}}. All the arguments are also available as attributes.
[[BR]]name:[[BR]]
The filename (should be just the base name).
[[BR]]type:[[BR]]
The type of the file.
[[BR]]size:[[BR]]
The size of the file in bytes.
[[BR]]hash:[[BR]]
The hash of the file in the following format: {{{hash:sha-1:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX}}}, where {{{X}}} is a hexadecimal digit. Currently, only SHA1 hashes are supported according to the RFC.
[[BR]]fd:[[BR]]
A file descriptor if the application has already opened the file.'''parse'''(''cls'', '''string''')::
Parses a file selector from the SDP {{{file-selector}}} a attribute and returns a {{{FileSelector}}} instance.'''for_file'''(''cls'', '''path''', '''content_type''', '''compute_hash'''={{{True}}})::
Returns a {{{FileSelector}}} instance for the specified file. The file identified by the path must exist. Note that if {{{compute_hash}}} is {{{True}}} this method will block while the hash is computed, a potentially long operation for large files.
[[BR]]path:[[BR]]
The full path to the file.
[[BR]]content_type:[[BR]]
An optional MIME type which is to be included in the file-selector.
[[BR]]compute_hash:[[BR]]
Whether or not this method should compute the hash of the file.'''compute_hash'''(''self'')::
Compute the hash for this file selector. This method will block while the hash is computed, a potentially long operation for large files.==== attributes ====
'''sdp_repr'''::
The SDP representation of the file-selector according to the RFC. This should be the value of the {{{file-selector}}} SDP attribute.=== FileTransferStream ===
Implemented in [browser:sipsimple/streams/msrp.py]
The {{{FileTransferStream}}} supports file transfer over MSRP according to RFC5547. An example of SDP constructed using this stream follows:
{{{
Content-Type: application/sdp
Content-Length: 383
v=0
o=- 3467525166 3467525166 IN IP4 192.168.1.6
s=blink-0.10.7-beta
c=IN IP4 192.168.1.6
t=0 0
m=message 2855 TCP/TLS/MSRP
a=path:msrps://192.168.1.6:2855/e593357dc9abe90754bd;tcp
a=sendonly
a=accept-types:
a=accept-wrapped-types:*
a=file-selector:name:"reblink.pdf" type:com.adobe.pdf size:268759 hash:sha1:60:A1:BE:8D:71:DB:E3:8E:84:C9:2C:62:9E:F2:99:78:9D:68:79:F6
}}}
==== methods ====
'''!__init!__'''(''self'', '''account''', '''file_selector'''={{{None}}})::
Instantiate a new {{{FileTransferStream}}}. If this is constructed by the application for an outgoing file transfer, the {{{file_selector}}} argument must be present.
[[BR]]account:[[BR]]
The {{{sipsimple.account.Account}}} or {{{sipsimple.account.BonjourAccount}}} instance which will be associated with the stream.
[[BR]]file_selector:[[BR]]
The {{{FileSelector}}} instance which represents the file which is to be transferred.==== notifications ====
'''FileTransferStreamDidDeliverChunk'''::
This notification is sent for an outgoing file transfer when a success report is received about part of the file being transferred.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]message_id:[[BR]]
The MSRP message ID of the file transfer session.
[[BR]]chunk:[[BR]]
An {{{msrplib.protocol.MSRPData}}} instance represented the received REPORT.
[[BR]]code:[[BR]]
The status code received. Will always be 200 for this notification.
[[BR]]reason:[[BR]]
The status reason received.
[[BR]]transferred_bytes:[[BR]]
The number of bytes which have currently been successfully transferred.
[[BR]]file_size:[[BR]]
The size of the file being transferred.'''FileTransferStreamDidNotDeliverChunk'''::
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
This notification is sent for an outgoing file transfer when a failure report is received about part of the file being transferred.
[[BR]]message_id:[[BR]]
The MSRP message ID of the file transfer session.
[[BR]]chunk:[[BR]]
An {{{msrplib.protocol.MSRPData}}} instance represented the received REPORT.
[[BR]]code:[[BR]]
The status code received.
[[BR]]reason:[[BR]]
The status reason received.'''FileTransferStreamDidFinish'''::
This notification is sent when the incoming or outgoing file transfer is finished.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''FileTransferStreamGotChunk'''::
This notificaiton is sent for an incoming file transfer when a chunk of file data is received.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]content:[[BR]]
The file part which was received, as a {{{str}}}.
[[BR]]content_type:[[BR]]
The MIME type of the file which is being transferred.
[[BR]]transferred_bytes:[[BR]]
The number of bytes which have currently been successfully transferred.
[[BR]]file_size:[[BR]]
The size of the file being transferred.=== IDesktopSharingHandler ===
This interface is used to describe the interface between a {{{IDesktopSharingHandler}}}, which is responsible for consuming and producing RFB data, and the {{{DesktopSharingStream}}} which is responsible for transporting the RFB data over MSRP. The middleware provides four implementations of this interface: * InternalVNCViewerHandler * InternalVNCServerHandler * ExternalVNCViewerHandler * ExternalVNCServerHandler
==== methods ====
'''initialize'''(''self'', '''stream''')::
This method will be called by the {{{DesktopSharingStream}}} when the stream has been started and RFB data can be transported. The stream has two attributes which are relevant to the {{{IDesktopSharingHandler}}}: incoming_queue and outgoing_queue. These attributes are {{{eventlet.coros.queue}}} instances which are used to transport RFB data between the stream and the handler.==== attributes ====
'''type'''::
{{{"active"}}} or {{{"passive"}}} depending on whether the handler represents a VNC viewer or server respectively.==== notifications ====
'''DesktopSharingHandlerDidFail'''::
This notification must be sent by the handler when an error occurs to notify the stream that it should fail.
[[BR]]context:[[BR]]
A string describing when the handler failed, such as {{{"reading"}}}, {{{"sending"}}} or {{{"connecting"}}}.
[[BR]]failure:[[BR]]
A {{{twisted.python.failure.Failure}}} instance describing the exception which led to the failure.
[[BR]]reason:[[BR]]
A string describing the failure reason.=== InternalVNCViewerHandler ===
This is a concrete implementation of the {{{IDesktopSharingHandler}}} interface which can be used for a VNC viewer implemented within the application.
==== methods ====
'''send'''(''self'', '''data''')::
Sends the specified data to the stream in order for it to be transported over MSRP to the remote endpoint.
[[BR]]data:[[BR]]
The RFB data to be transported over MSRP, in the form of a {{{str}}}.==== notifications ====
'''DesktopSharingStreamGotData'''::
This notification is sent when data is received over MSRP.
[[BR]]data:[[BR]]
The RFB data from the remote endpoint, in the form of a {{{str}}}.=== InternalVNCServerHandler ===
This is a concrete implementation of the {{{IDesktopSharingHandler}}} interface which can be used for a VNC server implemented within the application.
==== methods ====
'''send'''(''self'', '''data''')::
Sends the specified data to the stream in order for it to be transported over MSRP to the remote endpoint.
[[BR]]data:[[BR]]
The RFB data to be transported over MSRP, in the form of a {{{str}}}.==== notifications ====
'''DesktopSharingStreamGotData'''::
This notification is sent when data is received over MSRP.
[[BR]]data:[[BR]]
The RFB data from the remote endpoint, in the form of a {{{str}}}.=== ExternalVNCViewerHandler ===
This implementation of {{{IDesktopSharingHandler}}} can be used for an external VNC viewer which connects to a VNC server using TCP.
==== methods ====
'''!__init!__'''(''self'', '''address'''={{{("localhost", 0)}}}, '''connect_timeout'''={{{3}}})::
This instantiates a new {{{ExternalVNCViewerHandler}}} which is listening on the provided address, ready for the external VNC viewer to connect to it via TCP. After this method returns, the attribute {{{address}}} can be used to find out exactly on what address and port the handler is listening on. The handler will only accept one conenction on this address.
[[BR]]address:[[BR]]
A tuple containing an IP address/hostname and a port on which the handler should listen. Any data received on this socket will then be forwarded to the stream and any data received from the stream will be forwarded to this socket.==== attributes ====
'''address'''::
A tuple containing an IP address and a port on which the handler is listening.=== ExternalVNCServerHandler ===
This implementation of {{{IDesktopSharingHandler}}} can be used for an external VNC server to which handler will connect using TCP.
==== methods ====
'''!__init!__'''(''self'', '''address''', '''connect_timeout'''={{{3}}})::
This instantiates a new {{{ExternalVNCServerHandler}}} which will connect to the provided address on which a VNC server must be listening before the stream using this handler starts.
[[BR]]address:[[BR]]
A tuple containing an IP address/hostname and a port on which the VNC server will be listening. Any data received on this socket will then be forwared to the stream and any data received form the stream will be forwarded to this socket.
[[BR]]connect_timeout:[[BR]]
How long to wait to connect to the VNC server before giving up.=== DesktopSharingStream ===
Implemented in [browser:sipsimple/streams/msrp.py]
This stream implements desktop sharing using MSRP as a transport protocol for RFB data.
There is no standard defining this usage but is fairly easy to implement in clients that already support MSRP. To traverse a NAT-ed router, a [http://msrprelay.org MSRP relay] configured for the called party domain is needed. Below is an example of the Session Description Protocol used for establishing a Desktop sharing session:
{{{
m=application 2855 TCP/TLS/MSRP *
a=path:msrps://10.0.1.19:2855/b599b22d1b1d6a3324c8;tcp
a=accept-types:application/x-rfb
a=rfbsetup:active
}}}
==== methods ====
'''!__init!__'''(''self'', '''acount''', '''handler''')::
Instantiate a new {{{DesktopSharingStream}}}.
[[BR]]account:[[BR]]
The {{{sipsimple.account.Account}}} or {{{sipsimple.account.BonjourAccount}}} instance this stream is associated with.
[[BR]]handler:[[BR]]
An object implementing the {{{IDesktopSharingHandler}}} interface which will act as the handler for RFB data.==== attributes ====
'''handler'''::
This is a writable property which can be used to get or set the object implementing {{{IDesktopSharingHandler}}} which acts as the handler for RFB data. For incoming {{{DesktopSharingStreams}}}, this must be set by the application before the stream starts.'''incoming_queue'''::
A {{{eventlet.coros.queue}}} instance on which incoming RFB data is written. The handler should wait for data on this queue.'''outgoing_queue'''::
A {{{eventlet.coros.queue}}} instance on which outgoing RFB data is written. The handler should write data on this queue.=== ConferenceHandler ===
This class is internal to the {{{Session}}} and provied the user with the ability to invite participants to a conference hosted by the remote endpoint.
Adding and removing participants is performed using a {{{REFER}}} request as explained in RFC 4579, section 5.5.
In addition, the {{{ConferenceHandler}}} will subscribe to the {{{conference}}} event in order to get information about participants in the conference.
==== methods ====
'''add_participant'''(''self'', '''participant_uri''')::
Send a {{{REFER}}} request telling the server to invite the participant specified in {{{participant_uri}}} to join the ongoing conference.'''remove_participant'''(''self'', '''participant_uri''')::
Send a {{{REFER}}} request telling the server to remove the participant specified in {{{participant_uri}}} from the ongoing conference.==== notifications ====
All notifications are sent with the {{{Session}}} object as the sender.'''SIPSessionGotConferenceInfo'''::
This notification is sent when a {{{NOTIFY}}} is received with a valid conferene payload.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]conference_info:[[BR]]
The {{{Conference}}} payload object.'''SIPConferenceDidAddParticipant'''::
This notification is sent when a participant was successfully added to the conference.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]participant:[[BR]]
URI of the participant added to the conference.'''SIPConferenceDidNotAddParticipant'''::
This notification is sent when a participant could not be added to the conference.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]participant:[[BR]]
URI of the participant added to the conference.
[[BR]]code:[[BR]]
SIP response code for the failure.
[[BR]]reason:[[BR]]
Reason for the failure.'''SIPConferenceDidRemoveParticipant'''::
This notification is sent when a participant was successfully removed from the conference.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]participant:[[BR]]
URI of the participant removed from the conference.'''SIPConferenceDidNotRemoveParticipant'''::
This notification is sent when a participant could not be removed from the conference.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]participant:[[BR]]
URI of the participant removed from the conference.
[[BR]]code:[[BR]]
SIP response code for the failure.
[[BR]]reason:[[BR]]
Reason for the failure.'''SIPConferenceGotAddParticipantProgress'''::
This notification is sent when a {{{NOTIFY}}} is received indicating the status of the add participant operation.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]participant:[[BR]]
URI of the participant whose operation is in progress.
[[BR]]code:[[BR]]
SIP response code for progress.
[[BR]]reason:[[BR]]
Reason associated with the response code.'''SIPConferenceGotRemoveParticipantProgress'''::
This notification is sent when a {{{NOTIFY}}} is received indicating the status of the remove participant operation.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]participant:[[BR]]
URI of the participant whose operation is in progress.
[[BR]]code:[[BR]]
SIP response code for progress.
[[BR]]reason:[[BR]]
Reason associated with the response code.The SIP SIMPLE middleware offers the {{{sipsimple.lookup}}} module which contains an implementation for doing DNS lookups for SIP proxies, MSRP relays, STUN servers and XCAP servers. The interface offers both an asynchronous and synchronous interface. The asynchronous interface is based on notifications, while the synchronous one on green threads. In order to call the methods in a asynchronous manner, you just need to call the method and wait for the notification which is sent on behalf of the DNSLookup instance. The notifications sent by the DNSLookup object are DNSLookupDidSucceed and DNSLookupDidFail. In order to call the methods in a synchronous manner, you need to call the wait method on the object returned by the methods of DNSLookup. This wait method needs to be called from a green thread and will either return the result of the lookup or raise an exception.
The DNSLookup object uses DNSManager, an object that will use the system nameservers and it will fallback to Google's nameservers (8.8.8.8 and 8.8.4.4) in case of failure.
=== DNS Manager ===
This object provides {{{DNSLookup}}} with the nameserver list that will be used to perform DNS lookups. It will probe the system local nameservers and check if they are able to do proper lookups (by querying sip2sip.info domain). If the local nameservers are not able to do proper lookups Google nameservers will be used and another probing operation will be scheduled. Local nameservers are always preferred.
==== methods ====
'''!__init!__'''(''self'')::
Instantiate the DNSManager object (it's a Singleton).'''start'''(''self'')::
Start the DNSManager. It will start the probing process to determine the suitable nameservers to use.'''stop'''(''self'')::
Stop the DNS resolution probing.==== notifications ====
'''DNSResolverDidInitialize'''::
This notification is sent when the nameservers to use for probing (and further DNS lookups) have been set for the first time.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]nameservers:[[BR]]
The list of nameservers that was set on the DNS Manager.'''DNSNameserversDidChange'''::
This notification is sent when the nameservers to use for probing (and further DNS lookups) have changed as a result of the probing process.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]nameservers:[[BR]]
The list of nameservers that was set on the DNS Manager.=== DNS Lookup ===
This object implements DNS lookup support for SIP proxies according to RFC3263 and MSRP relay and STUN server lookup using SRV records. The object initially does NS record queries in order to determine the authoritative nameservers for the domain requested; these authoritative nameservers will then be used for NAPTR, SRV and A record queries. If this fails, the locally configured nameservers are used. The reason for doing this is that some home routers have broken NAPTR and/or SRV query support.
==== methods ====
'''!__init!__'''(''self'')::
Instantiate a new DNSLookup object.'''lookup_service'''(''self'', '''uri''', '''service''', '''timeout'''={{{3.0}}}, '''lifetime'''={{{15.0}}})::
Perform an SRV lookup followed by A lookups for MSRP relays or STUN servers depending on the {{{service}}} parameter. If SRV queries on the {{{uri.host}}} domain fail, an A lookup is performed on it and the default port for the service is returned. Only the {{{uri.host}}} attribute is used. The return value is a list of (host, port) tuples.
[[BR]]uri:[[BR]]
A {{{(Frozen)SIPURI}}} from which the {{{host}}} attribute is used for the query domain.
[[BR]]service:[[BR]]
The service to lookup servers for, {{{"msrprelay"}}} or {{{"stun"}}}.
[[BR]]timeout:[[BR]]
How many seconds to wait for a response from a nameserver.
[[BR]]lifetime:[[BR]]
How many seconds to wait for a response from all nameservers in total.'''lookup_sip_proxy'''(''self'', '''uri''', '''supported_transports''', '''timeout'''={{{3.0}}}, '''lifetime'''={{{15.0}}})::
Perform a RFC3263 compliant DNS lookup for a SIP proxy using the URI which is considered to point to a host if either the {{{host}}} attribute is an IP address, or the {{{port}}} is present. Otherwise, it is considered a domain for which NAPTR, SRV and A lookups are performed. If NAPTR or SRV queries fail, they fallback to using SRV and A queries. If the transport parameter is present in the URI, this will be used as far as it is part of the supported transports. If the URI has a {{{sips}}} schema, then only the TLS transport will be used as far as it doesn't conflict with the supported transports or the transport parameter. The return value is a list of {{{Route}}} objects containing the IP address, port and transport to use for routing in the order of preference given by the supported_transports argument.
[[BR]]uri:[[BR]]
A {{{(Frozen)SIPURI}}} from which the {{{host}}}, {{{port}}}, {{{parameters}}} and {{{secure}}} attributes are used.
[[BR]]supported_transports:[[BR]]
A sublist of {{{['udp', 'tcp', 'tls']}}} in the application's order of preference.
[[BR]]timeout:[[BR]]
How many seconds to wait for a response from a nameserver.
[[BR]]lifetime:[[BR]]
How many seconds to wait for a response from all nameservers in total.'''lookup_xcap_server'''(''self'', '''uri''', '''timeout'''={{{3.0}}}, '''lifetime'''={{{15.0}}})::
Perform a TXT DNS query on xcap.<uri.host> and return all values of the TXT record which are URIs with a scheme of http or https. Only the {{{uri.host}}} attribute is used. The return value is a list of strings representing HTTP URIs.
[[BR]]uri:[[BR]]
A {{{(Frozen)SIPURI}}} from which the {{{host}}} attribute is used for the query domain.
[[BR]]timeout:[[BR]]
How many seconds to wait for a response from a nameserver.
[[BR]]lifetime:[[BR]]
How many seconds to wait for a response from all nameservers in total.==== notifications ====
'''DNSLookupDidSucceed'''::
This notification is sent when one of the lookup methods succeeds in finding a result.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]result:[[BR]]
The result of the DNS lookup in the format described in each method.'''DNSLookupDidFail'''::
This notification is sent when one of the lookup methods fails in finding a result.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]error:[[BR]]
A {{{str}}} object describing the error which resulted in the DNS lookup failure.'''DNSLookupTrace'''::
This notification is sent several times during a lookup process for each individual DNS query.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]query_type:[[BR]]
The type of the query, {{{"NAPTR"}}}, {{{"SRV"}}}, {{{"A"}}}, {{{"NS"}}} etc.
[[BR]]query_name:[[BR]]
The name which was queried.
[[BR]]answer:[[BR]]
The answer returned by dnspython, or {{{None}}} if an error occurred.
[[BR]]error:[[BR]]
The exception which caused the query to fail, or {{{None}}} if no error occurred.
[[BR]]context:[[BR]]
The name of the method which was called on the {{{DNSLookup}}} object.
[[BR]]service:[[BR]]
The service which was queried for, only available when context is {{{"lookup_service"}}}.
[[BR]]uri:[[BR]]
The uri which was queried for.
[[BR]]nameservers:[[BR]]
The list of nameservers that was used to perform the lookup.=== Route ===
This is a convinience object which contains sufficient information to identify a route to a SIP proxy. This object is returned by {{{DNSLookup.lookup_sip_proxy}}} and can be used with the {{{Session}}} or a {{{(Frozen)RouteHeader}}} can be easily constructed from it to pass to one of the objects in the SIP core handling SIP dialogs/transactions ({{{Invitation}}}, {{{Subscription}}}, {{{Request}}}, {{{Registration}}}, {{{Message}}}, {{{Publication}}}). This object has three attributes which can be set in the constructor or after it was instantiated. They will only be documented as arguments to the constructor.
==== methods ====
'''!__init!__'''(''self'', '''address''', '''port'''=None, '''transport'''={{{'udp'}}})::
Creates the Route object with the specified parameters as attributes.
Each of these attributes can be accessed on the object once instanced.
[[BR]]''address'':[[BR]]
The IPv4 address that the request in question should be sent to as a string.
[[BR]]''port'':[[BR]]
The port to send the requests to, represented as an int, or None if the default port is to be used.
[[BR]]''transport'':[[BR]]
The transport to use, this can be a string of either "udp", "tcp" or "tls" (case insensitive).'''get_uri'''(''self'')::
Returns a {{{SIPURI}}} object which contains the adress, port and transport as parameter. This can be used to easily construct a {{{RouteHeader}}}:
{{{
route = Route("1.2.3.4", port=1234, transport="tls")
route_header = RouteHeader(route.get_uri())
}}}Account Management is implemented in [browser:sipsimple/account.py] ({{{sipsimple.account}}} module) and offers support for SIP accounts registered at SIP providers and SIP bonjour accounts which are discovered using mDNS.
=== AccountManager ===
The {{{sipsimple.account.AccountManager}}} is the entity responsible for loading and keeping track of the existing accounts. It is a singleton and can be instantiated anywhere, obtaining the same instance. It cannot be used until its {{{start}}} method has been called.
==== methods ====
'''!__init!__'''(''self'')::
The {{{__init__}}} method allows the {{{AccountManager}}} to be instantiated without passing any parameters. A reference to the {{{AccountManager}}} can be obtained anywhere before it is started.'''start'''(''self'')::
This method will load all the existing accounts from the configuration. If the Engine is running, the accounts will also activate. This method can only be called after the [wiki:SipConfigurationAPI#ConfigurationManager ConfigurationManager] has been started. A '''SIPAccountManagerDidAddAccount''' will be sent for each account loaded. This method is called automatically by the SIPApplication when it initializes all the components of the middleware.'''stop'''(''self'')::
Calling this method will deactivate all accounts managed by the {{{AccountManager}}}. This method is called automatically by the SIPApplication when it stops.'''has_account'''(''self'', '''id''')::
This method returns {{{True}}} if an account which has the specifed SIP ID (must be a string) exists and {{{False}}} otherwise.'''get_account'''(''self'', '''id''')::
Returns the account (either an {{{Account}}} instance or the {{{BonjourAccount}}} instance) with the specified SIP ID. Will raise a {{{KeyError}}} if such an account does not exist.'''get_accounts'''(''self'')::
Returns a list containing all the managed accounts.'''iter_accounts'''(''self'')::
Returns an iterator through all the managed accounts.'''find_account'''(''self'', '''contact_uri''')::
Returns an account with matches the specified {{{contact_uri}}} which must be a {{{sipsimple.core.SIPURI}}} instance. Only the accounts with the enabled flag set will be considered. Returns None if such an account does not exist.==== notifications ====
'''SIPAccountManagerDidAddAccount'''::
This notification is sent when a new account becomes available to the {{{AccountManager}}}. The notification is also sent when the accounts are loaded from the configuration.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''account'':[[BR]]
The account object which was added.'''SIPAccountManagerDidRemoveAccount'''::
This notification is sent when an account is deleted using the {{{delete}}} method.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''account'':[[BR]]
The account object which was deleted.'''SIPAccountManagerDidChangeDefaultAccount'''::
This notification is sent when the default account changes.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''old_account'':[[BR]]
This is the account object which used to be the default account.
[[BR]]''account'':[[BR]]
This is the account object which is the new default account.=== Account ===
The {{{sipsimple.account.Account}}} objects represent the SIP accounts which are registered at SIP providers. It has a dual purpose: it acts as both a container for account-related settings and as a complex object which can be used to interact with various per-account functions, such as presence, registration etc. This page documents the latter case, while the former is explained in the [wiki:SipConfigurationAPI#Account Configuration API].
There is exactly one instance of {{{Account}}} per SIP account used and it is uniquely identifiable by its SIP ID, in the form ''user@domain''. It is a singleton, in the sense that instantiating {{{Account}}} using an already used SIP ID will return the same object. However, this is not the recommended way of accessing accounts, as this can lead to creation of new ones; the recommended way is by using the [wiki:SipMiddlewareApi#AccountManager AccountManager]. The next sections will use a lowercase, monospaced {{{account}}} to represent an instance of {{{Account}}}.
==== states ====
The {{{Account}}} objects have a setting flag called {{{enabled}}} which, if set to {{{False}}} will deactivate it: none of the internal functions will work in this case; in addition, the application using the middleware should not do anything with a disabled account. After changing it's value, the {{{save()}}} method needs to be called, as the flag is a setting and will not be used until this method is called:
{{{
account.enabled = True
account.save()
}}}
The {{{Account}}} objects will activate automatically when they are loaded/created if the {{{enabled}}} flag is set to {{{True}}} and the {{{sipsimple.engine.Engine}}} is running; if it is not running, the accounts will activate after the engine starts.
In order to create a new account, just create a new instance of {{{Account}}} with an id which doesn't belong to any other account.
The other functions of {{{Account}}} which run automatically have other enabled flags as well. They will only be activated when both the global enabled flag is set and the function-specific one. These are:
'''Account.registration.enabled'''::
This flag controls the automatic registration of the account. The notifications '''SIPAccountRegistrationDidSucceed''', '''SIPAccountRegistrationDidFail''' and '''SIPAccountRegistrationDidEnd''' are used to inform the status of this registration.'''Account.presence.enabled'''::
This flag controls the automatic subscription to buddies for the ''presence'' event and the publication of data in this event. (Not implemented yet)'''Account.dialog_event.enabled'''::
This flag controls the automatic subscription to buddies for the ''dialog-info'' event and the publication of data in this event. (Not implemented yet)'''Account.message_summary.enabled'''::
This flag controls the automatic subscription to the ''message-summary'' event in order to find out about voicemail messages. (Not implemented yet)The {{{save()}}} method needs to be called after changing these flags in order for them to take effect. The methods available on {{{Account}}} objects are inherited from [wiki:SipConfigurationAPI#SettingsObject SettingsObject].
==== attributes ====
The following attributes can be used on an Account object and need to be considered read-only.
'''id'''::
This attribute is of type {{{sipsimple.configuration.datatypes.SIPAddress}}} (a subclass of {{{str}}}) and contains the SIP id of the account. It can be used as a normal string in the form ''user@domain'', but it also allows access to the components via the attributes {{{username}}} and {{{domain}}}.
{{{
account.id # 'alice@example.com'
account.id.username # 'alice'
account.id.domain # 'example.com'
}}}'''contact'''::
This attribute can be used to construct the Contact URI for SIP requests sent on behalf of this account. It's type is {{{sipsimple.account.ContactURIFactory}}}. It can be indexed by a string representing a transport ({{{'udp'}}}, {{{'tcp'}}}, {{{'tls'}}}) or a {{{sipsimple.util.Route}}} object which will return a {{{sipsimple.core.SIPURI}}} object with the appropriate IP, port and transport. The username part is a randomly generated 8 character string consisting of lowercase letters; but it can be chosen by passing it to init when building the {{{ContactURIFactory}}} object.
{{{
account.contact # 'ContactURIFactory(username=hnfkybrt)'
account.contact.username # 'hnfkybrt'
account.contact['udp'] # <SIPURI "sip:hnfkybrt@10.0.0.1:53024">
account.contact['tls'] # <SIPURI "sip:hnfkybrt@10.0.0.1:54478;transport=tls">
}}}'''credentials'''::
This attribute is of type {{{sipsimple.core.Credentials}}} which is built from the {{{id.username}}} attribute and the {{{password}}} setting of the Account. Whenever this setting is changed, this attribute is updated.
{{{
account.credentials # <Credentials for 'alice'>
}}}'''uri'''::
This attribute is of type {{{sipsimple.core.SIPURI}}} which can be used to form a {{{FromHeader}}} associated with this account. It contains the SIP ID of the account.
{{{
account.uri # <SIPURI "sip:alice@example.com">
}}}==== notifications ====
'''CFGSettingsObjectDidChange'''::
This notification is sent when the {{{save()}}} method is called on the account after some of the settings were changed. As the notification belongs to the {{{SettingsObject}}} class, it is exaplained in detail in [wiki:SipConfigurationAPI#SettingsObjectNotifications SettingsObject Notifications].'''SIPAccountWillActivate'''::
This notification is sent when the {{{Account}}} is about to be activated, but before actually performing any activation task. See {{{SIPAccountDidActivate}}} for more detail.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountDidActivate'''::
This notification is sent when the {{{Account}}} activates. This can happen when the {{{Account}}} is loaded if it's enabled flag is set and the Engine is running, and at any later time when the status of the Engine changes or the enabled flag is modified.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountWillDeactivate'''::
This notification is sent when the {{{Account}}} is about to be deactivated, but before performing any deactivation task. See {{{SIPAccountDidDeactivate}}} for more detail.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountDidDeactivate'''::
This notification is sent when the {{{Account}}} deactivates. This can happend when the {{{Engine}}} is stopped or when the enabled flag of the account is set to {{{False}}}.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountWillRegister'''::
This notification is sent when the account is about to register for the first time.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountRegistrationWillRefresh'''::
This notification is sent when a registration is about to be refreshed.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountRegistrationDidSucceed'''::
This notification is sent when a REGISTER request sent for the account succeeds (it is also sent for each refresh of the registration). The data contained in this notification is:
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''contact_header'':[[BR]]
The Contact header which was registered.
[[BR]]''contact_header_list'':[[BR]]
A list containing all the contacts registered for this SIP account.
[[BR]]''expires'':[[BR]]
The amount in seconds in which this registration will expire.
[[BR]]''registrar'':[[BR]]
The {{{sipsimple.util.Route}}} object which was used.'''SIPAccountRegistrationDidFail'''::
This notification is sent when a REGISTER request sent for the account fails. It can fail either because a negative response was returned or because PJSIP considered the request failed (e.g. on timeout). The data contained in this notification is:
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''error'':[[BR]]
The reason for the failure of the REGISTER request.
[[BR]]''timeout'':[[BR]]
The amount in seconds as a {{{float}}} after which the registration will be tried again.'''SIPAccountRegistrationDidEnd'''::
This notification is sent when a registration is ended (the account is unregistered). The data contained in this notification is:
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''registration'':[[BR]]
The {{{sipsimple.core.Registration}}} object which ended.'''SIPAccountRegistrationDidNotEnd'''::
This notification is sent when a registration fails to end (the account is not unregistered). The data contained in this notification is:
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''code'':[[BR]]
The SIP status code received.
[[BR]]''reason'':[[BR]]
The SIP status reason received.
[[BR]]''registration'':[[BR]]
The {{{sipsimple.core.Registration}}} object which ended.'''SIPAccountRegistrationGotAnswer'''::
This notification is sent whenever a response is received to a sent REGISTER request for this account. The data contained in this notification is:
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''code'':[[BR]]
The SIP status code received.
[[BR]]''reason'':[[BR]]
The SIP status reason received.
[[BR]]''registration'':[[BR]]
The {{{sipsimple.core.Registration}}} object which was used.
[[BR]]''registrar'':[[BR]]
The {{{sipsimple.util.Route}}} object which was used.'''SIPAccountMWIDidGetSummary'''::
This notification is sent when a NOTIFY is received with a message-summary payload. The data contained in this notification is:
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]''message_summary'':[[BR]]
A {{{sipsimple.payloads.messagesummary.MessageSummary}}} object with the parsed payload from the NOTIFY request.=== BonjourAccount ===
The {{{sipsimple.account.BonjourAccount}}} represents the SIP account used for P2P mode; it does not interact with any server. The class is a singleton, as there can only be one such account on a system. Similar to the {{{Account}}}, it is used both as a complex object, which implements the functions for bonjour mode, as well as a container for the related settings.
==== states ====
The {{{BonjourAccount}}} has an {{{enabled}}} flag which controls whether this account will be used or not. If it is set to {{{False}}}, none of the internal functions will be activated and, in addition, the account should not be used by the application. The bonjour account can only activated if the Engine is running; once it is started, if the enabled flag is set, the account will activate. When the {{{BonjourAccount}}} is activated, it will broadcast the contact address on the LAN and discover its neighbours sending notifications as this happens.
==== attributes ====
The following attributes can be used on a BonjourAccount object and need to be considered read-only.
'''id'''::
This attribute is of type {{{sipsimple.configuration.datatypes.SIPAddress}}} (a subclass of {{{str}}}) and contains the SIP id of the account, which is {{{'bonjour@local'}}}. It can be used as a normal string, but it also allows access to the components via the attributes {{{username}}} and {{{domain}}}.
{{{
bonjour_account.id # 'bonjour@local'
bonjour_account.id.username # 'bonjour'
bonjour_account.id.domain # 'local'
}}}'''contact'''::
This attribute can be used to construct the Contact URI for SIP requests sent on behalf of this account. It's type is {{{sipsimple.account.ContactURIFactory}}}. It can be indexed by a string representing a transport ({{{'udp'}}}, {{{'tcp'}}}, {{{'tls'}}}) or a {{{sipsimple.util.Route}}} object which will return a {{{sipsimple.core.SIPURI}}} object with the appropriate IP, port and transport. The username part is a randomly generated 8 character string consisting of lowercase letters; but it can be chosen by passing it to init when building the {{{ContactURIFactory}}} object.
{{{
bonjour_account.contact # 'ContactURIFactory(username=lxzvgack)'
bonjour_account.contact.username # 'lxzvgack'
bonjour_account.contact['udp'] # <SIPURI "sip:lxzvgack@10.0.0.1:53024">
bonjour_account.contact['tls'] # <SIPURI "sip:lxzvgack@10.0.0.1:54478;transport=tls">
}}}'''credentials'''::
This attribute is of type {{{sipsimple.core.Credentials}}} object which is built from the {{{contact.username}}} attribute; the password is set to the empty string.
{{{
bonjour_account.credentials # <Credentials for 'alice'>
}}}'''uri'''::
This attribute is of type {{{sipsimple.core.SIPURI}}} which can be used to form a {{{FromHeader}}} associated with this account. It contains the contact address of the bonjour account:
{{{
bonjour_account.uri # <SIPURI "sip:lxzvgack@10.0.0.1">
}}}==== notifications ====
'''BonjourAccountDidAddNeighbour'''::
This notification is sent when a new Bonjour neighbour is discovered.
[[BR]]''service_description'':[[BR]]
BonjourServiceDescription object uniquely identifying this neighbour in the mDNS library.
[[BR]]''display_name'':[[BR]]
The name of the neighbour as it is published.
[[BR]]''host'':[[BR]]
The hostname of the machine from which the Bonjour neighbour registered its contact address.
[[BR]]''uri'':[[BR]]
The contact URI of the Bonjour neighbour, as a {{{FrozenSIPURI}}} object.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''BonjourAccountDidUpdateNeighbour'''::
This notification is sent when an existing Bonjour neighbour has updates its published data.
[[BR]]''service_description'':[[BR]]
BonjourServiceDescription object uniquely identifying this neighbour in the mDNS library.
[[BR]]''display_name'':[[BR]]
The name of the neighbour as it is published.
[[BR]]''host'':[[BR]]
The hostname of the machine from which the Bonjour neighbour registered its contact address.
[[BR]]''uri'':[[BR]]
The contact URI of the Bonjour neighbour, as a {{{FrozenSIPURI}}} object.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''BonjourAccountDidRemoveNeighbour'''::
This notification is sent when a Bonjour neighbour unregisters.
[[BR]]''service_description'':[[BR]]
The BonjourServiceDescription object, which uniquely identifies a neighbour, that got unregistered.'''BonjourAccountDiscoveryDidFail'''::
This notification is sent once per transport when the Bonjour account has failed to perform the discovery process for the indicated transport.
[[BR]]''reason'':[[BR]]
String defining the reason of the failure.
[[BR]]''transport'':[[BR]]
String specifying the transport for which the discovery failed.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''BonjourAccountDiscoveryFailure'''::
This notification is sent once per transport when the Bonjour account has encountered a problem while browsing the list of neighbours for the indicated transport.
[[BR]]''error'':[[BR]]
String defining the error of the failure.
[[BR]]''transport'':[[BR]]
String specifying the transport for which the neighbour resoution failed.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''BonjourAccountRegistrationDidEnd'''::
This notification is sent once per transport when the Bonjour account unregisters its contact address for the indicated transport using mDNS.
[[BR]]''transport'':[[BR]]
String specifying the transport for which the registration ended.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''BonjourAccountRegistrationDidFail'''::
This notification is sent once per transport when the Bonjour account fails to register its contact address for the indicated transport using mDNS.
[[BR]]''reason'':[[BR]]
A human readable error message.
[[BR]]''transport'':[[BR]]
String specifying the transport for which the registration failed.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''BonjourAccountRegistrationUpdateDidFail'''::
This notification is sent once per transport when the Bonjour account fails to update its data for the indicated transport using mDNS.
[[BR]]''reason'':[[BR]]
A human readable error message.
[[BR]]''transport'':[[BR]]
String specifying the transport for which the registration update failed.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''BonjourAccountRegistrationDidSucceed'''::
This notification is sent once per transport when the Bonjour account successfully registers its contact address for the indicated transport using mDNS.
[[BR]]''name'':[[BR]]
The contact address registered.
[[BR]]''transport'':[[BR]]
String specifying the transport for which the registration succeeded.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''BonjourAccountWillInitateDiscovery'''::
This notification is sent when the Bonjour account is about to start the discovery process for the indicated transport.
[[BR]]''transport'':[[BR]]
String specifying the transport for which the discovery will be started.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''BonjourAccountWillRegister'''::
This notification is sent just before the Bonjour account starts the registering process for the indicated transport.
[[BR]]''transport'':[[BR]]
String specifying the transport for which the registration will be started.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''CFGSettingsObjectDidChange'''::
This notification is sent when the {{{save()}}} method is called on the account after some of the settings were changed. As the notification belongs to the {{{SettingsObject}}} class, it is exaplained in detail in [wiki:SipConfigurationAPI#SettingsObjectNotifications SettingsObject Notifications].
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountWillActivate'''::
This notification is sent when the {{{BonjourAccount}}} is about to be activated, but before actually performing any activation task. See {{{SIPAccountDidActivate}}} for more detail.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountDidActivate'''::
This notification is sent when the {{{BonjourAccount}}} activates. This can happen when the {{{BonjourAccount}}} is loaded if it's enabled flag is set and the Engine is running, and at any later time when the status of the Engine changes or the enabled flag is modified.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountWillDeactivate'''::
This notification is sent when the {{{BonjourAccount}}} is about to be deactivated, but before performing any deactivation task. See {{{SIPAccountDidDeactivate}}} for more detail.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''SIPAccountDidDeactivate'''::
This notification is sent when the {{{BonjourAccount}}} deactivates. This can happend when the {{{Engine}}} is stopped or when the enabled flag of the account is set to {{{False}}}.
[[BR]]''timestamp'':[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.The high-level audio API hides the complexity of using the low-level PJMEDIA interface. This is implemented in the {{{sipsimple.audio}}} module and contains the following components: * IAudioPort: an interface describing an object capable of producing and/or consuming audio data. * AudioDevice: an object conforming to the IAudioPort interface which describes a physical audio device. * AudioBridge: a collection of objects conforming to IAudioPort which connects all of them in a full mesh. * WavePlayer: an object conforming to the IAudioPort interface which can playback the audio data from a {{{.wav}}} file. * WaveRecorder: an object conforming to the IAudioPort interface which can record audio data to a {{{.wav}}} file.
=== IAudioPort ===
The IAudioPort interface describes an object capable of producing and/or consuming audio data. This can be a dynamic object, which changes its role during its lifetime and notifies such changes using a notification, which is part of the interface.
==== attributes ====
'''mixer'''::
The {{{AudioMixer}}} this audio object is connected to. Only audio objects connected to the same mixer will be able to send audio data from one to another.'''consumer_slot'''::
An integer representing the slot (see [wiki:SipCoreApiDocumentation#AudioMixer AudioMixer]) which this object uses to consume audio data, or {{{None}}} if this object is not a consumer.'''producer_slot'''::
An integer representing the slot (see [wiki:SipCoreApiDocumentation#AudioMixer AudioMixer]) which this object uses to produce audio data, or {{{None}}} if this object is not a producer.==== notifications ====
'''AudioPortDidChangeSlots'''::
This notification needs to be sent by implementations of this interface when the slots it has change, so as to let the {{{AudioBridges}}} it is part of know that reconnections need to be made.
[[BR]]consumer_slot_changed:[[BR]]
A bool indicating whether the consumer slot was changed.
[[BR]]producer_slot_changed:[[BR]]
A bool indicating whether the producer slot was changed.
[[BR]]old_consumer_slot:[[BR]]
The old slot for consuming audio data. Only required if consumer_slot_changed is {{{True}}}.
[[BR]]new_consumer_slot:[[BR]]
The new slot for consuming audio data. Only required if consumer_slot_changed is {{{True}}}.
[[BR]]old_producer_slot:[[BR]]
The old slot for producing audio data. Only required if producer_slot_changed is {{{True}}}.
[[BR]]new_producer_slot:[[BR]]
The new slot for producing audio data. Only required if producer_slot_changed is {{{True}}}.=== AudioDevice ===
The AudioDevice represents the physical audio device which is part of a {{{AudioMixer}}}, implementing the {{{IAudioPort}}} interface. As such, it can be uniquely identified by the mixer it represents.
==== methods ====
'''!__init!__'''(''self'', '''mixer''', '''input_muted'''={{{False}}}, '''output_muted'''={{{False}}}):
Instantiates a new AudioDevice which represents the physical device associated with the specified {{{AudioMixer}}}.
[[BR]]mixer:[[BR]]
The {{{AudioMixer}}} whose physical device this object represents.
[[BR]]input_muted:[[BR]]
A boolean which indicates whether this object should act as a producer of audio data.
[[BR]]output_muted:[[BR]]
A boolean which indicates whether this object should act as a consumer of audio data.==== attributes ====
'''input_muted'''::
A writable property which controls whether this object should act as a producer of audio data. An {{{AudioPortDidChange}}} slots notification is sent when this attribute is changed to force connections to be reconsidered within the {{{AudioBridges}}} this object is part of.'''output_muted'''::
A writable property which controls whether this object should act as a consumer of audio data. An {{{AudioPortDidChange}}} slots notification is sent when this attribute is changed to force connections to be reconsidered within the {{{AudioBridges}}} this object is part of.=== AudioBridge ===
The {{{AudioBridge}}} is the basic component which is able to connect {{{IAudioPort}}} implementations. It acts as a container which connects as the producers to all the consumers which are part of it. An object which is both a producer and a consumer of audio data will not be connected to itself. Being an implementation of {{{IAudioPort}}} itself, an {{{AudioBridge}}} can be part of another {{{AudioBridge}}}. The {{{AudioBridge}}} does not keep strong references to the ports it contains and once the port's reference count reaches 0, it is automatically removed from the {{{AudioBridge}}}.
Note: although this is not enforced, there should never be any cycles when connecting {{{AudioBridges}}}.
==== methods ====
'''!__init!__'''(''self'', '''mixer''')::
Instantiate a new {{{AudioBridge}}} which uses the specified {{{AudioMixer}}} for mixing.'''add'''(''self'', '''port''')::
Add an implementation of {{{IAudioPort}}} to this AudioBridge. This will connect the new port to all the existing ports of the bridge. A port cannot be added more than once to an {{{AudioBridge}}}; thus, this object acts like a set.'''remove'''(''self'', '''port''')::
Remove a port from this {{{AudioBridge}}}. The port must have previously been added to the {{{AudioBridge}}}, otherwise a {{{ValueError}}} is raised.=== WavePlayer ===
A {{{WavePlayer}}} is an implementation of {{{IAudioPort}}} which is capable of producing audio data read from a {{{.wav}}} file. This object is completely reusable, as it can be started and stopped any number of times.
==== methods ====
'''!__init!__'''(''self'', '''mixer''', '''filename''', '''volume'''={{{100}}}, '''loop_count'''={{{1}}}, '''pause_time'''={{{0}}}, '''initial_play'''={{{True}}})::
Instantiate a new {{{WavePlayer}}} which is capable of playing a {{{.wav}}} file repeatedly. All the parameters are available as attributes of the object, but should not be changed once the object has been started.
[[BR]]mixer:[[BR]]
The {{{AudioMixer}}} this object is connected to.
[[BR]]filename:[[BR]]
The full path to the {{{.wav}}} file from which audio data is to be read.
[[BR]]volume:[[BR]]
The volume at which the file should be played.
[[BR]]loop_count:[[BR]]
The number of times the file should be played, or {{{0}}} for infinity.
[[BR]]pause_time:[[BR]]
How many seconds to wait between successive plays of the file.
[[BR]]initial_play:[[BR]]
Whether or not the file to play once the {{{WavePlayer}}} is started, or to wait {{{pause_time}}} seconds before the first play.'''start'''(''self'')::
Start playing the {{{.wav}}} file.'''stop'''(''self'')::
Stop playing the {{{.wav}}} file immediately.'''play'''(''self'')::
Play the {{{.wav}}} file. This method is an alternative to the start/stop methods, it runs on a waitable green thread. One may call {{{play().wait()}}} in order to green-block waiting for the file playback to end.==== attributes ====
'''is_active'''::
A boolean indicating whether or not this {{{WavePlayer}}} is currently playing.==== notifications ====
'''WavePlayerDidStart'''::
This notification is sent when the {{{WavePlayer}}} starts playing the file the first time after the {{{start()}}} method has been called.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''WavePlayerDidEnd'''::
This notification is sent when the {{{WavePlayer}}} is done playing either as a result of playing the number of times it was told to, or because the {{{stop()}}} method has been called.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''WavePlayerDidFail'''::
This notification is sent when the {{{WavePlayer}}} is not capable of playing the {{{.wav}}} file.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
[[BR]]error:[[BR]]
The exception raised by the {{{WaveFile}}} which identifies the cause for not being able to play the {{{.wav}}} file.=== WaveRecorder ===
A {{{WaveRecorder}}} is an implementation of {{{IAudioPort}}} is is capable of consuming audio data and writing it to a {{{.wav}}} file. Just like {{{WavePlayer}}}, this object is reusable: once stopped it can be started again, but if the filename attribute is not changed, the previously written file will be overwritten.
==== methods ====
'''!__init!__'''(''self'', '''mixer''', '''filename''')::
Instantiate a new {{{WaveRecorder}}}.
[[BR]]mixer:[[BR]]
The {{{AudioMixer}}} this {{{WaveRecorder}}} is connected to.
[[BR]]filename:[[BR]]
The full path to the {{{.wav}}} file where this object should write the audio data. The file must be writable. The directories up to the file will be created if possible when the {{{start()}}} method is called.'''start'''(''self'')::
Start consuming audio data and writing it to the {{{.wav}}} file. If this object is not part of an {{{AudioBridge}}}, not audio data will be written.'''stop'''(''self'')::
Stop consuming audio data and close the {{{.wav}}} file.==== attributes ====
'''is_active'''::
A boolean indicating whether or not this {{{WaveRecorder}}} is currently recording audio data.Conference support is implemented in the {{{sipsimple.conference}}} module. Currently, only audio conferencing is supported.
=== AudioConference ===
This class contains the basic implementation for audio conferencing. It acts as a container for {{{AudioStream}}} objects which it will connect in a full mesh, such that all participants can hear all other participants.
==== methods ====
'''!__init!__'''(''self'')::
Instantiates a new {{{AudioConference}}} which is ready to contain {{{AudioStream}}} objects.'''add'''(''self'', '''stream''')::
Add the specified {{{AudioStream}}} object to the conference.'''remove'''(''self'', '''stream''')::
Removes the specified {{{AudioStream}}} object from the conference. Raises a {{{ValueError}}} if the stream is not part of the conference.'''hold'''(''self'')::
Puts the conference "on hold". This means that the audio device will be disconnected from the conference: all the participants will be able to continue the conference, but the local party will no longer contribute any audio data and will not receive any audio data using the input and output devices respectively. This does not affect the hold state of the streams in any way.'''unhold'''(''self'')::
Removes the conference "from hold". This means that the audio device will be reconnected to the conference: all the participants will start to hear the local party and the local party will start to hear all the participants. This does not affect the hold state of the streams in any way.==== attributes ====
'''bridge'''::
An {{{AudioBridge}}} which this conference uses to connect all audio streams. It can be used by the application to play a wav file using a {{{WavePlayer}}} to all the participants or record the whole conference using a {{{WaveRecorder}}}.'''on_hold'''::
A boolean indicating whether or not the conference is "on hold".'''streams'''::
The list of streams which are part of this conference. The application must not manipulate this list in any way.The {{{sipsimple.xcap}}} module offers a high level API for managing XCAP resources to other parts of the middleware or to the applications built on top of the middleware. The XCAP resources
which can be managed by means of this module are:
* '''contact list''', by means of the {{{resource-lists}}} and {{{rls-services}}} XCAP applications
* '''presence policies''', by means of the {{{org.openmobilealliance.pres-rules}}} or {{{pres-rules}}} XCAP applications
* '''dialoginfo policies''', by means of the {{{org.openxcap.dialog-rules}}} XCAP application
* '''status icon''', by means of the {{{org.openmobilealliance.pres-content}}} XCAP application
* '''offline status''', by means of the {{{pidf-manipulation}}} XCAP application
The module can work with both OMA or IETF-compliant XCAP servers, preferring the OMA variants of the specification if the server supports them. Not all applications need to be available on the
XCAP server, although it is obvious that only those that are will be managed. The central entity for XCAP resource management is the XCAPManager, whose API relies on a series of objects describing
the resources stored on the XCAP server.
=== Contact ===
Implemented in [browser:sipsimple/xcap/__init__.py]
A {{{Contact}}} is a URI with additional information stored about it, central to the XCAP contact list management. Information about a contact is stored in the {{{resource-lists}}}, {{{rls-services}}},
{{{org.openmobilealliance.pres-rules}}} or {{{pres-rules}}}, and {{{org.openxcap.dialog-rules}}} applications. The URI associated with the contact is considered a unique identifier. Information
found in various places about the same URI is aggregated into a single {{{Contact}}} instance. More information about the contact is described within the attributes section.
==== attributes ====
'''name'''::
A human-readable name which can be associated with the contact. This is stored using the {{{display-name}}} standard {{{resource-lists}}} element.'''uri'''::
The uniquely identifying URI.'''group'''::
A human-readable group name which can be used to group contacts together. If this is not {{{None}}}, the contact will be reachable from the {{{oma_buddylist}}} list within the {{{resource-lists}}}
document, as defined by OMA. The group of a contact is the first {{{display-name}}} of an ancestor list which contains the contact information.'''subscribe_to_presence'''::
A boolean flag which indicates whether a subscription to the {{{presence}}} event is desired. If this is {{{True}}}, the contact's URI is referenced from a {{{rls-services}}} service which defines
{{{presence}}} as one of the packages. Thus, a contact with this flag set is guaranteed to be referenced by an RLS service.'''subscribe_to_dialoginfo'''::
A boolean flag which indicates whether a subscription to the {{{dialog}}} event is desired. If this is {{{True}}}, the contact's URI is referenced from a {{{rls-services}}} service which defines
{{{dialog}}} as one of the packages. Thus, a contact with this flag set is guaranteed to be refereneced by an RLS service.'''presence_policies'''::
Either {{{None}}} or a list of {{{PresencePolicy}}} objects which represent {{{org.openmobilealliance.pres-rules}}} or {{{pres-rules}}} rules which reference this contact's URI either directly
(through an identity condition) or indirectly through resource lists (using the OMA external-list common policy extension).'''dialoginfo_policies'''::
Either {{{None}}} or a list of {{{DialoginfoPolicy}}} objects which represent {{{org.openxcap.dialog-rules}}} rules which reference this contact's URI through an identity condition.'''attributes'''::
A dictionary containing additional name, value pairs which the middleware or the application can use to store any information regarding this contact. This is stored through a proprietary AG-Projects
extension to resource-lists.==== methods ====
'''!__init!__'''(''self'', '''name''', '''uri''', '''group''', '''**attributes''')::
Initializes a new {{{Contact}}} instance. The policies are by default set to {{{None}}} and the {{{subscribe_to_presence}}} and {{{subscribe_to_dialoginfo}}} flags to {{{True}}}.=== Service ===
Implemented in [browser:sipsimple/xcap/__init__.py]
A {{{Service}}} represents a URI managed by a Resource List Server (RLS). Subscriptions to this URI will be handled by the RLS.
==== attributes ====
'''uri'''::
The URI which can be used to access a service provided by the RLS.'''packages'''::
A list of strings containing the SIP events which can be subscribed for to the URI.'''entries'''::
A list of URIs which represent the expanded list of URIs referenced by the service. A subscription to the service's URI for one of packages will result in the RLS subscribing to these URIs.==== methods ====
'''!__init!__'''(''self'', '''uri''', '''packages''', '''entries'''={{{None}}})::
Initializes a new {{{Service}}} instance.=== Policy ===
Implemented in [browser:sipsimple/xcap/__init__.py]
{{{Policy}}} is the base class for {{{PresencePolicy}}} and {{{DialoginfoPolicy}}}. It describes the attributes common to both.
==== attributes ====
'''id'''::
A string containing the unique identifier of this specific policy. While it should not be considered human readable, OMA does assign specific meanings to some IDs.'''action'''::
A string having one of the values {{{"allow"}}}, {{{"confirm"}}}, {{{"polite-block"}}} or {{{"block"}}}.'''validity'''::
Either {{{None}}}, or a list of {{{datetime}}} instance 2-tuples representing the intervals when this policy applies. Example valid validity list which represents two intervals, each of two hours:
{{{
from datetime import datetime, timedelta
now = datetime.now()
one_hour = timedelta(seconds=3600)
one_day = timedelta(days=1)
validity = [(now-one_hour, now+one_hour), (now+one_day-one_hour, now+one_day+one_hour)]
}}}'''sphere'''::
Either {{{None}}} or a string representing the sphere of presentity when this policy applies.'''multi_identity_conditions'''::
Either {{{None}}} or a list of {{{CatchAllCondition}}} or {{{DomainCondition}}} objects as defined below. This is used to apply this policy to multiple users.==== methods ====
'''!__init!__'''(''self'', '''id''', '''action''', '''name'''={{{None}}}, '''validity'''={{{None}}}, '''sphere'''={{{None}}}, '''multi_identity_conditions'''={{{None}}})::
Initializes a new {{{Policy}}} instance.'''check_validity'''(''self'', '''timestamp''', '''sphere'''={{{Any}}})::
Returns a boolean indicating whether this policy applies at the specific moment given by timestamp (which must be a {{{datetime}}} instance) in the context of the specific sphere.=== CatchAllCondition ===
Implemented in [browser:sipsimple/xcap/__init__.py]
{{{CatchAllCondition}}} represents a condition which matches any user, but which can have some exceptions.
==== attributes ====
'''exceptions'''::
A list containing {{{DomainException}}} or {{{UserException}}} objects to define when this condition does not apply.==== methods ====
'''!__init!__'''(''self'', '''exceptions'''={{{None}}})::
Initializes a new {{{CatchAllCondition}}} instance.=== DomainCondition ===
Implemented in [browser:sipsimple/xcap/__init__.py]
{{{DomainCondition}}} represents a condition which matches any user within a specified domain, but which can have some exceptions.
==== attributes ====
'''domain'''::
A string containing the domain for which this condition applies.'''exceptions'''::
A list containing {{{UserEception}}} objects to define when this condition does not apply.==== methods ====
'''!__init!__'''(''self'', '''domain''', '''exceptions'''={{{None}}})::
Initializes a new {{{DomainCondition}}} instance.=== DomainException ===
Implemented in [browser:sipsimple/xcap/__init__.py]
{{{DomainException}}} is used as an exception for a {{{CatchAllCondition}}} which excludes all users within a specified domain.
==== attributes ====
'''domain'''::
A string containing the domain which is to be excluded from the {{{CatchAllCondition}}} containing this object as an exception.==== methods ====
'''!__init!__'''(''self'', '''domain''')::
Initializes a new {{{DomainException}}} instance.=== UserException ===
Implemented in [browser:sipsimple/xcap/__init__.py]
{{{UserException}}} is used as an exception for either a {{{CatchAllCondition}}} or a {{{DomainCondition}}} and excludes a user identified by an URI.
==== attributes ====
'''uri'''::
A string containing the URI which is to be excluded from the {{{CatchAllCondition}}} or {{{DomainCondition}}} containing this object as an exception.==== methods ====
'''!__init!__'''(''self'', '''uri''')::
Initializes a new {{{UserException}}} instance.=== PresencePolicy ===
Implemented in [browser:sipsimple/xcap/__init__.py]
A {{{PresencePolicy}}} represents either a {{{org.openmobilealliance.pres-rules}}} or {{{pres-rules}}} rule. It subclasses {{{Policy}}} and inherits its attributes, but defines additional
attributes corresponding to the transformations which can be specified in a rule.
==== attributes ====
All of the following attributes only make sense for a policy having a {{{"allow"}}} action.'''provide_devices'''::
Either {{{sipsimple.util.All}}}, or a list of {{{Class}}}, {{{OccurenceID}}} or {{{DeviceID}}} objects as defined below.'''provide_persons'''::
Either {{{sipsimple.util.All}}}, or a list of {{{Class}}} or {{{OccurenceID}}} objects as defined below.'''provide_services'''::
Either {{{sipsimple.util.All}}}, or a list of {{{Class}}}, {{{OccurenceID}}}, {{{ServiceURI}}} or {{{ServiceURIScheme}}} objects as defined below.'''provide_activities'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_class'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_device_id'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_mood'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_place_is'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_place_type'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_privacy'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_relationship'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_status_icon'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_sphere'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_time_offset'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.'''provide_user_input'''::
Either {{{None}}} (if the transformation is not be specified) or one of the strings {{{"false"}}}, {{{"bare"}}}, {{{"thresholds"}}}, {{{"full"}}}.'''provide_unknown_attributes'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean. The name of the attribute is not a typo, although it maps to the transformation named {{{provide-unknown-attribute}}} (singular form).'''provide_all_attributes'''::
Either {{{None}}} (if the transformation is not be specified) or a boolean.==== methods ====
'''!__init!__'''(''self'', '''id''', '''action''', '''name'''={{{None}}}, '''validity'''={{{None}}}, '''sphere'''={{{None}}}, '''multi_identity_conditions'''={{{None}}})::
Initializes a new {{{PresencePolicy}}} instance. The {{{provide_devices}}}, {{{provide_persons}}} and {{{provide_services}}} are initialized to {{{sipsimple.util.All}}}, {{{provide_all_attributes}}} to {{{True}}} and the rest to {{{None}}}.=== DialoginfoPolicy ===
Implemented in [browser:sipsimple/xcap/__init__.py]
A {{{DialoginfoPolicy}}} represents a {{{org.openxcap.dialog-rules}}} rule. It subclasses {{{Policy}}} and inherits all of its attributes. It does not add any other attributes or methods and thus
has an identical API.
=== Icon ===
Implemented in [browser:sipsimple/xcap/__init__.py]
An {{{Icon}}} instance represents a status icon stored using the {{{org.openmobilealliance.pres-content}}} application.
==== attributes ====
'''data'''::
The binary data of the image, as a string.'''mime_type'''::
The MIME type of the image, one of {{{image/jpeg}}}, {{{image/gif}}} or {{{image/png}}}.'''description'''::
An optional description of the icon.'''location'''::
An HTTP(S) URI which can be used by other users to download the status icon of the local user. If the XCAP server returns the proprietary X-AGP-Alternative-Location header in its GET and PUT
responses, that is used otherwise the XCAP URI of the icon is used.==== methods ====
'''!__init!__'''(''self'', '''data''', '''mime_type''', '''description'''={{{None}}}, '''location'''={{{None}}})::
Initializes a new {{{Icon}}} instance.=== OfflineStatus ===
Implemented in [browser:sipsimple/xcap/__init__.py]
An {{{OfflineStatus}}} instance represents data stored using the {{{pidf-manipulation}}} application.
==== attributes ====
'''activity'''::
A string representing an activity within a {{{person}}} element.'''note'''::
A string stored as a note within a {{{person}}} element.==== methods ====
'''!__init!__'''(''self'', '''activity'''={{{None}}}, '''note'''={{{Note}}})::
Initializes a new {{{OfflineStatus}}} instance.=== XCAPManager ===
Implemented in [browser:sipsimple/xcap/__init__.py]
The XCAPManager is the central entity used to manage resource via the XCAP protocol. It is a {{{Singleton}}} per account and has state machine as described in the following diagram:
Image(xcap-manager-state.png, align=center)
The XCAPManager associated with an account can be obtained by instantiating it with the account passed as an argument. The {{{load}}} method needs to be called just once in order to specify the
directory which is used by manager to store its cache and other internal data. Once this is done, the {{{start}}} and {{{stop}}} methods can be called as needed. Initially in the {{{stopped}}} state,
the start method will result in a transition to the {{{initializing}}} state. While in the {{{initializing}}} state, the XCAP manager will try to connect to the XCAP server and retrieve the
capabilities ({{{xcap-caps}}} application). It will then initiate a SUBSCRIBE for the {{{xcap-diff}}} event (if configured) and transition to the {{{fetching}}} state. In the {{{fetching}}} state, it
will try retrieve all the documents from the XCAP server, also specifying the ETag of the last known version. If none of the documents changed and this is not the first fetch, it transitions to the
{{{insync}}} state. Otherwise, it inserts a {{{normalize}}} operation at the beginning of the journal (described below) and transitions to the {{{updating}}} state. In the {{{updating}}} state, it
applies the operations from the journal which were not applied yet on the currently known documents and tries to push the documents, specifying the Etag of the last known version. If an operation
fails due to a document having been modified, it marks all the operations in the journal as not being applied and transitions to the {{{fetching}}} state; if any other error occurs, the update is
retried periodically. If the update succeeds, data is extracted from the documents and the {{{XCAPManagerDidReloadData}}} notification is sent. The XCAPManager then transitions to the {{{insync}}}
state. A call to the {{{stop}}} method will result in a transition to the {{{stopping}}} state, termination of any existing SUBSCRIBE dialog and a transition to the {{{stopped}}} state.
Modifications to the settings which control the XCAPManager can result in either a transition to the {{{initializing}}} state or the termination of any previous SUBSCRIBE dialog and creation of a new
one.
The subscription to the {{{xcap-diff}}} event allows the XCAPManager to be notified when the documents it manages are modified remotely. If the subscription fails, a fetch of all the documents is
tried and the subscription is retried in some time. This allows the XCAPManager to reload the documents when they are modified remotely even if {{{xcap-diff}}} event is not supported by the provider. If subscription for {{{xcap-diff}}} event fails, a fetch of all the documents will be tried every 2 minutes.
The XCAPManager keeps the documents as they are stored on the XCAP server along with their ETags in an on-disk cache. All operations are made using the conditional {{{If-Match}}} and
{{{If-None-Match}}} headers such that remote modifications the XCAPManager does not know about are not overwritten and bandwidth and processing power are not wasted by GET operations when a document
is not modified.
Operations which the XCAPManager can be asked to apply to modify the documents are kept in a journal. This journal is saved to disk, such that operations which cannot be applied when requested due
to server problems or lack of connectivity are retried even after application restarts. In addition, the high-level defined operations and the journal allow the modifications to be applied even if the
document stored on the XCAP server are modified. Put differently, operations do depend on a specific version of the documents and the XCAPManager will try to apply them irrespective of the format
of the document.
==== configuration ====
'''Account.id''', '''Account.auth.username''', '''Account.auth.password'''::
These are used both for the {{{xcap-diff}}} subscription and the XCAP server connection.'''Account.sip.subscribe_interval'''::
This controls the Expires header used for the subscription, although a 423 response from the server can result in a larger Expires value being used.'''Account.xcap.xcap_root'''::
This specifies the XCAP root used for contacting the XCAP server and managing the resources. If this setting is {{{None}}}, a TXT DNS query is made for the {{{xcap}}} subdomain of the SIP account's
domain. The result is interpreted as being an XCAP root. Example record for account alice@example.org:
{{{
xcap.example.org. IN TXT "https://xcap.example.org/xcap-root"
}}}'''SIPSimpleSettings.sip.transport_list'''::
This controls the transports which can be used for the subscription.==== methods ====
'''!__init!__'''(''self'', '''account''')::
Initializes an XCAPManager for the specified account.'''load'''(''self'')::
Allows the XCAPManager to the load its internal data from cache.'''start'''(''self'')::
Starts the XCAPManager. This will result in the subscription being started, the XCAP server being contacted and any operations in the journal being applied. This method must be called in a green
thread.'''stop'''(''self'')::
Stops the XCAPManager from performing any tasks. Waits until the {{{xcap-diff}}} subscription, if any, is terminated. This method must be called in a green thread.'''start_transaction'''(''self'')::
This allows multiple operations to be queued and not applied immediately. All operations queued after a call to this method will not be applied until the {{{commit_transaction}}} method is called.
This does not have the same meaning as a relational database transaction, since there is no {{{rollback}}} operation.'''commit_transaction'''(''self'')::
Applies the modifications queued after a call to {{{start_transaction}}}. This method needs to be called the exact same number of times the {{{start_transaction}}} method was called. Does not have
any effect if {{{start_transaction}}} was not previously called.The following methods results in XCAP operations being queued on the journal:'''add_group'''(''self'', '''group''')::
Add a contact group with the specified name.'''rename_group'''(''self'', '''old_name''', '''new_name''')::
Change the name of the contact group {{{old_name}}} to {{{new_name}}}. If such a contact group does not exist, the operation does not do anything.'''remove_group'''(''self'', '''group''')::
Remove the contact group (and any contacts contained in it) with the specified name. If such a contact group does not exist, the operation does not do anything.'''add_contact'''(''self'', '''contact''')::
Adds a new contact, described by a {{{Contact}}} object. If the contact with the same URI and a not-{{{None}}} group already exists, the operation does not do anything. Otherwise, the contact
is added and any reference to the contact's URI is overwritten. Requests to add a contact to some OMA reserved presence policies ({{{wp_prs_unlisted}}}, {{{wp_prs_allow_unlisted}}},
{{{wp_prs_block_anonymous}}}, {{{wp_prs_allow_own}}}) is ignored.'''update_contact'''(''self'', '''contact''', '''**attributes''')::
Modifies a contact's properties. The keywords can be any of the {{{Contact}}} attributes, with the same meaning. The URI of the contact to be modified is taken from the first argument. If such
a URI does not exist, it is added. Requests to add a contact to some OMA reserved presence policies ({{{wp_prs_unlisted}}}, {{{wp_prs_allow_unlisted}}}, {{{wp_prs_block_anonymous}}},
{{{wp_prs_allow_own}}}) is ignored. The URI of a contact can be changed by specified the keyword argument {{{uri}}} with the new value.'''remove_contact'''(''self'', '''contact''')::
Removes any reference to the contact's URI from all documents. This also means that the operation will make sure there are no policies which match the contact's URI.'''add_presence_policy'''(''self'', '''policy''')::
Adds a new presence policy, described by a {{{PresencePolicy}}} object. If the id is specified and a policy with the same id exists, the operation does not do anything. Otherwise, if the id is not
specified, one will be automatically generated (recommended). If the id is specified, but it is incompatible with the description of the policy (for example if an OMA defined id is used and there
are some multi_identity_conditions), a new one will be automatically generated.'''update_presence_policy'''(''self'', '''policy''', '''**attributes''')::
Modifies a presence policy's properties. The keywords can be any of the {{{PresencePolicy}}} attributes, with the same meaning. The id of the policy to be modified is taken from the first argument.
If such a policy does not exist and there is sufficient information about the policy, it is added. If the policy to be modified uses the OMA extension to reference resource-lists and
multi_identity_conditions are specified in the keywords, a new policy whose properties are the combination of the existing policy and the keywords is created.'''remove_presence_policy'''(''self'', '''policy''')::
Removes the presence policy identified by the id attribute of the {{{PresencePolicy}}} object specified. If the id is {{{None}}} or does not exist in the document, the operation does not do
anything. Some standard OMA policies ({{{wp_prs_unlisted}}}, {{{wp_prs_allow_unlisted}}}, {{{wp_prs_block_anonymous}}}, {{{wp_prs_allow_own}}}, {{{wp_prs_grantedcontacts}}},
{{{wp_prs_blockedcontacts}}}) cannot be removed.'''add_dialoginfo_policy'''(''self'', '''policy''')::
Adds a new dialoginfo policy, described by a {{{DialoginfoPolicy}}} object. If the id is specified and a policy with the same id exists, the operation does not do anything. Otherwise, if the id is
not specified, one will be automatically generated (recommended).'''update_dialoginfo_policy'''(''self'', '''policy''', '''**attributes''')::
Modifies a dialoginfo policy's properties. The keywords can be any of the {{{DialoginfoPolicy}}} attributes, with the same meanining. The id of the policy to be modified is taken from the first
argument. If such a policy does not exist and there is sufficient information about the policy, it is added.'''remove_dialoginfo_policy'''(''self'', '''policy''')::
Removes the dialoginfo policy identified by the id attribute of the {{{DialoginfoPolicy}}} object specified. If the id is {{{None}}} or does not exist in the document, the operation does not do
anything.'''set_status_icon'''(''self'', '''icon''')::
Sets the status icon using the information from the {{{Icon}}} object specified. The {{{location}}} attribute is ignored. The MIME type must be one of {{{image/gif}}}, {{{image/png}}} or
{{{image/jpeg}}}. If the argument is {{{None}}}, the status icon is deleted.'''set_offline_status'''(''self'', '''status''')::
Sets the offline status using the information from the {{{OfflineStatus}}} object specified. If the argument is {{{None}}}, the offline status document is deleted.==== notifications ====
'''XCAPManagerWillStart'''::
This notification is sent just after calling the {{{start}}} method.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''XCAPManagerDidStart'''::
This notification is sent after the XCAPManager has started doing its tasks (contacting the XCAP server, subscribing to {{{xcap-diff}}} event). This notification does not mean that
any of these operations were successful, as the XCAPManager will retry them continuously should they fail.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''XCAPManagerWillEnd'''::
This notification is sent just after calling the {{{stop}}} method.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''XCAPManagerDidEnd'''::
This notification is sent when the XCAPManager has stopped performing any tasks. This also means that any active {{{xcap-diff}}} subscription has been terminated.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''XCAPManagerDidDiscoverServerCapabilities'''::
This notification is sent when the XCAPManager contacts an XCAP server for the first time or after the connection is reset due to configuration changes. The data of the notification contains
information about the server's capabilities (obtained using the {{{xcap-caps}}} application).
[[BR]]contactlist_supported:[[BR]]
A boolean indicating the support of documents needed for contact management ({{{resource-lists}}} and {{{rls-services}}}).
[[BR]]presence_policies_supported:[[BR]]
A boolean indicating the support of documents needed for presence policy management ({{{org.openmobilealliance.pres-rules}}} or {{{pres-rules}}}).
[[BR]]dialoginfo_policies_supported:[[BR]]
A boolean indicating the support of documents needed for dialoginfo policy management ({{{org.openxcap.dialog-rules}}}).
[[BR]]status_icon_supported:[[BR]]
A boolean indicating the support of documents needed for status icon management ({{{org.openmobilealliance.pres-content}}}).
[[BR]]offline_status_supported:[[BR]]
A boolean indicating the support of documents needed for offline status management ({{{pidf-manipulation}}}).
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''XCAPManagerDidReloadData'''::
This notification is sent when the XCAPManager synchronizes with the XCAP server. The data of the notification contains objects representing the data as it is stored on the XCAP server.
[[BR]]contacts:[[BR]]
A list of {{{Contact}}} objects.
[[BR]]groups:[[BR]]
A list of strings.
[[BR]]services:[[BR]]
A list of {{{Service}}} objects.
[[BR]]presence_policies:[[BR]]
A list of {{{PresencePolicy}}} objects.
[[BR]]dialoginfo_policies:[[BR]]
A list of {{{DialoginfoPolicy}}} objects.
[[BR]]status_icon:[[BR]]
A {{{StatusIcon}}} object if one is stored, {{{None}}} otherwise.
[[BR]]offline_status:[[BR]]
A {{{OfflineStatus}}} object if offline status information is stored, {{{None}}} otherwise.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.'''XCAPManagerDidChangeState'''::
This notification is sent when the XCAPManager transitions from one state to another.
[[BR]]prev_state:[[BR]]
The old state of the XCAPManager, a string.
[[BR]]state:[[BR]]
The new state of the XCAPManager, a string.
[[BR]]timestamp:[[BR]]
A {{{datetime.datetime}}} object indicating when the notification was sent.
