Possible MCD bug

[RDECIT]

We have a system that was on the last version of MCD, the business hours worked fine until we had to upgrade it to the lastest build. Now the business hours dont work.

We have had to use programmed schedule (which isn't flexible enough) to get round the problem for now.

Anybody else experienced this with the latest MCD.

 

[Mitelmatt]

Rob

Depends what you;re trying to use business hours for? Business hours is only for voicemail and changes the greeting from open to closed greeting. It doesn;t control night service

programmed service changes the mode of the system from day to night 1 or 2

Full scheduled night service is in 4.1 out towards end of year

 

[RDECIT]

Matt, I just want the system to send their main line pilot number to voicemail after the close of business. However call flow continues regardless of the time, unless I program night service.

 

[Mitelpassion]

call routing is NOT affected by business hours.
Night service will initiate the alternate call routings if programmed.

essentially the business hours is merely to indicate when the day or night greetings are played if you had an auto attendant configured. (as per Mitelmatt)

what you're trying to achieve can only be done by switching to night service or dialling some sort of code to initiate the call forward/call flow rule. there are some dependencies here.

the system does cater for auto day and night service but this too is limited. I'll explain if you need more info

 

[northportphoneguy]

Hi, I had a similar situation here. With multiple departmens and all of them wanting different routing at different times, even the OPSMGR switching in and out of Day Service was not flexible enough. So I went back to my DOS days and edited a batch file which dials out the various CFWD and CANCEL codes on a modem. Made some Windows Schedules and it works like a charm. Need to leave the PC on through.

 

[Mitelpassion]

interesting. how'd you get a batch file to do this?

 

[northportphoneguy]

Hi,
I edited my batch down to it's simplest, but you could add rem(remark) cls(clearscreen) echo on, echo off and the @ sign to dress it up. I cycle 10 call forwards in a single batch. I also have a batch which then cancels cfwd with the appropriate feature access code. Batch files are then run using windows scheduler. Hope this helps.

mode com1: baud=9600 parity=e data=8 stop=1 dtr=off rts=off
atdt**1583971105>com1
sleep 6
ath>com1
sleep 4
atdt**1588001105>com1
sleep 6
ath>com1


Here is the detailed explanation.
Use google and locate sleep.exe(a 124kb file). I put it in the root directory. It is a tiny program which causes a batch file to pause for a timed period. Needed to pause the batch while the modem dials out because there is no relevant command in the DOS set.

I use the mode command to set my com1 port where the modem is attached to.
mode com1: baud=9600 parity=e data=8 stop=1 dtr=off rts=off

atdt**1583971105>com1 broken down is:
atdt - is the modem command for dial tone
**1583971105 - **15(my feature access code for remote call forward) + from ext 8397 to ext 1105
>com1 - redirect this command to the modem com1 port

sleep 6 - pause the batch command 6 seconds while the above dials out

ath>com1 - modem command to hang-up (go on hook)redirected to com1 port

sleep 4 - pause batch command 4 seconds while the above dials.

(repeat next cycle which in this case is for 8800 to go to 1105)

 

[Mitelmatt]

I've also created a batch file and used windows sheduled services to automatically put system into night service. Works ok.

Pretty much all that OPS man does when setting that to schedule night service

 

[kwbMitel]

Article ID #
05-5162-00064

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

Ignore Above, that was for a different post.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.