SIP 607 Unwanted vs 608 Rejected
SIP 607 and 608 both reject calls, but with different signals to the network. A 607 marks the call as unwanted (potential spam/robocall), which can feed into call analytics and blocking systems. A 608 is a simple refusal without any spam signal — the callee just does not want to take this call.
विवरण
The called party did not want this call from the calling party. This response is used for robocall and spam call blocking.
जब आप इसे देखें
When the callee's system identifies the call as spam or unwanted. Used in STIR/SHAKEN call verification frameworks.
कैसे ठीक करें
If you are a legitimate caller being blocked as spam, ensure your STIR/SHAKEN attestation level is 'A' (full attestation). Contact the callee through alternative means.
विवरण
An intermediary machine or process rejected the call attempt. Similar to 607 but the rejection comes from the network rather than the end user.
जब आप इसे देखें
When a network element (not the callee) blocks the call. Used by analytics engines and call-blocking services in the network path.
कैसे ठीक करें
This is a network-level block. Contact the network administrator or carrier to understand why the call was blocked.
मुख्य अंतर
607 signals the call is unwanted/spam — networks can use this to update reputation scores and block future calls.
608 is a neutral rejection — the callee declined the call without implying it is spam.
607 was introduced by RFC 8197 specifically for robocall/spam mitigation infrastructure.
608 was introduced by RFC 8688 as a general-purpose call rejection without negative connotation.
607 may trigger the caller's reputation to be downgraded; 608 does not affect caller reputation.
कब किसका उपयोग करें
Use 607 when the callee identifies an incoming call as spam, robocall, or unwanted telemarketing. This feeds into STIR/SHAKEN analytics and helps carriers block future spam. Use 608 when the callee simply does not want to take the call but does not consider it spam — for example, declining a known contact's call during a meeting.