Home Page Articles User Guides News Letter  



Author Topic: MAS Nupoint - Call Flow Blind Transfer to Hunt Group with Single Multicall Fails  (Read 3711 times)

Offline tntmart

  • New Member
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
3300 V 4.2
MAS 2.2 sp1
Nupoint 14.2.0.36.01

I have a Nupoint Call flow set up to transfer to a 3300 Hunt Group. The Hunt Group has one single Multicall line that appears one 4 phones. If I direct a DID to the hunt Group I can Camp on mutiple calls to the groups, or if I call internally I have the same result.
However if the Nupoint does the transfer and an active call is ringing, even though it is a "Blind Transfer" the Nupoint kicks the call back stating the call could not complete because the Hunt Group is busy. I have spoken to Tech support and they state that this is a known "issue".

Tech support gave me direction to Build a fake ACD group and interflow the same to the Hunt Group.

Has anyone done this, I am trying, the best result is getting the first call through, then an infinite camp on somewhere. I used both ACD express and the standard ACD group. Set the interflow to 2 sec.

Had the customer on ACD express, they were not an ACD environment proir to this install and can not and will not change. So the Hunt Group scenario is all I have left.

Any ideas would be appreciated.



Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5296
  • Country: us
  • Karma: +453/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Yep.   Seen it.
If you go to maintenance commands, locate the PLIDs of the extensions involved and type:
stat mls <plid>   (i.e. stat mls 3 1 2 1) I'll be you'll see that the key is in a busy state even though no one is on the phone.

Seen this many times where I've put multicall keys in hunt groups.

A reboot of the pbx will clear it for a while but it will happen again.

If tech support is saying that it's a known issue then that is a change.   They've always told me there was no such issue.  Given up on trying to use that as a programming technique.

Sucks, I know.

Now for the work around:  Not sure that I have one.   Can't see how an interflow from an acd path would resolve it because when it interflows, it will ring the only phone that doesn't have the key in a busy state.  If there aren't any then it will get stuck in the phantom ACD group because it won't try again once it fails to the interflow.

My suggestion would be to remove all the multicall keys.  Then set up a hunt group of 3 to 4 line "key appearance".   If these phone for any reason go into make busy then you'll have to program them as either phantom phones or analog lines and then (very important here) station forward them each to the next button up on a busy condition.   

Hopefully that helps.

Ralph
« Last Edit: April 23, 2014, 01:02:50 PM by ralph »

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5296
  • Country: us
  • Karma: +453/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
oh, and BTW:  That's why I never recommend putting multicall keys in a hunt group.

Ralph


 

Sitemap 1 2 3 4 5 6 7 8 9