Docs

Send your circuits in one form; 2N5 verifies each one, calls them day and night, and alerts you first. Nothing to install on your PBX.

Know when a SIP trunk stops completing calls before your customers do. The SIP code as proof, retries before any alert, and escalation until someone owns it.

We call your 0800 toll-free number and your IVR the way a customer does, confirm the message, and alert the right team when something fails, with proof.

We measure the audio quality of every test call against the expected recording, not by estimating from network stats. Learn what MOS-LQO is and the thresholds.

Alerts only for confirmed failures, by email and SMS, tier by tier, until someone acknowledges with one tap. Maintenance windows silence alerts while you work.

Availability of every voice circuit over the year and the month, the way Brazilian contracts are measured, in reports sent every month in English or Portuguese.

An agent 2N5 installs on site measures latency, packet loss, jitter, and speed of each branch's internet link, and alerts you when the link goes down.

What data Monitor processes and for how long, the call audio rule, encryption, separation between customers, and how to exercise your rights under the LGPD.

Pricing per monitored circuit and service, with onboarding done by 2N5. See what is included and book a demo on your own numbers to receive a proposal.

How Brazil's SAC decree reaches each regulated industry, what is verified, what to check in the regulator's rules, and how to monitor your 0800 and IVR.

What Brazil's SAC decree asks of a bank's phone service, what to confirm with legal counsel, and how to document that the 0800 and IVR stayed up.

Running SAC for a regulated client means following that client's rules. How to document that every 0800 and IVR in the operation stayed up, client by client.

What ANS rule RN 623/2024 and Brazil's SAC decree ask of phone service, and how a health insurer documents that its 0800 and IVR stayed up around the clock.

Asterisk, 3CX, Intelbras, Grandstream, Cisco, Teams, Genesys Cloud, Avaya and Amazon Connect: where each one fails silently and what a real call proves.

Why a SIP trunk on 3CX stops completing calls while the dashboard stays green, where to look in 3CX for each symptom, and what a real test call proves.

Why a service number on Amazon Connect stops connecting or answers with an error, where to look, and what a real test call placed from the outside proves.

Why a trunk on Asterisk, Issabel or FreePBX stops completing calls without an alarm, where to look on each one, and what a real test call catches.

Why a SIP or E1 trunk in an Avaya environment stops completing calls without an alarm, where to look at each layer, and what a real test call proves.

Silent SIP trunk failures on Cisco CUBE, CUCM and Webex Calling, where to look on each one, and what a real test call placed from the outside proves.

Why an 0800 or service number on Genesys Cloud stops connecting or lands in the wrong flow, where to look, and what a real test call proves from the outside.

Why the SIP trunk on an Intelbras or Grandstream IP PBX stops completing calls without an alarm, where to look, and what a real test call proves.

Why Teams Phone numbers stop completing calls: SBC certificate, SIP OPTIONS, codecs, Operator Connect. Where to look and what a real test call proves.

How to tell whether your carrier's SIP or E1 trunk went down, read the SIP code and Q.850 cause of each failure, and open a ticket with evidence it can investigate.

How to confirm a Claro SIP or E1 trunk stopped, what each SIP code and Q.850 cause points to, and how to build a ticket with the evidence the carrier looks for.

How to tell that an Embratel SIP or E1 trunk stopped completing calls, read the SIP code and Q.850 cause of each failure, and take the proof to the ticket.

How to tell whether a Vivo SIP or E1 trunk stopped completing calls, the SIP codes and Q.850 causes of each failure, and what evidence to put in the ticket.

Every SIP response code in the IANA registry, from 100 to 608, with what each one means and how a real test call reads each response.

The 72 ITU-T Q.850 release causes, what each one means, and the RFC 3398 map between Q.850 causes and SIP response codes in both directions.

Short definitions and examples of telephony and voice over IP terms: MOS, MOS-LQO, jitter, SIP ALG, IVR, DID, 0800, SIP trunk, SLA and more.

Practical guides on SIP trunks, 0800 numbers and IVRs, voice quality, telephony SLAs and error codes, written by the people who build the monitoring.

Why an 0800 line goes down without anyone noticing, how to test the 0800 and IVR from outside, what Brazil's SAC rules require and what to do when it stops.

What Decree 11,034/2022 and Anatel's RGC (Resolution 765) require of phone support in Brazil, and how to document that your 0800 and IVR stayed up.

Why a VoIP call connects with no audio or one-way audio: NAT, SIP ALG, RTP ports, the external IP in the SDP, codecs and SRTP. How to find the cause and fix it.

How to monitor SIP trunks, 0800 numbers and IVRs: ping, SIP OPTIONS, passive capture or a real test call, the retry ladder and the evidence that holds up.

How to calculate the availability SLA for SIP trunks and 0800 numbers, by year and by month: the formula, what 99.9% allows, maintenance and what counts as down.

What MOS means in VoIP, how measured MOS-LQO differs from the E-model's estimate, how much jitter, loss and delay voice can take, and what to do about a low score.

Your 0800 works from a landline but not from a mobile? The common causes, from origin blocking to routing, and how to test each one before you open a ticket.

Honest comparisons between Monitor by 2N5 and PRTG, Zabbix, VoIPmonitor, Sipfront and the alternatives to Cyara, with sources and where each one is better.

Cyara (now including Spearline), Klearcom, VistaCX and Monitor by 2N5 compared: what each one does, what it publishes, and where 2N5's managed service fits.

PRTG watches networks and servers and estimates MOS from the network; Monitor really calls SIP trunks and 0800 numbers and measures the voice. When to use each.

Both place test calls and use ViSQOL. Sipfront is self-service with public pricing; Monitor is a managed service run by 2N5, with alerts by email and SMS.

VoIPmonitor passively listens to the calls on your network; Monitor places real test calls and measures the voice that arrives. Here is when to use each one.

The Zabbix template for Asterisk reads the PBX's own status; Monitor really calls every circuit. Also compared: a home-grown test-call script on Asterisk.

Turn an availability target into the downtime it allows per year, month, week and day, or work out the SLA you actually had. With maintenance windows.

Type a SIP response code, such as 503 or 486, and see its official name, what it means, and the page with causes, diagnosis and what to send the carrier.

Monitor is 2N5's managed service that monitors voice circuits with real calls. Who we are, who writes this website, and how to get in touch with 2N5.

Fayaz Noor builds Monitor for 2N5, from the test call engine to voice quality measurement and the reports. He is the author of the guides on this website.

How 2N5 handles personal data in Monitor: what is collected, why, for how long, who it is shared with, and your rights over it.

The terms of use of Monitor, 2N5's managed service that tests voice circuits with real calls: what it includes and what each side commits to.

How to use your LGPD rights over the data Monitor keeps: access, correction and deletion, and how to reach 2N5's data protection officer.