When SIP Events Never Reach the CRM: A Triage Order for Webhook and API Failures
The platform shows the call, the customer relationship system has no record of it, and the argument starts about which system is at fault. Both sides are usually telling the truth. The failure sits between them, in a gap that is invisible from either end, and it is usually a certificate, a changed field name, an expired secret, or a firewall rule that somebody added last month.
Establish Where the Chain Broke
There is a fixed sequence between a call happening and a record appearing in a customer relationship system: the platform detects the event, queues it, formats it, posts it to the receiving endpoint, the endpoint accepts it, the receiving system authenticates it, and the record is written. Each stage can fail and each produces a different symptom. The temptation is to start at the customer relationship system, because that is where the missing record is noticed, and work backwards. Working forwards from the platform is faster, because the platform usually records whether delivery was attempted and what the peer replied.
Ask for the platform's delivery log and its own event log before anything else. Without those two artefacts the discussion becomes a comparison of recollections, and recollections are not evidence.
| Stage | Artefact that proves it | Failure signal |
|---|---|---|
| Event detection | Platform call detail record | Call present internally but no event queued |
| Queue and format | Event log entry | Events queued but never delivered |
| Transport to endpoint | Delivery log with peer response | Connection refused, timeout, or TLS error |
| Endpoint acceptance | HTTP status returned to platform | Reject status with a stated reason |
| Authentication | Receiver's own audit log | Rejected credentials despite a valid request |
| Record write | Record present in the receiver | Accepted request with no resulting record |
The Failure Modes That Account for Most Cases
Certificate problems on the receiving endpoint appear often enough to be worth checking first. A customer relationship system behind a load balancer presents a certificate issued for a different host name, or one that expired during a renewal nobody told the voice team about. The handshake fails, the platform retries, and the retries are frequently configured to be quiet, so the only evidence is a gap in the event stream.
Schema drift is the second common cause. A change to the field names in the webhook contract, made by the receiving team without telling the voice team, produces a rejection at the endpoint. Then the authentication secret expires and the response changes. Then a rate limit appears upstream and the responses change again. Each returns a specific status code, and each deserves to be distinguished from a generic failure.
One cause sits outside the software entirely: source address allowlisting. A platform that posts from a new address after a migration, or an endpoint that now sits behind a proxy whose address changed, will be blocked silently by something in between. Nothing in either application's logs will show the drop, which is precisely why it is worth checking the firewall rules by hand.
Check the Obvious Ones in Order
There is a sequence that resolves most of these in under fifteen minutes, and it is worth writing down so that it is followed under pressure rather than improvised. Take the delivery log for the affected period and isolate one event that failed and one that succeeded. Compare the two requests field by field. The difference between a working request and a broken one is the diagnosis, and it is usually visible in the address, the headers, or the certificate presented by the endpoint.
- Pull the delivery log before asking the receiving team for anything
- Compare one successful request with one failed request, field by field
- Check the certificate on the receiving endpoint, including the host name
- Confirm the contract has not changed by checking recent releases on both sides
- Check whether the secret or token has rotated since the last successful delivery
- Verify the source address is still permitted by every firewall in the path
- Note the status codes returned, since each code points to a different fault
Replaying an Event Without Duplicating a Record
Replaying is the fastest way to prove a fix and the fastest way to create a duplicate. A replayed ringing event may create a second opportunity in the receiving system. A replayed answered event may create a second call record, and in a system that drives dialler campaigns a duplicate record is worse than a missing one. Decide before replaying whether the endpoint is idempotent, whether the receiving system deduplicates on a supplied identifier, and whether the event carries one that it can key on. If it does not, replaying is effectively a database change performed by an administrator.
Where the platform can mark a replayed event so that it does not produce a second record, that is the preferable route. Where it cannot, note the identifiers that were replayed in the incident record so that the duplicate can be explained later rather than discovered.
Redstone Approach
Redstone platforms deliver call events to external endpoints through configurable event and webhook targets, and delivery attempts together with the peer responses are retained for inspection rather than discarded. Group and campaign behaviour can be configured to avoid triggering a duplicate record on retry, and the platform's own call detail records remain the reference copy when the external system is the one that has lost data.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.

Current Location :

