Hunt Group Zero out, but return to original VM 3

[driven0]

Hello all;

I'm reaching out to see if anyone has come across something similar.

I currently have the zero out set to go to reception. If the receptionist doesn't answer is there a way to return the call to the original voicemail.

Trying different variables, but nothing seems to be sticking, any help on this would be greatly appreciated.

in a nutshell:
Call comes in to User A ---> Customer Zero's out to receptionist --> If receptionist doesn't answer return call to originally dialed VM (User A)

Thanks!

 

[driven0]

Let me rephrase my title, doesn't need to be a huntgroup zero out, this is more-so user zero out not huntgroup. Sorry about that.

 

[driven0]

Someone brought this up to me. I am aware I can do this individually for each user and make it work, but 400 people might take a while. I'm looking for an easier solution.

 

[intrigrant]

Don't transfer to the reception, transfer to a shortcode which points to the reception.
SC = *99
TN = Reception number
Action = Dial Extension
LineID = 0

That will keep the call ringing on the reception ( at least it used to do but Avaya does make "hidden" features at will )

 

[driven0]

I gave that a try and the call went to the 'receptionist' voicemail. Any other ways to force it to go to the originally dialed VM?

Thanks for your input.

 

[AACon]

Shortcode *97N/Voicemail Collect/"LeaveVM",N

Set zero out of user to *97 and their extension. So user 2500 would be *972500
Create VMPRO Module called LeaveVM
Make menu with ???? only.
Send to generic action to copy $KEY to $CP0
Send that to an assisted transfer that points to reception.
Make busy/no answer go to leave mail for $CP0

Worked in my test. May have faults some where. Could also be a better way to do it somewhere.

-Austin
ACE: Implement IP Office

 

[driven0]

Hello AACon

Created the flow as you mentioned and here's where it's stuck:
In manager created the suggested shortcode above and put correct shortcode+extension in correct place in vm tab.

Created menu with ????? (we have 5 digit extensions) to generic action where I set CPxx value of $KEY to $CP0 Sent to assisted transfer with the destination of reception and make busy/no answer to go leave mail and $CP0

I watched the flow in SSA and it gets stuck at Mailbox LeaveVM in the destination end party. I'm not sure where I went wrong and any help/suggestions is appreciated.

I really do appreciate you taking the time to post the flow you created on this, Thank you for that.

 

[AACon]

What is your vm answer time for your reception group? What is the no answer time in the assisted transfer? Make the no answer time less than the voicemail answer time, or just disable voicemail on the group all together, if possible.

-Austin
ACE: Implement IP Office

 

[driven0]

I turned the VM off on the reception group. Changed no answer time in assisted transfer to 10 seconds (for testing). So - VM off transfer time 10 seconds, but it still hangs at Mailbox LeaveVM in the destination end party

It's like it's not pushing through the Digits (N)

Just an fyi I'm using a test environment using 8.1.73

 

[AACon]

what does your shortcode look like, exactly.

-Austin
ACE: Implement IP Office

 

[driven0]

This is Copy - Pasted
*97N
Voicemail Collect
"LeaveVM",N
Line Group ID 0

In the user voicemail DTMF Breakout:
*9755555 (extension 55555)

Here's a pic of VM pro

 

[AACon]

If you call the group in your assisted transfer directly, does it go direct to vm? try turning queueing on. Granted, you may not want queueing enabled on reception, you could create a secondary reception group just for this purpose.

-Austin
ACE: Implement IP Office

 

[smokinjoe2938]

maybe stop and restart on voicemail pro service.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[amriddle01]

Just use the $Target variable, that holds the original target of the call and can be used to route it to the correct mailbox

$TARGET
For calls sent by the IP Office to a mailbox, this variable contains the original target of a call, that is, the original target user or hunt group.

 

[driven0]

@AACon
No, it rings and it's set for the default 15 seconds before VM. Assisted transfer timeout/no answer is 10 seconds. I tried putting queuing on to no avail.

I also just tested in a different environment with no luck. There has to be some small detail I'm missing here - esp if you were able to make it work in your testing.

@smokinjoe2938 - Restarted vmpro service, but didn't make any difference.

I appreciate you guys donating your time to help me out on this.

 

[amriddle01]

Did you see my post?

 

[driven0]

Hello amriddle01 - great idea on that..

Just one question, is the "LeaveVM",N do I need to remove the ,N and in the DTMF just put *97 or keep it *97(Extension)

Also, by changing that, I need to modify the vmpro so... start --> generic $TARGET as $CP0 assisted transfer with timeout/no answer to $CP0 destination.

Does that look right?

 

[AACon]

I forgot all about the $TARGET var...that would work much better.

-Austin
ACE: Implement IP Office

 

[driven0]

Does everything else remain the same? Just change $KEY with $TARGET ? - Sorry never used this variable before.

 

[driven0]

Alright, update on what I've done.

Tried every combination I could think of, but the problem I run into is the $TARGET doesn't seem to save the original extension.

I ran the debug and I set $TARGET as $CP0 but run into the issue of Substitute ($CP0) -> () or Substitute ($TARGET) -> ()

Once it passes through the users "Leave" by zeroing out it seems to lose the variable when it reaches the LeaveVM module, and shows blank like above.