Zero Out Again

[h382]

Kudos to KenMeans for helping me on my previous Zero Out issue..

Our MM is connected via H.323 trunk to S8300. Right now, we have Zero out going to a VDN. When no one answers that call, it covers back to MM, but says "That person does not answer....... blah blah you know the story." what would cause this?

 

[KenMeans]

So is it picking up with the mailbox that it was 0 out came from? or to a new one.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[h382]

We have a vdn 4190 which points to a vector that validates the time of day and available agents it then rings Group 4170 which has skill number 1. The call will successfully ring the group however, if there isn't an availble agent the hunt group by default is supposed to ring the 4104 support mailbox. When a user zeros out of a mailbox and doesn't get an availble agent instead of it ringing 4104 it says "That extension is not valid press 3 to disconnect".

Any Thoughts?

 

[KenMeans]

Well I can see what is happening. The H.323 is supervised transfer only and when it transfers the call it never lets it go. So on a no answer it pulls it back to the mailbox that it came from. You can;t do a blind transfer using H.323.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[h382]

Is there anyway we can have it ring a group of people until it is answered by someone. No matter what extension or VDN we put into the "Receptionist" extension for Zero Out, it always comes back and says There is no one available to take your call.

 

[KenMeans]

So does it ring the phone or just comeback right away and say no one is available?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[h382]

Right now we have zero out ringing a hunt group. It won't cover to someone else in the hunt group.. It picks the most idle, but if that person doesn't answer, it just says this extension does not answer, press 2 to leave a message. It won't cover to another person or to a voicemail.

 

[KenMeans]

And that is the way it will work with the H.323 on a supervised transfer. it will ring the phone for so many rings and pull it back. I do not know of anyway to change the number of rings befor it pulls it back.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[h382]

Maybe I'm missing it, but if it's pulling it back, why doesn't it just go back to the original mailbox, instead of saying that it cannot answer.

 

[KenMeans]

Well you are right. What do you have set in the transfer type for the PBX?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[h382]

Transfer type is set to Full.

 

[KenMeans]

This may be it.

H.323 integration (QSIG Protocol) does not support
forwarding/transfer from a Vector. Currently, if calls are routed from a
Vector to the QSIG link(s) connected to the MAS, the call will not pass the
VDN as the called party ID. Applications requiring calls that are routed
from Vectors to mailboxes on the MAS can be configured so as to route
calls to phantom extensions (X-ports) configured to call-cover all-calls to
the MAS hunt group.
Note: Patch 7960 corrects this. Avaya CM 2.0.1 and later releases
include this fix/patch.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)