Q.850 cause 127 Interworking, unspecified

What Q.850 cause 127 means

The call crossed into a network that does not report causes, so the gateway at the boundary had to say something and said this. Cause 127 is an admission of ignorance rather than a diagnosis: the real reason sits on the other side of an interworking point. It is common on international and some mobile routes, and it maps to SIP 500 Server Internal Error.

Interworking class
Sent by The gateway sitting at the boundary with the other network
Occasional

What Q.850 cause 127 Interworking, unspecified actually means

Every network boundary is a translation point, and translation only works if the far side supplies something to translate. Where it does not, the gateway knows the call ended but has nothing to say about why, and Q.850 provides this value precisely so it can be honest about that. Reading it as a fault is the standard mistake in call-record analysis, because a healthy international route can produce a steady background of it indefinitely. RFC 3398 maps it to 500 Server Internal Error, which sounds far more alarming than the situation usually warrants.

This cause indicates that there has been interworking with a network which does not provide causes for actions it takes. Thus, the precise cause for a message which is being sent cannot be ascertained.
— ITU-T Q.850 section 6.2.7.7.1

The SIP equivalent of Q.850 cause 127

A gateway translating this cause into SIP reports it as SIP 500 Server Internal Error. The mapping is defined in RFC 3398 section 7.2.4.1.

What causes Q.850 cause 127 on a business phone system

International routes through networks that do not pass causesOnce a call leaves the UK it may traverse several wholesale carriers with varying signalling maturity. The cause reflects the least informative network in the chain rather than the destination country as such.
Interworking with mobile networksMobile core networks use their own release causes which do not always translate cleanly. Calls to mobiles that end for ordinary reasons can be recorded this way with no fault present at all.
Least-cost routing through multiple wholesale suppliersTraffic handed between suppliers to find the cheapest path loses fidelity at each handover. The same destination can produce different causes on different days depending on which route was chosen.
Legacy ISDN interworking still in the pathA modern IP call passing through an older circuit-switched segment can lose its cause information at that boundary. This is worth checking during a PSTN migration, when such segments often persist longer than anyone realises.
A gateway that flattens anything it does not recogniseSome equipment substitutes this value rather than attempting a translation. Where that is the behaviour, the volume tells you about the gateway rather than about your calls.

How to fix Q.850 cause 127

Group the records by destination and by route firstA concentration on one country or one prefix is meaningful; an even scattering across everything is usually just how that gateway reports. This one piece of sorting prevents most wasted investigation.
Establish whether users are actually affectedCompare the count against completed calls to the same destinations and ask whether anyone has complained. A cause that appears in records but produces no complaints is a reporting artefact, not an incident.
Test the destination over an alternative pathDial the same number from a mobile or a second provider. If it connects reliably elsewhere, you have something concrete to put to your carrier.
Give the carrier specific examples so they can chase upstreamThey cannot see beyond their own interconnect either, so they need timestamps and numbers to raise it with their supplier. Vague reports about international quality rarely move.
Ask for a different route to a problem destinationCarriers usually have more than one path to any given country and can pin traffic to a better one. This is a routine request when you can show that a particular destination behaves differently from the rest.

Fixing the underlying problem

This page explains the code. These guides walk through the fix in detail.

Questions about Q.850 cause 127

Is cause 127 a fault on my system?

Almost never. It is generated at a boundary with another network and says only that no reason was supplied, so unless it is concentrated on one destination your own equipment is very unlikely to be involved.

Why do so many international calls report cause 127?

Because international calls cross more network boundaries, and each one is an opportunity for the reason to be lost. Some countries and some wholesale routes simply do not pass causes back, and no amount of configuration at your end changes that.

Can cause 127 be fixed?

Not directly, since you cannot make another operator send information it does not send. What you can do is have your carrier route the affected destinations differently, which often replaces the problem route rather than fixing it.

Related Q.850 cause values

Source. Q.850 cause 127 Interworking, unspecified is defined in ITU-T Q.850 section 6.2.7.7.1 and registered in the ITU-T Recommendation Q.850 (10/2018). The causes and fixes above are drawn from our own experience supporting UK business phone systems.

All Call hangup causes (Q.850) codes