SIP SIMPLE Client SDK

= MSRP API =

[[TOC(WikiStart, Sip*, depth=3)]]

Message Session Relay Protocol (MSRP) is a protocol for transmitting a series of related instant messages in the context of a session. Message sessions are treated like any other media stream when set up via a rendezvous or session creation protocol such as the Session Initiation Protocol (SIP). 

 * MSRP sessions are defined in [http://tools.ietf.org/html/rfc4975 RFC 4975].

 * MSRP relay extension used for NAT traversal of instant messaging and file transfer sessions is defined in [http://tools.ietf.org/html/rfc4976 RFC 4976].

The MSRP protocol is implemented by [http://devel.ag-projects.com/cgi-bin/darcsweb.cgi?r=python-msrplib;a=summary msrplib] Python package. On top of it, {{{sipsimple}}} provides higher level classes integrated into middleware notification and configuration systems:

 * {{{sipsimple.msrp.MSRPChat}}}

 * {{{sipsimple.msrp.MSRPFileTransfer}}}

 * {{{sipsimple.msrp.MSRPDesktopSharing}}}

These classes are used internally by [wiki:SipMiddlewareApi#Session Session], which provides the necessary methods to access their features. The notifications posted by these classes are also handled internally by [wiki:SipMiddlewareApi#Session Session]. The notifications that are relevant to the user are then reposted by the Session instance. Refer to [wiki:SipMiddlewareApi#Session Session documentation] for details on the Session API. To communicate with the middleware, MSRP high level classes use the notification system provided by the [http://pypi.python.org/pypi/python-application python-application] package.

== MSRPChat high level API ==

{{{sipsimple.msrp.MSRPChat}}} implements Instant Messaging over MSRP in the context of SIPSIMPLE middleware. This class

 * automatically wraps outgoing messages with Message/CPIM if that's necessary according to accept-types

 * unwraps incoming Message/CPIM messages; for each incoming message, {{{MSRPChatGotMessage}}} is posted.

 * plays notification sounds on received/sent message

=== methods ===

 '''!__init!__'''(''self'', ''account'', ''remote_uri'', ''outgoing'')::

 Initialize MSRPChat instance.

 '''initialize'''(''self'')::

 Initialize the MSRP connection; connect to the relay if necessary. When done, fire MSRPChatDidInitialize (with 'sdpmedia' attribute, containing the appropriate 'SDPMedia' instance)

 '''start'''(''self'', ''remote_media'')::

 Complete the MSRP connection establishment; this includes binding the MSRP session. [[BR]]

 When done, fire MSRPChatDidStart. At this point each incoming message is posted as a {{{MSRPChatGotMessage}}} notification

 '''end'''(''self'')::

 Close the MSRP connection or cleanup after initialize(), whatever is necessary. [[BR]]

 Before doing anything post {{{MSRPChatWillEnd}}}.

 When done, post {{{MSRPChatDidEnd}}}. If there was an error, post {{{MSRPChatDidFail}}}. 

 {{{MSRPChatDidEnd}}} will be posted anyway.

 '''send_message'''(''self'', ''content'', ''content_type''={{{'text/plain'}}}, ''to_uri''={{{None}}}, ''dt''={{{None}}})::

 Send IM message. Prefer Message/CPIM wrapper if it is supported. If called before the connection was established, the messages will be

 queued until MSRPChatDidStart notification.

 Return generated MSRP chunk (MSRPData instance); to get Message-ID use its 'message_id' attribute.

 ''content'' str:[[BR]]

 content of the message

 ''to_uri'' SIPURI:[[BR]]

 "To" header of CPIM wrapper; use to override the default supplied to {{{__init__}}}.

 May only differ from the one supplied in __init__ if the remote party supports private messages. If it does not, {{{MSRPChatError}}} will be raised;

 ''content_type'' str:[[BR]]

 Content-Type of wrapped message if Message/CPIM is used (Content-Type of MSRP message is always Message/CPIM in that case);

 otherwise, Content-Type of MSRP message.

 These MSRP headers are used to enable end-to-end success reports and to disable hop-to-hop successful responses:

{{{

Failure-Report: partial

Success-Report: yes

}}}

=== notifications ===

 * MSRPChatDidInitialize

 * MSRPChatDidStart

 * MSRPChatWillEnd

 * MSRPChatDidEnd

 * MSRPChatDidFail

 * MSRPChatGotMessage

  - cpim_headers (dict)

  - message  (MSRPData)

  - content (str) - the actual string that the remote user has typed

 * MSRPChatDidDeliverMessage

 * MSRPChatDidNotDeliverMessage

== MSRPFileTransfer ==

== MSRPDesktopSharing ==

----------------------

== msrplib low level API ==

{{{msrplib}}} is based upon [http://twistedmatrix.com twisted] and [http://devel.ag-projects.com/~denis/eventlet/ eventlet] and provides a set of

classes for establishing and managing MSRP connection.

The library consist of the following modules:

 '''msrplib.transport'''::

 Defines {{{MSRPTransport}}} class, which provides low level control over MSRP connection.

 '''msrplib.connect'''::

 Defines means to establish a connection, bind it, and provide an initialized {{{MSRPTransport}}} instance.

 '''msrplib.session'''::

 Defines {{{MSRPSession}}} class, which provides high level control over a MSRP connection.

 '''msrplib.protocol'''::

 Provides representation and parsing of MSRP entities - chunks and URIs.

 '''msrplib.trafficlog'''::

 Defines {{{Logger}}} class that is used through out the library to log the connection state.

=== Usage ===

==== Establish a connection ====

{{{msrplib.connect}}} provides a number of classes to establish a connection, so the first

thing to do is to select which one applies to your situation:

    1. Calling endpoint, not using a relay ({{{ConnectorDirect}}})

    2. Answering endpoint, not using a relay ({{{AcceptorDirect}}})

    3. Calling endpoint, using a relay ({{{ConnectorRelay}}})

    4. Answering endpoint, using a relay ({{{AcceptorRelay}}})

The answering endpoint may skip using the relay if sure that it's accessible

directly. The calling endpoint is unlikely to need the relay.

Once you have an instance of the right class (use the convenience functions

{{{get_connector()}}} and {{{get_acceptor()}}} to get one), the procedure to establish the

connection is the same:

{{{

full_local_path = connector.prepare()

try:

    ... put full_local_path in SDP 'a:path' attribute

    ... get full_remote_path from remote's 'a:path: attribute

    ... (the order of the above steps is reversed if you're the

    ... answering party, but that does not affect connector's usage)

    msrptransport = connector.complete(full_remote_path)

finally:

    connector.cleanup()

}}}

To customize connection's parameters, create a new {{{protocol.URI}}} object and pass

it to prepare() function, e.g.

{{{

local_uri = protocol.URI(use_tls=False, port=5000)

connector.prepare(local_uri)

}}}

{{{prepare()}}} may update {{{local_uri}}} in place with the actual connection parameters

used (e.g. if you specified port=0). 'port' attribute of {{{local_uri}}} is currently

only respected by {{{AcceptorDirect}}}.

Note that, acceptors and connectors are one-use only. Which means, that {{{AcceptorDirect}}}

will open a port just to handle one incoming connection and close it right after.

If your application behaves more like a server, i.e. opens a port and listens on it

constantly, use {{{MSRPServer}}} class.

=== Components ===

==== a connector or acceptor ====

 {{{msrplib.connect}}} provides 2 connectors (with and without relay) and 2 acceptors (likewise, with or without relay). All of them have the exact same interface,

 '''prepare'''(''self'', ''local_uri''={{{None}}})::

 Depending on type of the connector, use local_uri to prepare the MSRP connection, which means:

 * connecting and authenticating at the relay if a relay is used ({{{ConnectorRelay}}} and {{{AcceptorRelay}}})

 * start listening on a local port for DirectAcceptor

 ''local_uri'' is used to specify the connection parameters, e.g. local port and local ip.

 If not provided, suitable ''local_uri'' will be generated.

 ''local_uri'' maybe updated in place by {{{prepare()}}} method if the real settings used are different from those specified.

 {{{prepare}}} returns a full local path - list of {{{protocol.URI}}} instances, suitable to be put in SDP {{{'a:path'}}} attribute.

 '''complete'''(''self'', ''full_remote_path'')::

 Complete establishing the MSRP connection, which means

 * establishing the connection if it wasn't already established ({{{ConnectorDirect}}})

 * bind the connection, i.e. exchange empty chunk to verify each other's From-Path and To-Path

 ''full_remote_path'' should be a list of {{{protocol.URI}}} instances, obtained by parsing {{{'a:path'}}} put in SDP by the remote party.

 {{{complete}}} returns {{{transport.MSRPTransport}}} instance, ready to read and send chunks.

 '''cleanup'''(''self'')::

 Call this method to cleanup after {{{initialize()}}} if it's impossible to call {{{complete()}}}

==== transport.MSRPTransport ====

Low level access to MSRP connection.

===== attributes =====

===== methods =====

 '''make_chunk'''(''self'', ''transaction_id''={{{None}}}, ''method''={{{'SEND'}}}, ''code''={{{None}}}, ''comment''={{{None}}}, ''data''={{{''}}}, ''contflag''={{{None}}}, ''start''={{{1}}}, ''end''={{{None}}}, ''length''={{{None}}}, ''message_id''={{{None}}})::

 Make a new chunk ({{{protocol.MSRPData}}} instance) with proper {{{From-Path}}}, {{{To-Path}}}, {{{Byte-Range}}} and {{{Message-ID}}} headers set up based on MSRPTransport's state and the parameters provided. Use ''data'' for payload, and ''start''/''end''/''length'' to generate {{{Byte-Range}}} header. Generate new random strings for default values of ''transaction_id'' and ''message_id''. 

 [[BR]]''contflag'':[[BR]]

 MSRP chunk's continuation flag ({{{'$'}}}, {{{'+'}}} or {{{'#'}}}). Default is {{{'$'}}}, unless you have a partial {{{SEND}}} chunk, in which case it is {{{'+'}}}

==== session.MSRPSession ====

===== attributes =====

===== methods =====

==== connect.MSRPServer ====

 Manage listening sockets. Bind incoming requests.

 MSRPServer solves the problem with AcceptorDirect: concurrent using of 2

 or more AcceptorDirect instances on the same non-zero port is not possible.

 If you initialize() those instances, one after another, one will listen on

 the socket and another will get BindError.

 MSRPServer avoids the problem by sharing the listening socket between multiple connections.

 It has a slightly different interface from AcceptorDirect, so it cannot be considered a drop-in

 replacement.

 '''prepare'''(''self'', ''local_uri''={{{None}}}, ''logger''={{{None}}})::

 Start a listening port specified by ''local_uri'' if there isn't one on that port/interface already.

 Add ''local_uri'' to the list of expected URIs, so that incoming connections featuring this URI won't be rejected.

 If ''logger'' is provided use it for this connection instead of the default one.

 '''complete'''(''self'', ''full_remote_path'')::

 Wait until one of the incoming connections binds using provided ''full_remote_path''.

 Return connected and bound {{{MSRPTransport}}} instance.

 If no such binding was made within {{{MSRPBindSessionTimeout.seconds}}}, raise {{{MSRPBindSessionTimeout}}}.

 ''full_remote_path'' should be a list of {{{protocol.URI}}} instances, obtained by parsing {{{'a:path'}}} put in SDP by the remote party.

 '''cleanup'''(''self'', ''local_uri'')::

 Remove ''local_uri'' from the list of expected URIs.