• deanm



    Viewing 7 replies - 1 through 7 (of 7 total)
    • in reply to: PC please call home #2556533

      Very true!  I didn’t realize that was the problem you were trying to solve.  You can also install cell phone signal “repeaters” – they are common in larger buildings, even required by many municipalities so that first responders don’t lose connection in the bowels of some large building.





    • in reply to: PC please call home #2554501

      I think your questions have been answered here, but if not, please clarify.  Many MANY providers offer the services you describe. Specifically, you asked about calling from desk phones and laptops.  YES, most products can do this.

      Again using Zoom Phone as an example, various manufacturers market Zoom-compatible desk phones. Here is a list on their website: Zoom Certified Hardware.

      The capability is SO widespread that I would encourage you to look at technology providers  – consider something that is integrated with your existing tools: Microsoft, Webex(Cisco), Google

      Smaller players exist too…  search “Virtual PBX” if you want to be overwhelmed.

      Depending on the size of your business and your budget, you might save yourself a lot of time and money by hiring a UCaaS consultant.

      1 user thanked author for this post.
    • in reply to: Shift to MS365 for four nonprofit PCs #2553979

      GREAT info. It hadn’t occurred to me to create a subdomain to “protect” the primary domain. Still resolving to the same IP address as the primary server I assume?

      Also, you hit the nail on the head with the BCC sending scheme.  That is how we send presently. Does the newsletter software break each recipient out into their own “direct” email?  Care to share what software you use?

      We’ve considered using Constant Contact or MailChimp, et. al.  (and with our nonprofit status might get those services “donated”). Simplicity is king here – our part-time secretary needs to operate the system and while she IS competent, there is little sense asking her to learn anything complex.

      Thanks for your help!

    • in reply to: Shift to MS365 for four nonprofit PCs #2553972

      Thank you cyberSAR, that is relevant experience.  Anyone else able to confirm? This thread has veered completely into the email deliverability topic… will a move to Microsoft email hosting fix our deliverability issues? How about for newsletters sent to <100 recipients?

    • in reply to: PC please call home #2553971

      Let’s see if I can help with some useful detail by describing my current setup.

      My team and I recently switched to this type of system. Eight of us function completely autonomously in/out of the office with no change in what callers see when they call us or when we call them.

      There are many providers, but we are trying “Zoom Phone.” That’s right, the video meeting company. It is working well for us.

      We can make/receive calls anywhere we can install the Zoom app – the same app you are probably familiar with (that’s a plus and may influence which provider you choose).

      Here is the step where I might lose you – or offend you by assuming you lack some knowledge – but here we go.

      We are all familiar with “phone numbers” and there is a relevant acronym we might as well use here: “DID” – Direct Inward Dialing.  You probably have a DID for your office, a separate one for your cell phone, maybe others.  You are also familiar with “forwarding” calls from one DID to another.  For instance, you forward your office phone to your cell phone.

      What number appears on caller-ID when you call other people? You might say “the phone in my hand” but that can be a bit more complicated. Take my workplace of over 1000 DID numbers.  Placing a call from any phone in the place will appear as one generic “main” number!

      My point here is that someone made that decision. This notion of numbers being attached to physical hardware (cell phones, desk phones, computers) is false.  An outgoing call can display whatever the system is programmed to display.  This get a bit tricky, because guess what! People figured out they could “spoof” other people’s numbers, making it hard to pin down who is or isn’t a telemarketer.

      (Reputable) providers will not allow you to just “set” your outgoing caller ID to your office number for that reason.

      The Solution: “Port” your (DID) phone number to a virtual phone system provider.  Call it VOIP if you like, but the distinction between wired and virtual no longer really matters.

      Have you ever switched cell phone providers while keeping your existing (DID) phone number? Same concept.  Once the DID phone number is “in the cloud,” you can into and out of it from anywhere, and with any hardware (oversimplification).  Your desk phone will probably have to be replaced with one compatible with your preferred provider.  In essence, it will be a box with software, just like your cell phone, just like your computer. It doesn’t matter how it gets a connection to the internet (ethernet cable, WiFi, cell phone network, satellite).

      You can receive calls on any DID number you control. You can “dial out from” any DID number you control (oversimplification).

      There is no “app” you can install – or service you can buy – which will give you the ability to “call from” someone else’s DID number.  You must have the right to “port” the number to a different service (Vonage, Zoom Phone, or literally thousands of their competitors).

      IF you own the business or are assigned the power/responsibility to manage the DID numbers, you can make this happen.

      I’m rambling now. What questions do you have?

      3 users thanked author for this post.
    • in reply to: Shift to MS365 for four nonprofit PCs #2553954

      Thank you cyberSAR –

      I have successfully edited DNS records in the past, that part of the change seems rather straightforward. Bigger picture, can we expect the shift to MS serving will fix our deliverability problem?

      I’ve tried to wrangle .pst files in the past… now THAT is something I might want to hire done!

    • in reply to: Shift to MS365 for four nonprofit PCs #2553941

      Hello Susan

      Yes we have a custom domain and the mail server is hosted at InMotion Hosting. The email server is on a shared IP, which I know makes us vulnerable to the behavior of other clients using that IP.

      Here’s a snippet from one recent response back from a receiving server (my emphasis):

      Reporting-MTA: dns; se4-iad1.servconfig.com
      Action: delayed
      Final-Recipient: rfc822;xxxxxx@rocketmail.com
      Status: 4.0.0
      Remote-MTA: dns; mta6.am0.yahoodns.net
      Diagnostic-Code: smtp; 421 4.7.0 [TSS04] Messages from temporarily deferred due to unexpected volume or user complaints –; see https://postmaster.yahooinc.<wbr />com/error-codes

    Viewing 7 replies - 1 through 7 (of 7 total)