Difference between revisions of "Architecture Overview"
Jump to navigation
Jump to search
m (replace image links to the old SVN repo with links to the Git repo) |
|||
(9 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | + | ReSIProcate's core transaction processing architecture uses a SIP message-based interface between the Transaction (and lower) layers and the Transaction User layers. The [[DUM Overview|Dialog Usage Manager]], which was created to simplify the creation of an user agent, is one example of a Transaction User. | |
− | DUM is one example of a Transaction User. | ||
− | + | The following diagram (PNG file [https://github.com/resiprocate/resiprocate/blob/master/resip/stack/doc/ResipArchitecture.png]) shows the ReSIProcate transaction and transport architecture. Common colors indicate related, thread-connected components. This diagram is also available as PDF [https://github.com/resiprocate/resiprocate/blob/master/resip/stack/doc/ResipArchitecture.pdf] and graffle source [https://github.com/resiprocate/resiprocate/blob/master/resip/stack/doc/ResipArchitecture.graffle]. The diagram was created with OmniGraffle Pro 3.0 [http://www.omnigroup.com/applications/omnigraffle/] and updated at the 2005Q2 ReSIProcate documentation session. | |
− | [[ |
Latest revision as of 11:28, 20 November 2016
ReSIProcate's core transaction processing architecture uses a SIP message-based interface between the Transaction (and lower) layers and the Transaction User layers. The Dialog Usage Manager, which was created to simplify the creation of an user agent, is one example of a Transaction User.
The following diagram (PNG file [1]) shows the ReSIProcate transaction and transport architecture. Common colors indicate related, thread-connected components. This diagram is also available as PDF [2] and graffle source [3]. The diagram was created with OmniGraffle Pro 3.0 [4] and updated at the 2005Q2 ReSIProcate documentation session.