Announcement

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

  • Message Waiting Indicator Repoll

    Ok, so I'm sure there's a way to force an individual phone to request the MWI status from it's respective DVM, but how?

    phonectl has got to be one of the worst documented commands (next to ipbxctl I guess.) The commands they give you in the maint guide are pretty much useless for fixing anything, only seeing that yes indeed your user's assertions are correct, it's broke.

    If someone knows the vxworks commands to get this to work (or hell a param to pass phonectl would be ideal, since we could script that in vb.)

    Because we use the phones in parallel rebooting them to repoll the MWI is not an option during the day, and it's happening semi frequently.

    (We're running one of the early builds of 8.0 and I can't wait till we upgrade till 8.1...)

  • #2
    8.1 is GA 13.24.5910.0, but don't think that will give you better documentation.

    Comment


    • #3
      Originally posted by jstewart View Post
      8.1 is GA 13.24.5910.0, but don't think that will give you better documentation.
      Not really, but I appreciate someone responding. Truly the issue seems like an easy one, and I'm frustrated that shoretel is behind Cisco in this one.

      It resolves itself over time, but the worst case (phone doesn't blink, and there are voicemail's waiting) is the one that will cause a salesperson to lose money, or a call center rep to miss a callback etc.

      Comment


      • #4
        Message Waiting Indicator Repoll

        try using the cfg utility on the DVM -
        the cfg.exe is located \shoreline communications\shoreware remoteserver directory

        >cfg

        to synchronize the MWI with all the phones, run

        >symwi

        let me know if that works

        Brian

        Comment


        • #5
          I'll let you know as soon as it happens again, we're going to do the 8.1 GA install this Thursday (if all goes according to plan) so hopefully we don't see this issue again but you never know.

          Comment

          Working...
          X