Escalating a Fault: Getting Past First-Line Support Without Losing a Day
There are two kinds of telephone fault. The first is found and fixed in an hour. The second bounces between the carrier, the equipment vendor, and the network team for three weeks while users lose confidence in all three. The difference is rarely technical difficulty. It is the quality of the evidence in the first ticket.
Prove Where the Fault Is Not
Every provider's first response is to ask whether the problem is on your side, and they will keep asking until you answer it convincingly. The fastest route to resolution is a ticket that already contains the proof: a test call from a known external number, the time it failed, the extension involved, and a packet capture showing whether media arrived. Where the fault is intermittent, a log of failure times is more persuasive than any description.
| Evidence | What it rules out | How to collect |
|---|---|---|
| Test call time and number | Ambiguous timing | Note the clock, use a known mobile |
| Packet capture at the edge | Your LAN or your gateway | Capture during a failing call |
| Trunk registration and status | Authentication and reachability | Platform status page, screenshots |
| Signal trace for the call | Dial plan and routing | Trace by call ID or time |
| Comparison call on another trunk | Carrier versus platform | Same destination, other route |
| List of affected and unaffected users | Scope of the fault | Simple table with times |
One Ticket, One Owner, One Question
A ticket that asks five questions gets five partial answers. The effective pattern is one ticket per fault, containing the evidence, asking a single specific question: whether the carrier can see the media arriving for this call at this time. That question has a yes or no answer, and either answer moves the fault forward. Repeating it politely, with the reference number, on a defined cadence is more effective than escalating emotionally.
- Collect evidence before calling, not during the call
- Ask one specific question per ticket
- Record every reference number and every promised callback
- Escalate on a schedule, in writing, referencing the history
- Name a single internal owner for the fault
- Ask what the service credit requires while the fault is open
The Comparison Call
One of the most useful tests is a call to the same destination from a different route: another trunk, another site, or a mobile. If that call succeeds while the first fails, the fault is isolated to a path rather than to the destination, and that narrows the discussion substantially. It takes two minutes and often ends a week of speculation.
Service Credits Are a Process
Contracts often provide credits for outages, and they almost always require evidence the customer did not keep: start and end times, affected services, and notification within a window. Reading the credit clause before the next fault, and recording faults in a way that matches its requirements, is the difference between recovering a month of charges and writing it off.
Redstone Approach
Redstone platforms provide trunk status, registration state, call detail records, and diagnostic tracing that can be exported for a carrier ticket, and Redstone support works fault tickets jointly with the carrier where the boundary is unclear. Deployments include a documented escalation path with named contacts on both sides.
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 :

