1) Customer has a CM 6 system with multiple tenants.
2) The main number terminates to a hunt group with zero (0) members and a coverage path that has two (2) coverage points: 1) attd and 2) an auto-attendant VDN. The Hunt-Group has a night service button but it is not used.
When attd 1 presses the "night-serv" button all calls goto the VDN as expected. When Attd 1 opens in the morning and turns off "night service," calls are still routed to the VDN until a manual "disable night-service trunk-group X" is issued via ASA (trunk-group X being the ISDN-PRI DID local trunk group). "status att 1" shows the attendant has released night service (in service/idle). When I status incoming calls, it simply shows them going to the VDN but does not indicate why.
Any ideas?
regs,
.al.
regs,
.al.
Avaya Certified Expert
2) The main number terminates to a hunt group with zero (0) members and a coverage path that has two (2) coverage points: 1) attd and 2) an auto-attendant VDN. The Hunt-Group has a night service button but it is not used.
When attd 1 presses the "night-serv" button all calls goto the VDN as expected. When Attd 1 opens in the morning and turns off "night service," calls are still routed to the VDN until a manual "disable night-service trunk-group X" is issued via ASA (trunk-group X being the ISDN-PRI DID local trunk group). "status att 1" shows the attendant has released night service (in service/idle). When I status incoming calls, it simply shows them going to the VDN but does not indicate why.
Any ideas?
regs,
.al.
regs,
.al.
Avaya Certified Expert