Jump to content

Mike Wayne

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by Mike Wayne

  1. Serious problem with voicemail on 3.2.0.3143 Debian 4.0: User calls in, gets transferred through the autoattendant to a hunt group which properly rings the extensions in this group. If, however, the call is not answered, it gets delivered to a final stage extension. The caller hears the prompt and leaves a message and the call shows up in the status, viewing it from the web page. Email gets generated on all voicemail & dropped calls. No attachment is to be sent in the email, it is notification only. The message is to be left in the mailbox. BUT, the email claims that the message is 0 seconds long, even with 60+ second test messages. The caller-id is correct. One thing that seemed to help was changing the mailbox settings: ---Disable, Save, Enable, Save ---Change to send attachments, Save, Do not send attachments, Save After trying this on one extension and seeing it work, we tried a second. The second then worked, the first stopped. We are about to upgrade to 3.3.0.3152 to see if there is an improvement but wanted to note the issue in the forums as well.
  2. From where? http://pbxnsip.com/software shows 3.2.0.3143 as latest version.
  3. Today, a user had the "stuck" MWI issue. She had saved a message but did not delete one so the MWI sticks on, occasionally. No messages existed in any group she was in. *99 did not clear it. So I sent her a test voicemail, instructing her to delete it as this has cleared stuck MWI in the past. As soon as I sent the message, the MWI cleared (good but unexpected). Email was generated about the voicemail I left (good). However the email states that the message length was 0 seconds (bad) and no voicemail was available (very bad). This is not an easy thing for me to duplicate as MWI sticks only rarely. Running 3.2.0.3143.
  4. More info. 5522 works fine with "Allow Access for Extensions" blank. 5511 always fails with a busy signal. Placing extensions in "Allow Access for Extensions" makes no difference. There are no extensions that begin with 8 and 8 is the "Mailbox Direct Dial Prefix". 8551 gives a fast busy, never permitting me to even enter the fourth digit of the extension number. To reiterate, both work fine when calling from outside.
  5. I've created a fairly simple setup and it's almost working correctly but I'm having one problem that I can't seem to get around. I've got a couple of extensions that function as group mailboxes, not attached to any devices. They both work fine when transversing the call tree and I can log into both of them when calling in from an outside line but one of them always gives a busy signal immediately when called from a phone that is inside the PBX. I've tried to delete and recreate it as well as giving it a new extension number with no success. Both extensions have (different) passwords and PINs and seem to be configured the same but the one continues to never work. What am I missing?
×
×
  • Create New...