Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.telegent.com/llms.txt

Use this file to discover all available pages before exploring further.

Goal: Collect the partner’s webhook URLs and, for SIP partners, exchange SBC IPs and agree on signaling so the network is ready before testing begins.

Checklist

Webhooks — Inbound Messaging and DLR

#TaskOwner
1Partner provided inbound message webhook URL (with auth type: Bearer / Basic).Partner
2Partner provided DLR (delivery report) webhook URL — may reuse the inbound URL.Partner
3Webhook URLs reachable from Telegent infrastructure (firewall / IP whitelist done).Joint
4CDR delivery method chosen: webhook / email / both. Voice and SMS files are split.Partner
5Partner reviewed inbound JSON schema (Message_ID, Owner, To, From, Message_Body, Segment, etc.) per the Customer FAQ.Partner

SIP Interconnect — If Voice via SIP is in Scope

#TaskOwner
6Partner provided SBC public IP(s) for SIP signaling and media.Partner
7Telegent provided Telegent SBC IP(s).Telegent
8Mutual IP whitelist applied on both sides.Joint
9Custom SIP headers agreed (e.g., hairpin flags for FMC, identifying flag headers).Joint

Inbound Message Webhook — Expected JSON Schema

When an inbound SMS/MMS is delivered to your webhook, the payload includes:
FieldDescription
Message_IDUnique identifier for the message
OwnerThe Telegent number that received the message
ToRecipient number (E.164)
FromSender number (E.164)
Message_BodyText content of the message
SegmentNumber of SMS segments
For the full inbound message schema, refer to the Customer FAQ provided by your Telegent representative.

Phase complete when: Webhooks are reachable from Telegent, and (for SIP partners) both sides have whitelisted each other and agreed on headers.

Previous: Phase 1 — Credentials & Access

Credentials and first OAuth token

Next: Phase 3 — API Walkthrough & Testing

End-to-end sandbox testing