BCM Centralized Vmail and Feature Codes

[stik62]

I have a BCM 400 at corperate site with Vmail and a remote BCM 50. MCDN keys are installed and routes are configured. I can access the Vmail on the 400 from the 50 by dialing the Vmail DN directly but i can not use any Vmail feature codes on the remote 50. What settings am i missing?

 

[Deweyhumbolt]

You can't use any feature codes. All you can do is access Vmail through DTMF and it will send MWI.

Adversity is Opportunity

 

[stik62]

That is what i thought. Just needed some conformation. Thanks

 

[hawks]

Is there anyway to use *9xx from the remote side?

 

[acewarlock]

New Question, Start New Thread.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[hawks]

ace I meant this as a possible answer to the question. Because if you use remote access from a trunk you can use certain Features of the system but instead of doing Fxxx you would use the *xxx.

 

[Deweyhumbolt]

Sorry hawks. Remote access allows you to use DTMF to access certain features. Vmail feature codes do not use DTMF.

Adversity is Opportunity

 

[hawks]

thanks dewey, I found this in the MICS 7.0 Installer Guide page 122. OI have not tried it though.

As well, instead of using F (feature) to access feature codes, users use the • button (*981), just as they would if they were dialing into their own system from a remote location.

 

[Deweyhumbolt]

Awesome hawks, keep me posted if it works. Will it work over VoIP, or just a P2P?

Adversity is Opportunity

 

[stik62]

I have attempted the *9xx going across the VoIP trunks from the 50 (remote system with the IP and dial plan route built) to the 400 (host) using a target line on the 400 to emulate an external call. But the 50 is not allowing me to start the dial with a * "invalid number".