4 ms·
An example of why. I once worked on a team tasked with auditing the phone lines in an office building to identify potential cost savings on lines with outgoing
by stevetrewick 10y ago
An example of why. I once worked on a team tasked with auditing the phone lines in an office building to identify potential cost savings on lines with outgoing access.
We came across two on the PBX that no one could identify. Numbers not in the internal directory. No tags in the PBX terminal. Rang them repeatedly with no answer.
So we disabled them on the grounds that if they were in use we would soon get a call from someone enquiring why their line was dead. Nothing all week. Went home for the weekend.
You can probably see how this ended, and that's (just one of the reasons) why you don't route them through your PBX.
- walrus01 10y agoMore like an example of how their provisioning and documentation process is broken, you can absolutely have critical things on SIP (and PoE powered security cameras, etc), just don't forget to document it correctly.
- stevetrewick 10y agoSure. Absolutely. But if they'd been straight PSTN lines the abject process failure you've correctly described wouldn't have been able to put lives at risk because we'd have had to call the telco who most assuredly would have known what the lines were for, and we wouldn't have been able to shut them off. Safety critical systems need to not rely on humans doing boring, complicated things correctly for long periods of time.