Voice Mail Interrupt "Not Allowed" 2

[jasidija]

Got a Release 2 BCM50 with CallPilot voice mail. Got a line configured to ring to DN 385. Rings fine, then goes to voice mail. When I use the programmed feature key for VMail Interrupt - or even when I use <Feature 987>, the call stays in voice mail and on the display (of the i2004 phone), it says 'not allowed'.

I've used element manager to make sure Priority Call is enabled.

I've searched in the CallPilot Admin guide and the CallPilot Reference Guide, but all I can find is how to use the feature - like it's supposed to auto-magically work.

Is there any special config or restrictions I should be considering?
Thank you.
P.S. Merry Christmas ;-)

 

[cook1082]

I think that for it to work you need CLID and the phone has to alert that a call is in the mailbox of that phone then interup can be done.

 

[DBrewsky]

If you program a button with F987, and someone is leaving a message, does that new button flash? If so, thats the time to use the feature. Also, make sure you use COS 1 is the voice mailbox as it allows this feature.


--DB

 

[jasidija]

DRewsky - the button never flashes (I was thinking it should, but it doesn't). As far as COS - I'm using a mailbox that is assigned with COS 1. There are multiple features within the COS that I can change - is there a specific feature?

cook1082 - I've got CLID working, but still no dice.

(I hate it when I can't find the needle in the haystack!!!)

Thanks for your help.

 

[Dasheen]

r u sure the button is programmed as F987?

 

[jasidija]

yep!

 

[DBrewsky]

ok, try this..

call the extension internally and let it go to voicemail and see if you can do F987 then. If not, use F980 and try to leave a message then activate F987.

 

[jasidija]

I'm beginning to think I'm missing something fundamental in the programming.
When I call Ext 385, it just rings - doesn't go to voicemail. When I use Feature 980 and tell it to go to mailbox 385, it does. However, the Voicemail Interrupt button does not flash - and whether I push it or try to manually use Feature 987, it still says 'Not allowed'.

I'll be back on site tonight - I think I need to review how I have that extension setup to go to voicemail. Right now, callers hit CallPilot's auto-attendant and get dumped into that Ext if they don't select anything else. It rings 6 times there and then goes to voicemail. Which seems to work - it lights the lamp and I can retrieve messages... But I must be missing something else. Seems odd that an external caller would get routed to voicemail after 6 rings, but an internal caller never goes to voicemail. Maybe that's part of it, or maybe that's another issue! LOL! I'll check it later tonight.

Thanks for the feedback!

 

[snowman50]

The Auto Attn is activated to answer the line after 6 rings if the call is not answered.
The AA then tries to send the call to to the nominated Attentant and if this is not available it goes to the General delivery mailbox.

To make the internal call go to a mailbox you have to set call forward no answer on the extension capabilites to go to the Mailbox DN (DN can be found by pressing Feature 985). then set the ring delay to say 4 rings.

Now when a call rings this extension the call will go to the mailbox after 4 rings if not answered.

If a call goes into the mailbox it can be retrived by pressing f987.
This only works when the caller is still active while leaving a message in the mailbox.
If the caller hangs up then there is nothing to retrive

Hope this sheds some light on what you are doing .!!!!!

 

[Dasheen]

setting the cfwd na should fix your problem.

 

[jasidija]

Thanks snowman50 & Dasheen!!!

That did it!

So, if I understand what I did - I changed the auto-attendant's Answer Mode for that trunk - from 'Auto-attendant' to 'None'.

Now the auto-attendant does not pick up the line and send the call to a table - which was putting the call in the mailbox of Ext 385 (I'm still not sure why this wouldn't work - I would think it wouldn't matter how the call is getting into the mailbox; if a voicemail was being left in the box for 385, Ext 385 should be able to interrupt it).

Anyway - here's a tip - this kinda threw me for a loop:
I've been using Element Manager to try to program this via the web interface. Guess what - in the version I'm using, there is no option to forward calls in the programming under the set's Capabilities. so... I had to go in via Telset Administration! There it was, clear as day.

Now, I assume I am using the LINE programming and setting the "Prime Set" - to Ext 385. That's why the line now rings in and eventually gets into the mailbox of Ext 385, Right?

Odd puzzle on that: When I set the Call Forward No Answer to 6 rings - I get sent to a different mailbox (somewhere other than Ext 385), and the Voice Mail Interrupt feature is 'not allowed'.
BUT, when I set it to 4 rings, it works perfectly.

So, that's where I'm leaving it for now:
No auto-attendant, and Call Forwarding with No Answer enabled, set to answer at 4 rings, with the 'forward to #' defined as the Mailbox DN.

If anybody can explain why you can't interrupt a voicemail when it is transferred from the auto-attendant...
And why forwarding after 6 rings gets a different result than after 4 rings...

I'd be interested!

But in the meantime - it's working. Thanks again snowman 50!

 

[DBrewsky]

Using Element Manager in the BCM50/450, the Call Forward options are on one of the columns of the main settings page for the extension (this is where you will also see the tab for Line Assignment).

Check it out.. You will find it..

 

[jasidija]

Sunuvabeach! I can't believe it was right in front of me! Seriously - I almost don't believe it was there - I swear I looked so hard for it! In fact, I started thinking, since Ext 385 was the only phone programmed to forward - that maybe by using the Telset Admin, I 'unlocked' those columns. LOL! But I think it's probably been there the whole time. (I did go so far as to remove the forwarding in Telset Admin, so no phones were forwarding, and go in and check Element Manager to see if the columns were still there... yup, still there.)
Thanks DBrewsky - star for you! I think I'd better hire some younger eyes. ;-)
Cheers ~