4xx Client error, RFC 3261

SIP 487 Request Terminated

SIP 487 Request Terminated means the call was cancelled before it was answered, usually because the caller hung up or the system's ring time ran out.

Who sends it: The called side
When: Ringing, before answer
Retry?: Only if the cancel was not intended.
The caller hears: Nothing unusual: the ringing stops when the caller hangs up.

PBXYour phone or PBX

SIPThe SIP trunk

☎The called sidesends 487

FIX

What causes 487, and how to fix it

487 is what an INVITE receives after the caller sends CANCEL. Seeing it in logs is normal for calls abandoned while ringing.

1
Most common
The caller hung up before the call was answered.
Nothing to fix. 487 confirms the cancel was processed.
2
Most common
Your PBX cancels calls after its ring time, so long-ringing calls end with 487.
If calls stop ringing too soon, raise the ring or no-answer timeout on the outbound route.
3
Sometimes
The call rang several devices at once and another one answered.
Normal for ring groups: the other branches are cancelled with 487.
4
Rare
A device cancels calls on its own after a few seconds, for example a misconfigured timer.
If every call ends with 487 after the same few seconds, check the timers on the phone and PBX.

LOG

SIP/2.0 487 Request Terminated

SIP response

SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 203.0.113.10:5060;branch=z9hG4bK-74bf9
Call-ID: [email protected]

≠

487, 183 or 200?

Early audio while the call is ringing; 487 often follows when the caller gives up.

200

The call was answered. 487 means it never was, so it is not charged.

FAQ

Is SIP 487 an error?

Usually not. It is the normal reply to a CANCEL: the call was stopped before answer, most often because the caller hung up.

Am I charged for a call that ended with 487?

No. It was never answered, and on LinkedSIP only answered calls are charged.

The full list: SIP response codes. 487 again and again? Check your SIP trunk configuration.