Honestly just for signaling efficiency. I do everything with TLS, and
maintaining 900+ TLS sessions all the time is wasteful, especially for
endpoints that will be infrequently used. I would prefer to register a
single signaling trunk per device.
On 3/21/2019 9:03 AM, Matthew Yaklin wrote:
When I read your email the first thought that popped into my head was
a bunch of Calix E5-111s used for pennies on the dollar. They are
simply ADSL/POTs boxes. 48 ports of pots. But each line registers
individually. But at least the box is stupid dumb and you handle
everything on the switch side. I would not want anything complex on
site barring a distinct requirement. Of course just turn off the ADSL.
Why do you prefer that the lines do not register individually? Do you
have a requirement for so much box intelligence in their closets?
*Matthew Yaklin*
Network Engineer
*FirstLight*
359 Corporate Drive │ Portsmouth, NH 03801
Mobile 603-845-5031
[email protected] | www.firstlight.net
/This email may contain FirstLight confidential and/or privileged
information. If you are not the intended recipient, you are directed/
/not to read, disclose or otherwise use this transmission and to
immediately delete same. Delivery of this message is not intended/
/to waive any applicable privileges./
------------------------------------------------------------------------
*From:* VoiceOps <[email protected]> on behalf of Ryan
Delgrosso <[email protected]>
*Sent:* Thursday, March 21, 2019 11:55:37 AM
*To:* [email protected]
*Subject:* [VoiceOps] Request for Opinions: High density ATA's
I have found myself with a number of hospital opportunities and
servicing the staff with IP phones is a no-brainer, however there is the
need for multi-hundred room connectivity for patient room phones and the
staff mandate is to keep it analog because "ip phones there will grow
legs".
I am looking for 24+ port density with amphenol connectors, and ideally
some kind of rudimentary internal routing so i dont need to register all
24 discreet ports and can route by some header (to or uri) within a
single registration.
Right now im looking at AudioCodes and the Sangoma Vega series. Obihai
would be my natural choice here but don't have anything that fits my
density requirements.
Any opinions on these or others I should consider. Anyone deploy these
and can speak to the experience?
Thanks in advance
-Ryan
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
