|
Joined: Mar 2014
Posts: 160
Member
|
Member
Joined: Mar 2014
Posts: 160 |
yes, the manual says "The number should exist in 11-02, 11-04, 11-06, 11-07 and 11-08." in 22-07 DIL assignment, that's why you can't put a ACD pilot number here.
the question is we can't put ACD pilot number in DID translation table, the only way is put Ring group pilot in 22-11.
you could transfer a call to an ACD pilot number, but you can't call it directly! I don't know why?
another "system design limitation"?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Mar 2014
Posts: 160
Member
|
Member
Joined: Mar 2014
Posts: 160 |
Yes, I set loopback (for DID) and use the DID routing tables. The procedure is like this, call 288--> loopback to trunk 5 (DID) -->translation table 88 is blank, translation 101: received number= 88, target number= 395(ACD pilot number). It doesn't work at all. If I put an IRG number (associated with ACD group in 41-03)in transfer target 1, it will go to ACD group.
|
|
|
|
Joined: Sep 2004
Posts: 4,220 Likes: 2
Member
|
Member
Joined: Sep 2004
Posts: 4,220 Likes: 2 |
I dunno about system limitation, but I have hundreds out there with SIP and PRI that have no issues. I have never used a loopback to simulate the DID going into an ACD. I have no idea why you would even use a loopback in this case What is the application that would require a digital loopback or are you simply trying to do something?
|
|
|
|
Joined: Apr 2005
Posts: 2,526 Likes: 4
Member
|
Member
Joined: Apr 2005
Posts: 2,526 Likes: 4 |
crazyfrog
If I'm reading this right you are not able to point DID numbers to ACD pilot numbers, if this is the case something is wrong somewhere in your settings.We have DID numbers pointed to ACD pilot numbers with no issues.
We get old too soon, smart too late
|
|
|
|
Joined: Jul 2005
Posts: 1,336
Member
|
Member
Joined: Jul 2005
Posts: 1,336 |
Yep thanx. The Loopback DID works fine..
Regards,
Paul W Now back to a 0 day week. Love these 7 day weekends.
|
|
|
|
Joined: Mar 2014
Posts: 160
Member
|
Member
Joined: Mar 2014
Posts: 160 |
It's a demo system, a toy for us. So there is no trunks coming in.
|
|
|
|
Joined: Mar 2014
Posts: 160
Member
|
Member
Joined: Mar 2014
Posts: 160 |
Hi dans, I think if we put ACD pilot number into DID table as a target number, it should work. But it doesn't. And I asked my colleagues, they said no, but they also don't know why.
main setup as below: 41-01-02 Login ID code: 0= no login ID 22-02 trunk type: DID *41-02 extension to ACD group: ACD group 32 *11-17 ACD pilot: ACD group 32 = XXX *22-11-02 target number: ACD pilot??? *15-07 function keys: *10 = ACD login/logout, *13= ACD off-duty mode ^22-04 extension to IRG: IRG 32/33 (day/night) ^41-03 IRG to ACD group: ACD group 32 ^22-11-05 transfer target 1: IRG 32/33 (day/night) ......
|
|
|
|
Joined: Sep 2007
Posts: 54
Member
|
Member
Joined: Sep 2007
Posts: 54 |
Not sure why you are having this problem. i have set acd pilot in DID table and and also used loopback trunks(set as normal) to ring the ACD internal. also using the IRG to ACD setting.
Did someone already suggest if you have the licence in?
|
|
|
Forums84
Topics94,518
Posts639,974
Members49,849
|
Most Online5,661 May 23rd, 2018
|
|
1 members (newtecky),
238
guests, and
55
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|