3 Legs/call-ids Correlation Mapping

[idanam-del]

Hey, this the example mapping for a 2 way correlation

Full Example for 2-way correlation
Mapping

[
    {
       "source_field": "data_header.callid",
        "lookup_id": 1,
        "lookup_profile": "call",
        "append_sid": true,
        "lookup_field": "data_header->>'X-CID'",
        "lookup_range": [
            -300,
            200
        ]
    },
    {
        "source_field": "data_header.X-CID",
        "lookup_id": 1,
        "lookup_profile": "call",
        "append_sid": true,
        "lookup_field": "data_header->>'X-CID'",
        "lookup_range": [
            -300,
            200
        ]
    },
    {
        "source_field": "data_header.X-CID",
        "lookup_id": 1,
        "lookup_profile": "call",
        "append_sid": true,
        "lookup_field": "data_header->>'callid'",
        "lookup_range": [
            -300,
            200
        ]
    },
    {
        "source_field": "data_header.callid",
        "lookup_id": 1,
        "lookup_profile": "call",
        "lookup_field": "sid",
        "lookup_range": [
            -300,
            200
        ]
    }
]

What would be an example of a 3 way correlation?

1. Phone -> Sip Server
2. Sip Server -> SBC
3. SBC -> Provider

[Lorenzo Mangani]

Correlation is cascading. If your X-CID logic cascades over multiple sessions, there's nothing else you should need to configure for correlation to work. If you have different headers at play, you'll need additional rules. Hope this helps!