मुख्य सामग्री पर जाएँ
शब्दावली November 2026 6 मिनट का पठन

What Is Network Effectiveness Ratio (NER)?

Network effectiveness ratio (NER) measures how often the network did its job, counting busy and declined calls as successes. See the SIP formula and example.

D
November 2026
अंतिम अपडेट

त्वरित उत्तर

Network effectiveness ratio (NER) measures how often the network delivered a call to the far end, whatever the person there then did. RFC 6076 defines the SIP version, the Session Establishment Effectiveness Ratio (SEER), by counting INVITEs that receive a 200, 480, 486, 600 or 603 response, and says it is similar to the NER defined in ITU-T E.411.

Answer seizure ratio has a weakness: it treats every call that was not answered as a failure, including calls where the network worked perfectly and the person on the other end was simply busy or chose not to take the call. Network effectiveness ratio is the companion measure that corrects for this. It asks a narrower question: did the network do its part.

The Definition

ITU-T E.411 is the telephone-network reference for NER. Its ITU page lists the title and versions only, so the SIP formula comes from the IETF. RFC 6076 defines the Session Establishment Effectiveness Ratio (SEER) and states that it is similar to the Network Effectiveness Ratio defined in ITU-T E.411.

The SEER formula counts the INVITE requests that receive an associated 200, 480, 486, 600 or 603 response and divides by the total number of INVITE requests minus those that received a 3XX response, multiplied by 100. RFC 6076 says the 480, 486, 600 and 603 codes were chosen because they clearly indicate the effect of an individual user of the user agent. It accepts that a user could cause other responses too, for example by misconfiguring the user agent, but that this cannot easily be determined from an intermediary, so response codes such as 401, 407 and 420 (its words: "not an exhaustive list") were left out of the numerator. It is measured at the originating user agent and expressed as a percentage.

What the Counted Responses Mean

RFC 3261 names these responses. A 200 is OK, the success response. A 480 is Temporarily Unavailable, a 486 is Busy Here, a 600 is Busy Everywhere and a 603 is Decline. RFC 6076 describes the four non-200 codes as ones that clearly indicate the effect of an individual user of the user agent, that is, the call reached the far side and the far side responded. The network carried the request; the user or their device responded. That is why NER treats them as network successes.

A Worked Example

This uses made-up round numbers for illustration. Take the same hour as the answer seizure ratio example: 1,000 attempts, 20 redirected with a 3XX, 380 answered with a 200 OK. Add that 150 attempts returned 486 Busy Here, 60 returned 480, and 40 returned 603 Decline, while the rest failed in other ways. The numerator is 380 plus 150 plus 60 plus 40, which is 630. The denominator is 980. NER is 630 divided by 980, about 64.3 percent, against an ASR of about 38.8 percent for the same traffic.

The gap between the two figures is the share of calls the network delivered that nobody answered. If the gap suddenly narrows or widens on one route while others stay steady, something changed on that route.

Why It Matters for Outbound and Inbound Teams

Outbound traffic produces a lot of busy, unavailable and declined results, and a single ASR figure would blame the carrier for all of them. Comparing NER and ASR per trunk helps separate a route problem from a list problem. If NER is low, calls are not reaching destinations: the cause is likely on the SIP ट्रंक or the route. If NER is healthy and ASR is low, the network is delivering and the explanation sits in the list, the calling hours or the caller number.

When you connect your own carriers through BYOC, DialerBee shows trunk health including answer-seizure ratio, average call duration, post-dial delay and estimated MOS, with failover to a backup carrier when quality drops below your threshold. The step-by-step SIP trunk setup guide shows where those trunk settings sit. At campaign level, कनेक्ट दर is the matching measure of dials that become live conversations.

Limits of the Metric

  • The code list is a choice. RFC 6076 accepts that a user can cause other responses too, but leaves those out because an intermediary cannot easily tell, so check which codes your reporting counts.
  • Definitions vary between tools. Ask how a report treats redirects and retries before comparing figures from different systems.
  • It does not measure audio. A call can be counted as a success and still sound poor. Quality is measured with metrics such as राज्यमंत्री.

अक्सर पूछे जाने वाले प्रश्नों

What is the difference between ASR and NER?

ASR counts answered calls out of attempts. NER also counts calls that reached the far end and were met with a busy, unavailable or declined response, because those reflect what the person did rather than a failure of the network. NER is therefore always at least as high as ASR on the same traffic.

Which SIP responses count toward NER?

In RFC 6076's SEER definition, the numerator counts 200, 480, 486, 600 and 603 responses. The RFC says other codes, such as 401, 407 and 420, were not included in the numerator, and calls that list of excluded codes not exhaustive.

Why are 486 Busy Here and 603 Decline counted as successes?

Because they show the request reached the destination and the user or device answered it. The network did its job; the person chose or was unable to take the call.

What does a low NER with a normal ASR mean?

Measured on the same traffic with the RFC 6076 formulas, NER cannot be lower than ASR, because its numerator includes every answered call. If NER itself is low, calls are failing before reaching destinations, so look at the trunk, the route and the carrier.

Is NER a guarantee of call quality?

No. It counts how many attempts the network handled, not how the calls sounded. Use MOS, jitter and packet loss for quality.

Related terms and guides: SIP ट्रंक, कनेक्ट दर, answer seizure ratio, BYOC, connecting your SIP trunk.

सूत्रों का कहना है

संबंधित लेख: SIP error codes on outbound calls: 403, 486, 503 and more · Post-Dial Delay (PDD)

संबंधित शब्द

DialerBee को काम करते हुए देखने के लिए तैयार हैं?

15 मिनट के लाइव डेमो का अनुरोध करें, या 14 दिन का फ़्री ट्रायल शुरू करें — न स्लाइड, न कोई प्रतिबद्धता। कॉलिंग तब शुरू होती है जब आपका अपना SIP ट्रंक या PBX जुड़ जाए और मंज़ूर हो जाए।

14 दिन का फ़्री ट्रायल · मुफ़्त AI क्रेडिट · कोई कार्ड नहीं · 11 भाषाएँ · BYOC · अनुपालन में सहायक नियंत्रण

पूरी साइट अंग्रेज़ी में देखें →