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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Call forwardinf issue

Status
Not open for further replies.

T8keiteasy

IS-IT--Management
Nov 28, 2006
267
FR
HI,

Set A is forward to set B (thru FAC)
Set B is forward to VM.

When I call set A, I have A VM
Is there anay solution to have B VM ?

Regards
 
Just forgot to say :
Question is about forwarding stuff and not forwardinf (which doesn't mean anything of course).

I'm running Mxe 7.1.3.4
Sets are 5212

Regards
 
not really as the way most systems work is that they look at the first directory number accessed and carries this trough all transfers/forwards therefore when you ring the voicemail it detects your DN number hence why you always get VM A.

 
you could try this not sure id it would ork but worth a try

Create a Voice hunt group of *xxxx where xxxx is the users mailbox/extension number. Note: The hunt group type must be Voice and not Phantom.
Call reroute always the new hunt group to the vmail pilot number.
Once the above is completed, you can transfer the caller directly into the new *xxxx and you will hear the user's greeting.

Let me know if this does work please.
 
Thank you for the answer..
My question was just a litle bit more complicated in fact..

A, B, C and D are 5550 multicall numbers
A for internal calls
B for external calls
C for IP trunking
D for DDI numbers returning to console 5550.

When night2 I reroute calls to A VM.
A VM message will be very change very often.
I wanted to reroute B, C and D to the A VM, to save VM licence and for my customer not to change 4 VM messages...

I will check out your group solution...
I could reroute all numbers to a specfic group...but, as you, I'm not sure of the issue...

Regards
 
If you can somehow integrate a named hunt group in to the mix, it may help. When a call is rerouted from a named hunt group it will autogmagically remove the original dn and present the named hunt group dn.
We use it to interflow multiple acd paths in to ONE mailbox, this works to a tee. If we just used the vm pilot as the interflow point we'd need a mailbox for each path. Doing it with the named hunt group resolves this.

Your mileage may vary of course, but it's something to think about.
 
When I say "named" I should specify that as "Name Tag" hunt group.
 
Hi,
WHen you say a name tag, do you mean to name the hunt group in telephone directory ?
Regards
 
No!!!!! what miteltech is saying is to make the hunt group type a nametag.

 
There was a TSB from Mitel recently about using Path DN's and Interflow to VM to separate a DN into Day/Night Mailboxes.

I am confident that the same process could be used to combine several DN's into 1 Mailbox.

Create a Path with interflow to VM

Call re-reroute your LDN's to the PAth.

The Mailbox would be associated with the Path DN.

Can't guarantee this will work, but it's worth a try.

There is an island of opportunity in the middle of every difficulty.

Miss that though, and you're pretty much doomed!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top