Go to a SIP-Trace with Call-ID in POST request

[NiteCrwlr]

We have an external Application for searching Calls and getting Call-ID's. For drilldown by now we copy the Call-ID, paste it into homer7 and search for it. Is it possible to create a link and POST the Call-ID to homer, to directly search for this Call-ID and show the results?

[adubovikov]

Hi,

Yes, but usually not as a browser POST link from your external app. A normal <a href> or redirect can only do GET. The usual pattern is:

1. Your backend calls Homer API with the Call-ID (POST + auth)
2. Homer returns a view URL (GET)
3. Your app redirects the user to that URL

Homer 7 (homer-app + homer-ui)

Use the homer-app search API from your backend (POST, authenticated), filter by Call-ID, then either:

• open results in your own UI using the API response, or
• create a share link (stored search payload) and redirect the user to the Homer UI share URL

Homer 7 does not ship a simple "POST Call-ID from browser and land in SIP trace" button out of the box. Integration is API + redirect.

You also need a time window (from/to) together with the Call-ID for reliable search.

Homer 11

Homer 11 has a dedicated endpoint for this flow:

POST /api/v4/transactions/view/link (authenticated)

Example body:

{
  "session_id": "your-call-id-here",
  "proto_type": 1,
  "event_type": "1",
  "timestamp": {
    "from": 1710000000000,
    "to": 1710086400000
  }
}

Response includes url_view, e.g. /export/view/<uuid>. Send the user to:

https://<your-homer-host>/export/view/<uuid>

That page opens the SIP trace without the user pasting the Call-ID. The link is time-limited and has a max open count.

You can also use POST /api/v4/transactions/search and POST /api/v4/transactions/messages if you want to embed results in your own app instead of redirecting.

Practical recommendation

From your call search app:

1. User clicks a call
2. Your server POSTs Call-ID + time range to Homer (H7 search/share API, or H11 view/link)
3. Browser GET redirect to the returned Homer view URL

If you tell us your Homer version (7 vs 11) and whether users already log into Homer, we can suggest the exact API calls and auth setup.

[NiteCrwlr]

Thanks! We have homer7 and now successfully use:
http://homer:9080/search/result?{"timestamp=:{"from":mytimestampfrom,"to":mytimestampto},"param":{"search":{"1_call":{"callid":["mycallid-1234"]}}}}=

[adubovikov]

Thanks for sharing what worked on Homer 7 - that’s exactly the legacy homer-ui pattern.

A few notes for others copying it:

• The query string is one JSON object; use "timestamp":{"from":...,"to":...} (colon after timestamp, not timestamp=:).
• The trailing = is intentional for homer-ui parsing.
• callid is an array: "callid":["mycallid-1234"].
• The profile key 1_call is the SIP-calls mapping in homer-app.
• Users still need to be logged into Homer; the link does not carry credentials.
• Always pass a time window (from / to in ms) with the Call-ID.

Homer 11 equivalent (dashboard deep link, no /search/result path):

https://<homer-host>/?call_id=mycallid-1234&from=<from_ms>&to=<to_ms>#dashboard
(User must be logged in; same idea as your H7 link.)

For integrations without a Homer UI session (e.g. external app + API token on the server), use:

1. POST /api/v4/transactions/view/link with Auth-Token or a service JWT
2. Redirect the browser to https:///export/view/ from url_view

That opens a standalone SIP trace page (time-limited / max opens) and does not require paste or a dashboard login.

Glad the H7 URL works for you - we’ll keep this thread as the reference for both approaches.