ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Weird Comcast to Voip.ms issue

    IT Discussion
    4
    7
    811
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • syko24S
      syko24
      last edited by

      So I ported a phone number from Comcast to Voip.ms about 3 weeks ago. Today I noticed that when I make a phone call to that ported number from another Comcast phone number it gets a busy signal. If I call from a cell phone or from AT&T it works fine. I contacted Voip.ms and they said Comcast needs to fix something on their network. Comcast says the carrier that is holding the number needs to fix something on their side. What do you guys think?

      1 Reply Last reply Reply Quote 0
      • syko24S
        syko24
        last edited by

        I even went over to a neighbor's business and made a call to the ported number from their Comcast phone number and still a busy signal.

        1 Reply Last reply Reply Quote 0
        • DanpD
          Danp
          last edited by

          Sounds like a problem on Comcast's end.

          syko24S 1 Reply Last reply Reply Quote 0
          • syko24S
            syko24 @Danp
            last edited by

            @danp - Yeah I am on the line with another tech from Comcast and he said he thinks he can see the problem.

            1 Reply Last reply Reply Quote 1
            • syko24S
              syko24
              last edited by

              Issue was corrected on Comcast's side. They did not remove the number from their switches after the number was ported. Therefore anytime a Comcast number called our number it went to a busy signal.

              1 Reply Last reply Reply Quote 1
              • scottalanmillerS
                scottalanmiller
                last edited by

                Yup. Very clearly a Comcast issue that they should have realized instantly.

                1 Reply Last reply Reply Quote 1
                • JaredBuschJ
                  JaredBusch
                  last edited by

                  It is a very common issue

                  1 Reply Last reply Reply Quote 0
                  • 1 / 1
                  • First post
                    Last post