Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Missed calls showing on phone?

    I have several people here saying their phones are displaying a number of missed calls when they either receive or make a call and the call is ended. No calls are missed, but some show 3 missed calls, some show 6 missed calls, some show 2 missed calls and it seems to be happening alot.

    Anyone have any idea's?

  • #2
    This sounds like the user is likely part of a hunt group where all phones ring simulaneously. If a hunt group rings all phones and it gets answered, all phones that rang on that call show the call as missed despite the fact that another user answered the call.

    Comment


    • #3
      Originally posted by [email protected] View Post
      This sounds like the user is likely part of a hunt group where all phones ring simulaneously. If a hunt group rings all phones and it gets answered, all phones that rang on that call show the call as missed despite the fact that another user answered the call.
      Hunt Group or Work group, BCA or Monitored

      Comment


      • #4
        Not a hunt group issue & we don't use workgroups. Not monitored & not sure what BCA is. This just seemed to of started within the last couple of days and as the admin of the system, I know nothing has been changed.

        Any other idea's?

        Comment


        • #5
          What SG switches are you using? If you have multiple, are you using IP Phone Failover?

          Comment


          • #6
            Also... What build are you on?

            Comment


            • #7
              Originally posted by cburgy View Post
              Also... What build are you on?


              Very important,

              Just FYI to everyone, When describing an issue, it is important to list the Call Flow Scenario or if applicable along with the most important ST Build aka 11.13.1110.0

              What Windows OS aka Server 2003, What SP level
              if possible list any commonalities like Only one person reporting, the PC is on Vista Home and so on.

              Its tough to explain, but the more information given the best answer is possible.

              Make sure your PCM is at the same level as the ShoreTel HQ.

              Comment


              • #8
                This used to happen to me as a user. A reboot of the phone from the handset didn't resolve. Sometimes, the guys did what they called a "hard reboot" of the phone. It was something they did in Director - maybe one of you genius engineer types know what I'm referring to. I do recall another time that that didn't work either & a switch reboot cleared it. More often, it was whatever that "hard reboot" was that solved the problem for our system & other customers systems.

                Comment


                • #9
                  We have this pop up every 3-4 months on phones connected to one of our SG-120s. A reboot of the switch after hours clears it up.

                  We're on 12.5.9303 btw.

                  Comment


                  • #10
                    We're on 12.14.1806.0, and this started happening to us today. We have three SG-120's. If there aren't any solutions, I guess I'll have to reboot our switches after hours tonight.

                    Comment


                    • #11
                      this happens to us all the time because we use our phone system to page. anytime someone pages every phone in the building, it shows up as a missed call.

                      just throwing that out there in case you all are doing the same thing.

                      Comment


                      • #12
                        I have a customer that has experienced this issue for a VERY long time. They will receive these missed calls, now known as Phantom calls. They will receive them when they are on the phone, or even when the phone is idle. But here is the real kicker, when they scroll through these phantom missed calls, the date and times are incorrect. I mean like 45 days previous incorrect.

                        Comment

                        Working...
                        X