Differences

This shows you the differences between two versions of the page.

--- kamailio:k43-async-sip-routing-nodejs [2015/09/07 12:21] – [Kamailio Config File] admin
+++ kamailio:k43-async-sip-routing-nodejs [2015/09/07 12:49] – [Node.js Application] admin
@@ Line 22: / Line 22: @@
 The tutorial here is aiming to offer a basic example, which should help building more complex external applications for deciding the SIP routing to be performed by Kamailio.
+==== RTJSON Routing Document ====
+The structure for RTJSON routing document is detailed at:
+  * [[http://kamailio.org/docs/modules/stable/modules/rtjson.html#rtjson.json-routing-structure|RTJSON Readme - Document Structure]]
+Next is a partial example, with the attributes for one destination:
+<code javascript>
+{
+ "version": "1.0",
+ "routing": "serial",
+ "routes":
+  [
+   {
+     "uri": "sip:127.0.0.1:5080",
+     "dst_uri": "sip:127.0.0.1:5082",
+     "path": "<sip:127.0.0.1:5084>, <sip:127.0.0.1:5086>",
+     "socket": "udp:127.0.0.1:5060",
+     "headers": {
+       "from": {
+         "display": "Alice",
+         "uri": "sip:alice@wonderland.com"
+       },
+       "to": {
+         "display": "Bob",
+         "uri": "sip:bob@wonderland.com"
+       },
+       "extra": "X-Hdr-A: abc\r\nX-Hdr-B: bcd\r\n"
+     },
+     "branch_flags": 8,
+     "fr_timer": 5000,
+     "fr_inv_timer": 30000
+   },
+...
+  ]
+}
+</code>
+The **routing** field specify if Kamailio has to do serial or parallel forking. After that, the relevant routing information is an array of destinations stored in **routes** field.
+Each destination corresponds to a SIP branch that is going to be created by Kamailio. For each branch can be specified values to set:
+  * request uri
+  * outbound proxy address (dst uri)
+  * display name and uri for From/To headers
+  * extra headers
+  * retransmission and ringing timeouts
+  * local socket or the path to be followed
+  * branch flags
+The example above results in: the request will be routed to sip:127.0.0.1:5080, via sip:127.0.0.1:5082, sip:127.0.0.1:5084, sip:127.0.0.1:5086; it will be sent using local socket udp:127.0.0.1:5060; From header display name will be set to **Alice** and From URI to **sip:alice@wonderland.com**; To header display name will be set to **Bob** and To URI to **sip:alice@wonderland.com**; branch flags will be updated with 8; retransmission will be done for 5000 milliseconds, waiting 30000 milliseconds while ringing.
 ===== Presentations =====
@@ Line 885: / Line 937: @@
   * http://nodejs.org
-A simple sample application is shown next:
+A simple sample application is shown next example. It connects to Kamailio's EVAPI socket, waiting for messages with json content serialized as netstring. There response will contain two destinations built with static values (sip:127.0.0.1:5080 and sip:127.0.0.1:5090), again serialazed as netstring.
-<code js kanapi.js>
+To read more about nestring format, see:
+  * https://en.wikipedia.org/wiki/Netstring
+Node.js application:
+<code javascript kanapi.js>
 var net = require('net');
@@ Line 1017: / Line 1075: @@
 </code>
+===== Resources =====
+  * [[http://www.kamailio.org|Kamailio Project]]
+  * [[http://kamailio.org/docs/modules/stable/modules/evapi.html|Kamaialio EVAPI Module]]
+  * [[http://kamailio.org/docs/modules/stable/modules/rtjson.html|Kamailio RTJSON Module]]
+  * [[http://kamailio.org/docs/modules/stable/modules/rtjson.html|Kamailio JANSSON Module]]
+  * [[http://nodejs.org|NodeJS Project]]
+  * [[https://en.wikipedia.org/wiki/Netstring|Netstring Format]]

Asipto - SIP and VoIP Knowledge Base Site

User Tools

Site Tools

Differences

Page Tools