Attendant

[btrain08]

I would appreciate a lesson on attendants, night service etc..

Main issue: 0 in dialplan is setup as attd. Works fine during the day and rings to attendant consoles. When night service is activated 0 gets a wave off. Trace shows some xxxx not assigned. Somehow the call is going to some extension and I have no idea how. Question.. where is that set as to what happens to calls when night service is on? Where is night service defined?

I didn't know how to fix this so I thought putting an entry in udp for 0 with length of 1, delete 1 and then insert 4 digits of an extension, which I wanted to then control. UDP wouldn't allow that entry and gave message stating: 'Len may be 1 or 2 only when inserted digits contain an Lx value'. What in the world does that mean??

So since my above trick didn't want to work I then targeted this extension from the above that says was invalid. That extension was in udp/aar going to some IP trunk to my int'l offices. I made a specific entry for that as an extension to keep it local. I tried using coverage paths and nothing worked. Dialing 0 would still get wave off. I then forwarded this extension to my VM number and that worked. Tried then to forward it to my main reception number and that didn't work. I then forwarded it out over the PSTN to the full number of main reception and that worked.

Please.. any explanation would help

 

[AvayaTier3]

Dial 0 calls when system is in system night service go to the Night Destination below:

# for non-tenant partition switch

change listed-directory-numbers                                 Page   1 of   2
                         LISTED DIRECTORY NUMBERS

                          [b][COLOR=red]Night Destination: 2999[/color][/b]

        Ext     Name                      TN
   1: 2100     Main Number                 1
   2: 3000     new test                    1
--------------------------------------------------------------------------------
# for tenant partition switch

change tenant 1                                                 Page   1 of   2

                               TENANT 1

           Tenant Description:

              Attendant Group: 1

        Ext Alert Port (TAAS):

            [b][COLOR=red]Night Destination: 2999[/color][/b]

                 Music Source: 1

      Attendant Vectoring VDN:

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[AvayaTier3]

If a console type night-only exists, the calls will go to the night-only console

dial zero calls will follow night station service if there is no night-only
console and the following programming is done.

display console-parameters                                      Page   1 of   4
                              CONSOLE PARAMETERS

         Attendant Group Name: OPERATOR

DID-LDN Only to LDN Night Ext? n

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[btrain08]

Ok that makes more sense. My trace that showed 'invalid extension' was the extension in the listed directory number table as the night service destination number. Is that 'night service destination' number supposed to be an created as a normal extension in the switch? Mine is, but it will not follow any coverage path or anything. It only works when that number is forwarded.

Also, my directory number table has no entries in it other than the night service destination. Is that ok?

 

[AvayaTier3]

Night Service Destination should be a working number in your switch. Yes, calls will not follow coverage for that extension.
Yes, it's okay not to have other entries on the form.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[btrain08]

So then what should that extension in the 'night service destination' be doing? Basically.. during the day when night service is not on the calls to 0 ring to the attd's. If they don't answer the call routes to a caller app where the caller can use the dial by name directory.. etc.. When night-service is turned on I want that same behavior, but right away and not waiting for 5 rings. Right now I call-fwd'd the night service destination number to the main number that routes to the attd's. Are there any other workarounds with this being that coverage doesn't work?

Also, I was just as curious with what I tried to do with 0 in the udp table. Were you able to see my original post with that?

Thanks for your help.

 

[AvayaTier3]

This is your switch. I am afraid I cannot answer that one.

Normally it would be programmed to go to vdn, hunt-group, station that has a live body to answer it, or an Auto-Attendant.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com