Login | Register

Documentation

About -> Available Versions? -> 2.3.x Releases -> Release 2.3.0

This page has been visited 265 times.

NonSIP Tracing examples

This page contains a series of nonSip tracing samples as they are traced by OpenSIPS using Homer Encapsulation Protocol. Each example will consist of the payload, the correlation id for the message and the extra correlation id which correlates the message to other protocols( like SIP ).

REST

Rest correlation id (correlates rest request with reply)
RESTCORR7y0AAJSUvligJ8dwAAAAAHWX+zk=
Extra correlation id (correlates rest with sip) - JSON encapsulated
{
        "sip":  "10f3e104-9158-458a-a341-ee4e281a74ee"
}
Rest Request - JSON encapsulated
{
        "first_line":   "GET /lrn/18329008433/&output=json&d=|&type=3 HTTP/1.1"
}
Rest Reply - JSON encapsulated
{
        "first_line":   "HTTP/1.1 200 OK",
        "payload":      "{"rn":"2819549999","data_points":2,"query_time":"113ms","ocn":"7982","number":8329008433,"created":"2017-03-07 05:39:37","rate":0.00045,"balance":"22.487400","from":8329008433}"
}

XLOG

XLOG correlation id (just for the sake of having a correlation id; not used) - SIP CallID
5da03998-3819-46d1-84c2-aafaf92266ab
Extra correlation id (correlates XLOG with sip) - JSON encapsulated
{
        "sip":  "10f3e104-9158-458a-a341-ee4e281a74ee"
}
XLOG message - JSON encapsulated
{
        "level":        "INFO",
        "text": "SCRIPT:DBG: PSTN routing for 18329008433/opensips.org (rpid <null>) via grp 1"
}

MI ( no extra correlation since MI is not linked to anythinkg else)

MI correlation id (correlates mi request with reply)
MICORRdkcAAPWY0lhASokjAAAAADFDWHk=
MI request - JSON encapsulated
{
        "command":      "sip_trace",
        "backend":      "xmlrpc",
        "parameters":   "hep_id"
}
MI reply - JSON encapsulated
{
        "code": "400",
        "reason":       "Bad parameter",
        "reply":        "<?xml version="1.0" encoding="UTF-8"?>
<methodResponse>
<fault><value>
<struct>
<member>
<name>faultCode</name>
<value><in"
}

TRANSPORT ( TCP, TLS, WS, WSS) - TLS example

Transport correlation ID uniquely identifying each TCP based connection ( will also be set as an extra correlation to SIP messages )

17640947659377874237

Connection accepted event(in real traces the master-key will be complete)
{
"server-subject": "/CN=opensips.org/ST=RO/C=RO/emailAddress=board@opensips.org/O=OpenSIPS",
"server-issuer": "/CN=opensips.org/ST=RO/C=RO/emailAddress=board@opensips.org/O=OpenSIPS",
"master-key": "9c70.........................87cd8ad",
"Status": "SUCCESS",
"Message": "Connection accepted..."
}
Connection closed event
{
"Status": "SUCCESS",
"Message": "EOF received"
}

Page last modified on March 22, 2017, at 06:37 PM