Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mitel or Cellular Voice Mail?

Status
Not open for further replies.

MitelInMyBlood

Technical User
Apr 14, 2005
1,990
US
Anyone recall the setup scenario?
Cfwd Always from the 2K over PRI to a cellular phone, some users want the cell VM to pick up, others want the company-internal VM to pick up

I can do it with Call Rerouting 2nd alternate to internal VM on the 2K. (34.2.7.4) The user forwards his inctrument CFA to his cell and if no answer the call comes back to the in-house VM. If I turn off Call Reroute 2nd alt, then the forwarded call stays on the cell and drops into the cellular VM system.

Any reason I shouldn't be able to make this same setup work on the 3300 (9.0 UR1)?

Original MUG/NAMU Charter Member
 
No, but could you explain why 2nd alt is used instead of first. Guessing it is to do with the timer based on System option instead of COS of the set.

The same can be done with 1st alt by having COS with appropriate FWD NO ANS and Recall Timers.

If your site is Auto-Att pay particular attension to the Recall Timer. I've seen issues where the call ends up in the internal Mail instead of the Cell Mail because the call recalled before answer.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Yes, 2nd alt vs 1st, as 2nd depends on the system call rerouting timer in the systems options assignment. Also 1st reroute is too soon (11 secs) vs 21 secs. Good catch on the recall timer. Still doesn't 'splain (Lucy) why it works predictably on the 2K and not on the 3300. Puzzling. Will have to research deeper.

Original MUG/NAMU Charter Member
 
Here is an example of how recall can affect things.

I have a site with a 6510 VM operating as an auto-att.
Caller dials into system
Auto-Att Answers
Caller Dial zero
Console Answers
Console transfers to Ext
Ext is forwarded externally to cell (No other routing or forwarding)

Sometimes, the call ends up in the internal mail, sometimes in the cell mail.

The difference is the time that it takes the console to release the call. If the release is immediate and the call recalls before going to the Cell's mail ring the voicemail (First ans position of initial call) Because the call was transfered to an extension, the VM would integrate with that VM.

If the console waited a couple of seconds before releasing the call, it would drop into the cell mail.

Fixed by extending the recall timer.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Amazing what you can find on the KB: (this in bold below fixed the problem with it not working on the 3300)

Article Title
How to pull external forwarded call back to internal VM Publish Date
Oct-15-2004


Description/Symptoms
How to pull an external forwarded call back to internal voice mail


Body/Solutions
When an incoming PRI trunk call is forwarded to an external party (such as a cell phone user) and the call is not answered or is busy, you have the option of rerouting the call back to an internal PBX answer point.

To activate this feature, you'll have to:
enable the Call Reroute after CFFM to busy destination option in the set's COS, and
set up a call reroute assignment against the set


Typical programming steps for PRI trunk callers
1. Use the Call Forward feature to set up Call Forward always conditions to an external party (such as cell phones).
2. Set up Call Reroute First Alternative to an internal party (such as Voice Mail).
3. Assign the Call Reroute First Alternative Index in step 2 against the Set in Call Reroute Assignment.
4. In the COS of the set, enable Call Reroute after CFFM to busy destination.

Additional programming steps for T1 incoming callers / Internal stations

If you want to apply the same feature to the originator such the T1 incoming caller or internal extension, you must enable Suppress simulated CCM after ISDN Progress in the T1 trunk's COS or the station's COS. Without this option, T1 trunks and/or internal extensions will not be able to reroute the call back to the internal answer point once the call has been forwarded externally.


Original MUG/NAMU Charter Member
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top