Current Location ：
Telephony and the Service Desk: Who Owns What
A voice fault is rarely contained within one team. The handset belongs to the desktop team, the platform to infrastructure, the network to networks, and the circuit to a supplier. Each team can plausibly say the fault is not theirs, and while they say it, the caller is still unable to make a call. The most valuable document in voice operations is not a design; it is a responsibility matrix that nobody enjoys writing.
Four Boundaries Where Voice Faults Live
Most disputes arise at the boundaries: between the handset and the platform, between the platform and the network, between the network and the carrier, and between the business and the supplier. Naming an owner for each boundary, and stating what evidence that owner must produce, converts an argument into a handover. The evidence requirement is the important half: whoever holds the boundary must be able to show what they checked.
| Boundary | Typical owner | Evidence required |
|---|---|---|
| Handset to platform | Desktop or endpoint team | Registration state, device logs, replacement test |
| Platform to network | Infrastructure | Platform logs, port and address configuration |
| Network to carrier | Networks | Path test, packet capture at the edge |
| Carrier to supplier | Service owner | Ticket reference and supplier response |
| Business rules to configuration | Service owner | Change record and approval |
Triage Before Escalation
A short triage script answered by the person taking the call saves a round of escalation: is it one user or many, is it inbound or outbound, is it one site or all, did anything change recently. Those four answers usually identify the boundary immediately. Where the service desk cannot answer them, the fault moves between teams several times before anyone measures anything.
- Publish a triage script the service desk can use without escalation
- Name an owner for each boundary between systems and teams
- Require evidence at each handover, not an opinion
- Keep a single incident record across teams
- Review boundary disputes monthly and fix the process, not the person
Changes Cause More Faults Than Failures
A large share of voice incidents follow a change: a firewall rule, a firmware update, a switch replacement, a carrier migration. A change calendar that includes voice-relevant work, agreed with the teams that make those changes, prevents the worst incidents and shortens the rest. Where voice is not represented in change planning, it is discovered afterwards, in the form of one-way audio on a Monday morning.
When the Supplier Is the Boundary
Supplier engagement needs the same discipline. A ticket that says calls are bad will be answered slowly; a ticket with a time, a calling number, a called number, and a direction will be investigated. Whoever owns the supplier relationship should be able to produce that information without asking three other teams, which is only possible if the platform retains the detail and the triage captures the identifiers.
Redstone Approach
Redstone deployments include a support model that states what the platform retains, how to retrieve it, and which information makes a ticket actionable. We agree the escalation contacts and the response expectations in writing, so that a fault has an owner inside both organisations rather than a shared hope.
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.
