DID Night Service

[ToddGivens]

We have a DID number(3100) that rings to audix auto attn. mailbox (3100) during the day. The console operator wants to push her night service key and have calls redirected to a separate night service mailbox such as 3599. I must be missing something. Can anyone out there help.

Thanks,
Todd

 

[sjforcum]

Do you have vectoring? If so, it's easy. If not, have the DID line route to a hunt group with no members. You can establish a cover path for day calls (which leads to your voice mailbox) and a night service destination. I believe you would then need to program a hunt group night service button on the console for her to activate nights on this line.

 

[ToddGivens]

Thanks for your reply. We do not have vectoring. I added a hunt group night service button to the console, but when pushed it flashes three times and goes off(like we need to do something else). Do you have any ideas?

Sorry we've never used this feature before. Thanks for your help.

Respectfully,
Todd

 

[ToddGivens]

Operator was pushing wrong key..Sorry..

Voicemail is still pulling mailbox 3100 instead of 3599. I routed night service destination to another hunt group, 3599, and then to voicemail to try to change it's identity but it is still retaining 3100. Any ideas? Please.

Thanks,
Todd

 

[sjforcum]

I just set this up in my lab and had the same results....anyone?

Here's what I found in my testing...when I used an X ported station as the night service destination (to route it to VMAIL) it stayed with the hunt group extension. When I used ATTD or a station with an assigned port, the call routed accordingly but did not follow coverage.

I tried setting up a number in the listed directory number and having the switch route to that, but the call was sent directly to the operator (I'm assuming it went there due to either the night service button not being active on the console or there was no physical station with that extension).

My curiousity has been peaked. According to the documentation I glanced at, this should work....the call should follow the night service destination's coverage path.

I'll work on it a little more when I have a minute....anyone else?

 

[mikeydidit]

A really easy way to make this happen is through time of day coverage path. Im not sure if you have that or not but it would be great if you do. Set it up so that time of day coverage path activates at whatever time and deactivates itself. I have our pateint room phones set up like this and I dont have to rely on our operators to do it, which is a plus.

 

[ToddGivens]

Thanks for all your help. We get the night service to work, but it continually wants to route to daytime mailbox of 3100. We need to lose that identity to pick another mailbox (3599).

The customer doesn't want to set a time of day because of odd work hours.

Thanks again.

-Todd

 

[t3chhelp]

Why don't you change it in the trunk group form.

 

[ToddGivens]

We can't use the trunk group form because 3100 is a DID number and we'd like the others with DID to receive their calls.

Thanks for responding.

Need Help
-Todd

 

[PBXJay]

I had a similar problem with my DID and the only way I got it to work (haven't had time to research it more) was to put in audix in the auto-att routing table, and have the daytime and night time extensions set. Then when Night service was activated on my hunt group it seemed to work.

 

[Phoneman2]

Any chance you could us the second Cover path option? Its a RTU. If you do have it you can put a set of speed dial buttons on the phone to select which cover path to us. Wisdom is Knowledge
that is Shared

Thanks All Phoneman2

 

[artieman]

1. You can not cover to a covered extension. If you use the hunt group to cover to, you can send it to a coverage point, but if that coverage point is unavailable, it will stay at the first station, ie the hunt group, or choose the second point in coverage. If you use this method, you must forward the covering station.

2. If this is a PRI, the 3rd page in the trunk group form will allow you to manipulate an single incomming entry. If this is a DID or TIE trunk, you can not delete and insert digits. Also if you use the night destination, you will route ALL incomming calls to that trunk group.

3.Vectoring will not allow you to choose day and night, but you could use attendant vectoring and input the destination for night service on the listed directory number form.

4. I would recomend routing the call to voice mail, if this is Intuity, and use the Auto Routing table to input day and night destinations. If you would like this option, email me with the specifics and I will try to help.

 

[sjforcum]

Maybe I'm not doing something correctly, but anyone have any idea why the hunt group night service does not work?

 

[PBXJay]

No. I called into Avaya and asked the same thing. They said it should have worked if there was an extension in the night service destination spot in the hunt group form and the night service button is activated. Anything more detailed and the wanted to charge me the big bucks.
I am hoping to do some more tesing in the lab today.

 

[PBXJay]

Here's what my testing showed:

If the night service extension was an x ported extension, then the call got redirected to the default operator's extension.

If the night service extension was a regular station in the carrier, the call flowed through properly to that station.

If anyone knows how to get it to work to an x ported extension without the use of the auto-attend-routing
routing-table in Audix, I'd be grateful.
-Jay

 

[avayaman]

Use the auto attendant routing table in Audix to translate it after hours. Set up a new business schedule and put 3100 in an auto attendant routing table with it pointing at mailbox 3100 during the day and 3599 at night.

 

[Bobg1]

Beddows is correct.
Make sure you setup the time of day schedule to reflect the hours you need. ( in audix)