kamailio:k43-async-sip-routing-nodejs

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
kamailio:k43-async-sip-routing-nodejs [2015/09/07 12:49] – [Node.js Application] adminkamailio:k43-async-sip-routing-nodejs [2015/09/07 12:53] – [RTJSON Routing Document] admin
Line 74: Line 74:
  
 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. 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.
 +
 +==== EVAPI Processing ====
 +
 +EVAPI is sort of generic framework to push events to external application from inside kamailio.cfg via TCP connections. It has the capability of suspending the processing of the SIP request until there is a response from the external application. By suspending the SIP request, other SIP messages can be processes, thus not blocking Kamailio while waiting for event response. This asynchronous mechanism enables high throughput for SIP routing.
 ===== Presentations ===== ===== Presentations =====
  

100%


Copyright 2010-2020 Asipto.com