Why does Monitor work with any platform?
Because it integrates with none of them. Monitor calls the numbers the way a customer does and judges what happened: whether the call connected, whether audio flowed both ways, whether the right message played and whether voice quality stayed above the threshold. None of that depends on the PBX or the platform.
What changes from one platform to the next is where the failure starts and where your team looks to fix it. That is what each page below describes.
Which platforms have a page?
The pages below cover the PBXs and contact-center platforms most common in Brazilian companies. Each one lists that platform’s silent failures, a table of symptom, SIP code and where to look, and what a real test call proves that its dashboards do not show.
- Asterisk, Issabel and FreePBX: registration, NAT, codecs and automatic bans, with the commands for each.
- 3CX: the registered trunk that receives no calls, and where to read the Activity Log.
- Intelbras and Grandstream IP PBX: the branch-office PBX behind an ordinary router, with SIP ALG and a dynamic IP.
- Cisco CUBE, CUCM and Webex Calling: dial-peers, TLS trunk certificates and transcoding.
- Microsoft Teams: the SBC certificate and SIP OPTIONS in Direct Routing, and what changes with Operator Connect.
- Genesys Cloud: the trunk to the cloud and the number that lands in the wrong IVR flow.
- Avaya: SIP and E1 trunks crossing an SBC, session routing and the call server.
- Amazon Connect: the 0800 forwarded by the carrier, the contact flow and the call quota.
Which silent failures apply to each type of platform?
Not every failure exists on every platform. An on-premises PBX suffers from the router and the internet link; a cloud platform does not have that problem, but depends on the carrier’s path to it and on the configured IVR flow. The table summarizes where each type of failure tends to show up.
| Failure | On-premises PBX | SBC on your network | Cloud platform |
|---|---|---|---|
| Expired SIP registration | Yes, on registering trunks | Yes, when the trunk registers | Only on your carrier’s trunk, if there is one |
| NAT and SIP ALG | Yes | Yes | No, unless your own equipment is in the path |
| Expired certificate | On TLS trunks | Yes, on TLS connections | On the TLS trunk to the cloud, if there is one |
| No matching codec (488) | Yes | Yes | Rarely |
| Channels or quota exhausted (503) | Yes | Yes | Yes, on the platform quota |
| Number without a route (404) | Yes | Yes | Yes |
| IVR playing the wrong message | Yes | — | Yes |
How do you read a failure on any platform?
Start with the response the call received. The SIP code tells you what kind of problem stopped the call, and the Q.850 cause, when the network sends one, tells you why. The SIP codes and Q.850 causes pages explain each one, with what to check and what to send to the carrier.
When the failure is in the trunk rather than the platform, the carriers pages show how to open a ticket with the right evidence.
How do you get started?
You send the numbers to monitor and who should be notified; 2N5 proves each circuit with a real call and starts calling at the agreed pace. See SIP trunk monitoring, 0800 and IVR monitoring and how it works.
Frequently asked questions
Does Monitor integrate with any of these platforms?
No, with none of them. Monitor calls the numbers you choose, from the 2N5 platform, the way a customer does. That is why it works with any PBX, on-premises or in the cloud, and with any contact-center platform, with nothing to install and no access to your systems.
My platform is not on the list. Will it work?
Yes. The pages in this section exist to show where each platform tends to fail and where to look, not because monitoring depends on it. If the number can take a call from the outside, Monitor can call it and judge the result.
Why isn't the platform's own monitoring enough?
Because it shows the platform from the inside. It does not see a call the carrier failed to deliver, and it does not know whether the IVR played the right message to the caller. A test call placed from the outside sees what the customer sees, with the route's SIP code as proof.