I'm making the jump from landline to SIP here at $home this month. I've done it at enough clients, it's time for me to do it too. 😊
I'm also getting a fax SIP trunk as a second line.
Thanks.
Regards,
Michael B. Smith
Managing Consultant
Smith Consulting, LLC
--
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/174d1fe4f9f04695aeb819eede5f9ed3%40smithcons.com.
I started making the leap to SIP YEARS ago. We had all internet, voice, and data coming in from the same carrier, over the same fiber. Fax lines ran over Cisco ATAs and had no issues.
I've been running SIP at home for years as well. Also no issues.
I am running all faxing through cloud, so I cannot speak to that, other than to say that if they claim and can prove T.38 compatibility, then you should​ be fine. I fought those battles long ago with faxing and healthcare, so I understand your hesitation.
Have you been good today? ಠ_à²
On Wed, 31 Aug 2022 at 05:13, Michael B. Smith <mic...@smithcons.com> wrote:
- I'm making the jump from landline to SIP here at $home this month. I've done it at enough clients, it's time for me to do it too. 😊
Just catching up from being out, but none of what you’re looking at doing should pose a problem. We dumped our PRI lines years ago. The only place they were being used at that point was inbound traffic for the Mitel PBX. That was replaced by a fiber “flex” circuit which just splits off part of the bandwidth to provide the SIP traffic required to a converter which then tied to the PBX. That said, 75% of our phones were already SIP at the time and the choice not to go 100% SIP was more one of expedience than technical issues. If I were to do it again I’d be 100% SIP. As for FAX, it is still the bane of my existence as the primary users refuse to use cloud based fax for their outbound fax requirements. I can’t speak to the in house fax part, I left that behind when I last changed jobs for this one.
All that said we have luckily been able to provide multiple fiber circuits from multiple providers and also from multiple entry points to our facility to minimize if not eliminate the BIF factor as I think someone called it earlier. Cut a fiber, well, there’s still one at the other end of the building which is fed from the other cross street and which don’t have adjacent paths for at least 5 miles. That’s mostly a matter of luck with regards to location however unless you’re willing to spend big bucks in most cases.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
¯\_(ツ)_/¯
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/631223db.050a0220.ee5b6.a75eSMTPIN_ADDED_MISSING%40gmr-mx.google.com.
Just catching up from being out, but none of what you're looking at doing should pose a problem. We dumped our PRI lines years ago. The only place they were being used at that point was inbound traffic for the Mitel PBX. That was replaced by a fiber "flex" circuit which just splits off part of the bandwidth to provide the SIP traffic required to a converter which then tied to the PBX. That said, 75% of our phones were already SIP at the time and the choice not to go 100% SIP was more one of expedience than technical issues. If I were to do it again I'd be 100% SIP. As for FAX, it is still the bane of my existence as the primary users refuse to use cloud based fax for their outbound fax requirements. I can't speak to the in house fax part, I left that behind when I last changed jobs for this one.
All that said we have luckily been able to provide multiple fiber circuits from multiple providers and also from multiple entry points to our facility to minimize if not eliminate the BIF factor as I think someone called it earlier. Cut a fiber, well, there's still one at the other end of the building which is fed from the other cross street and which don't have adjacent paths for at least 5 miles. That's mostly a matter of luck with regards to location however unless you're willing to spend big bucks in most cases.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
¯\_(ツ)_/¯
From: ntsys...@googlegroups.com <ntsys...@googlegroups.com> On Behalf Of Ken Dibble
Sent: Friday, September 2, 2022 11:40 AM
To: ntsys...@googlegroups.com
Subject: Re: [ntsysadmin] Telephony, Fax & Internet, Oh My!
I knew this was gonna be a "niche" issue when I posted it. I am kind of surprised by the very small number of responses though. Thank you everybody, very much.
Ken Dibble
www.stic-cil.org
At 01:46 PM 8/31/2022, Jonathan Raper wrote:
- I started making the leap to SIP YEARS ago. We had all internet, voice, and data coming in from the same carrier, over the same fiber. Fax lines ran over Cisco ATAs and had no issues.
- I've been running SIP at home for years as well. Also no issues.
- I am running all faxing through cloud, so I cannot speak to that, other than to say that if they claim and can prove T.38 compatibility, then you should be fine. I fought those battles long ago with faxing and healthcare, so I understand your hesitation.
- Best of luck!
- Thanks,
- Jonboy
- VERY Timing Sensitive
- Packet Order MATTERS
- QoS applied
- Jitter Buffer DISABLED
- Echo Cancel DISABLED
- VAD/Silence Suppression DISABLED
- Codec Negotiation DISABLED
- Transcoding DISABLED
- Fax-Passthrough Mode DISABLED
- Fax parameters:
- On Wed, 31 Aug 2022 at 05:13, Michael B. Smith <mic...@smithcons.com> wrote:
- I'm making the jump from landline to SIP here at $home this month. I've done it at enough clients, it's time for me to do it too.