This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
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:34] – [RTJSON Routing Document] 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. | 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:// | ||
+ | |||
+ | Next is a partial example, with the attributes for one destination: | ||
+ | |||
+ | <code javascript> | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | [ | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | }, | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | }, | ||
+ | " | ||
+ | }, | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | }, | ||
+ | ... | ||
+ | ] | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | 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 | ||
===== Presentations ===== | ===== Presentations ===== | ||