My previous job site is now a customer and they have a request. They are bringing in 200 new DIDs that they want assigned to 200 stations on the production floor (each station will have its own unique DID). They would like each DID to have VM capabilities. The system is a Opt 81C with MAX and no VM and an 11C with MerMail 12,connected by TIE lines (located in the same data center). I have already verified I can pass calls accross to the 11C and leave VMs. The 200 phones are agent phones with a Pos IDs on key 00 and a DN on 03. I can see two options.
1) Point the DIDs to the phones either by programmed DNs or an IDC table. Calls can be forwarded and hunted across to the 11C with no issues. However, the customer would like to generate reports (Avg length of call, etc) through MAX. The best I can do with this solution is to have the agent log into a dummy ACDDN, take calls and we can see DN activation reports and total time logged into the queue.
2) I originally tried created 200 ACDDNs. To satisfy the CFW and HUNT issues, I had NCFW set to dial the ACOD for the TIE line plus an ACDDN built on the 11C that was NCF to VM. But to satisfy the Call Forward when Busy, I set the OVTH to 0 and discovered I could only OVDN to an ACDDN. So I planned on creating another 200 ACDDNs that were NCFW to the 11C VM - and ran into the 240 ACDDN limitation. Crap.
SO.....
I can use solution 1 and have limited reports or use soluion 2 and not have Call Forward when busy. Solution 1 may be my best choice unless I can find another way to use OVDN. Any other solutions or ideas?
Yes, the obvious solution is to sell the customer Call Pilot for the 81C, but can I engineer around the issue for now?
1) Point the DIDs to the phones either by programmed DNs or an IDC table. Calls can be forwarded and hunted across to the 11C with no issues. However, the customer would like to generate reports (Avg length of call, etc) through MAX. The best I can do with this solution is to have the agent log into a dummy ACDDN, take calls and we can see DN activation reports and total time logged into the queue.
2) I originally tried created 200 ACDDNs. To satisfy the CFW and HUNT issues, I had NCFW set to dial the ACOD for the TIE line plus an ACDDN built on the 11C that was NCF to VM. But to satisfy the Call Forward when Busy, I set the OVTH to 0 and discovered I could only OVDN to an ACDDN. So I planned on creating another 200 ACDDNs that were NCFW to the 11C VM - and ran into the 240 ACDDN limitation. Crap.
SO.....
I can use solution 1 and have limited reports or use soluion 2 and not have Call Forward when busy. Solution 1 may be my best choice unless I can find another way to use OVDN. Any other solutions or ideas?
Yes, the obvious solution is to sell the customer Call Pilot for the 81C, but can I engineer around the issue for now?