Module: sip-router Branch: master Commit: 0c95e9cd63b7e121e9f27f5f16efa9bd78bf5aec URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=0c95e9cd...
Author: Daniel-Constantin Mierla miconda@gmail.com Committer: Daniel-Constantin Mierla miconda@gmail.com Date: Tue Jan 17 09:35:24 2012 +0100
msrp: docs extended with more details about usage
---
modules/msrp/README | 74 ++++++++++++++++++++++++++++++- modules/msrp/doc/msrp_admin.xml | 91 ++++++++++++++++++++++++++++++++++++++- 2 files changed, 161 insertions(+), 4 deletions(-)
diff --git a/modules/msrp/README b/modules/msrp/README index d04692b..817ebfb 100644 --- a/modules/msrp/README +++ b/modules/msrp/README @@ -83,7 +83,7 @@ Chapter 1. Admin Guide
1. Overview
- This module provides a MSRP routing engike, a.k.a. MSRP relay. MSRP + This module provides a MSRP routing engine, a.k.a. MSRP relay. MSRP (Message Session Relay Protocol) is defined by RFC4975, the extensions for a MSRP Relay being covered in RFC4976.
@@ -105,6 +105,13 @@ Chapter 1. Admin Guide authentication, authorization to database connectors, security and DoS attacks protections.
+ Kamailio can handle SIP and MSRP traffic received on the same port, the + appropriate configuration file block being executed based on the type + of message. Therefore you can use Kamailio as a stand-alone MSRP relay + or have an instance handling both SIP and MSRP. Another option is to + configure Kamailio to listen on multiple ports, some of them being used + for SIP and others for MSRP. + 2. Dependencies
2.1. Kamailio Modules @@ -288,7 +295,66 @@ event_route[msrp:frame-in] {
7. Usage
- Example routing block for MSRP frames. + When 'sipmsg' parameter is set to 1 (which is default), the module + builds internally a SIP request from the MSRP frame and gives it to the + config file interpreter, in this way all the functions that are valid + for SIP requests can be used safe in event_route[msrp:frame-in]. + + To build the SIP request, msrp module takes the first line and the + headers from a MSRP message and appends to a static buffer. Next two + examples show a MSRP frame and the resulted SIP request. +... +MSRP 6aef SEND +To-Path: msrps://a.example.org:9000/kjfjan;tcp \ + msrps://b.example.net:9000/aeiug;tcp \ + msrps://bob.example.net:8145/foo;tcp +From-Path: msrps://alice.example.org:7965/bar;tcp +Success-Report: yes +Byte-Range: 1-*/* +Message-ID: 87652 +Content-Type: text/plain + +Hi Bob, I'm about to send you a photo. +-------6aef$ +... +... +MSRP sip:a@127.0.0.1 SIP/2.0 +Via: SIP/2.0/UDP 127.0.0.1:9;branch=z9hG4bKa +From: b@127.0.0.1;tag=a +To: a@127.0.0.1 +Call-ID: a +CSeq: 1 MSRP +Content-Length: 0 +MSRP-First-Line: MSRP 6aef SEND +To-Path: msrps://a.example.org:9000/kjfjan;tcp \ + msrps://b.example.net:9000/aeiug;tcp \ + msrps://bob.example.net:8145/foo;tcp +From-Path: msrps://alice.example.org:7965/bar;tcp +Success-Report: yes +Byte-Range: 1-*/* +Message-ID: 87652 +Content-Type: text/plain + +... + + Note that MSRP does not permit line folding. A "" in the examples + shows a line continuation due to limitations in line length of this + document. Neither the backslash nor the extra CRLF is included in the + actual request or response. + + As it can be observed, the MSRP frame content starts with the body of + header 'MSRP-First-Line:'. Using a static content to get to a valid SIP + request is a perfect trade off for performances. + + Besides the option to access parts of MSRP frame via internally build + SIP message, msrp module exports a new pseudo-variable class $msrp(key) + which returns attributes from the MSRP frame. There is also a new + transformation, {msrpuri.key}, to get access to parts of a MSRP URI. + See the appropriate Wiki pages on the project's web site for full + details about new pseudo-variable and transformation classes. + + Next is an example of configuration file with the routing block for + MSRP frames. In this config, the SIP traffic is rejected.
Example 1.9. Event Route ... @@ -332,6 +398,10 @@ request_route { exit; }
+reply_route { + drop; +} + event_route[msrp:frame-in] { xdbg("============#[[$msrp(method)]]===========\n"); xdbg("============*[[$si:$sp]]\n"); diff --git a/modules/msrp/doc/msrp_admin.xml b/modules/msrp/doc/msrp_admin.xml index b10e1e3..1ac7039 100644 --- a/modules/msrp/doc/msrp_admin.xml +++ b/modules/msrp/doc/msrp_admin.xml @@ -16,7 +16,7 @@ <section> <title>Overview</title> <para> - This module provides a MSRP routing engike, a.k.a. MSRP relay. + This module provides a MSRP routing engine, a.k.a. MSRP relay. MSRP (Message Session Relay Protocol) is defined by RFC4975, the extensions for a MSRP Relay being covered in RFC4976. </para> @@ -41,6 +41,14 @@ authentication, authorization to database connectors, security and DoS attacks protections. </para> + <para> + &kamailio; can handle SIP and MSRP traffic received on the same port, + the appropriate configuration file block being executed based on the + type of message. Therefore you can use &kamailio; as a stand-alone + MSRP relay or have an instance handling both SIP and MSRP. Another + option is to configure &kamailio; to listen on multiple ports, some + of them being used for SIP and others for MSRP. + </para> </section>
<section> @@ -321,7 +329,82 @@ event_route[msrp:frame-in] { <section> <title>Usage</title> <para> - Example routing block for MSRP frames. + When 'sipmsg' parameter is set to 1 (which is default), the module + builds internally a SIP request from the MSRP frame and gives it to + the config file interpreter, in this way all the functions that are + valid for SIP requests can be used safe in + event_route[msrp:frame-in]. + </para> + <para> + To build the SIP request, msrp module takes the first line and the + headers from a MSRP message and appends to a static buffer. Next + two examples show a MSRP frame and the resulted SIP request. + </para> + <programlisting format="linespecific"> +<![CDATA[ +... +MSRP 6aef SEND +To-Path: msrps://a.example.org:9000/kjfjan;tcp \ + msrps://b.example.net:9000/aeiug;tcp \ + msrps://bob.example.net:8145/foo;tcp +From-Path: msrps://alice.example.org:7965/bar;tcp +Success-Report: yes +Byte-Range: 1-*/* +Message-ID: 87652 +Content-Type: text/plain + +Hi Bob, I'm about to send you a photo. +-------6aef$ +... +]]> +</programlisting> + + <programlisting format="linespecific"> +<![CDATA[ +... +MSRP sip:a@127.0.0.1 SIP/2.0 +Via: SIP/2.0/UDP 127.0.0.1:9;branch=z9hG4bKa +From: <b@127.0.0.1>;tag=a +To: <a@127.0.0.1> +Call-ID: a +CSeq: 1 MSRP +Content-Length: 0 +MSRP-First-Line: MSRP 6aef SEND +To-Path: msrps://a.example.org:9000/kjfjan;tcp \ + msrps://b.example.net:9000/aeiug;tcp \ + msrps://bob.example.net:8145/foo;tcp +From-Path: msrps://alice.example.org:7965/bar;tcp +Success-Report: yes +Byte-Range: 1-*/* +Message-ID: 87652 +Content-Type: text/plain + +... +]]> +</programlisting> + <para> + Note that MSRP does not permit line folding. A "" in the examples + shows a line continuation due to limitations in line length of this + document. Neither the backslash nor the extra CRLF is included in + the actual request or response. + </para> + <para> + As it can be observed, the MSRP frame content starts with the body + of header 'MSRP-First-Line:'. Using a static content to get to a + valid SIP request is a perfect trade off for performances. + </para> + <para> + Besides the option to access parts of MSRP frame via internally + build SIP message, msrp module exports a new pseudo-variable class + $msrp(key) which returns attributes from the MSRP frame. There is + also a new transformation, {msrpuri.key}, to get access to parts + of a MSRP URI. See the appropriate Wiki pages on the project's + web site for full details about new pseudo-variable and + transformation classes. + </para> + <para> + Next is an example of configuration file with the routing block + for MSRP frames. In this config, the SIP traffic is rejected. </para> <example> <title>Event Route</title> @@ -367,6 +450,10 @@ request_route { exit; }
+reply_route { + drop; +} + event_route[msrp:frame-in] { xdbg("============#[[$msrp(method)]]===========\n"); xdbg("============*[[$si:$sp]]\n");
-
Daniel-Constantin Mierla