Busy short code? (AA) 2

[Ludit]

Hi,
I created an new short code *60 for Auto Attendant and it goes busy when ever I try accessing by pressing *60. I have it as

*60
AAay
Auto Attendant
Line 0

My Auto Attendant is named as Day.
It seems like an simple issue that I have might overlooked.
Thanks

 

[janni78]

Forget my old post, I don't work with embedded much =)
When you create an Auto Attendant it should create the shortcode automatically and show in the Auto Attendant screen which shortcode to use to access it.

The shortcode should be for example the following

"Trying is the first step to failure..." - Homer

 

[Ludit]

I tried the "AAay" with quotations but still busy.

 

[janni78]

Does it work from Incoming Call Route?

"Trying is the first step to failure..." - Homer

 

[Telecomboy]

Your short code should work. It should be:

*60
Auto Attendant
AAay
Line group 0

If that doesn't work, I would say something else is wrong. Have you recorded the greeting under *8401? If not, then dialing *60 isn't going to work. If you have, then I would ask what release are you dealing with?

 

[Telecomboy]

Also, just verify you have not put a space between the : and Day. If there is a space it will not work.

 

[Ludit]

Janni78, It does not work with incoming call route, I changed it's destination to AAay and dial with ringing tone.

Telecomboy, Yes *8401 is recorded. There is also no space between, I also tried "AA"ay / "AA:"Day / AAay. This is the 9.0 release, this is weird cause I did this same setup and was working before.

 

[Greybeard191]

if you are accessing AA via incoming call routes on destinations tab, then a previously created embedded AA will be visible in the dropdown.

If you are trying to access via a shortcode (e.g. for testing, or for a phantom user forwarded to a SC), then the format is (assuming your AA is called Day)

*60
AutoAttendant
AAay
0

Once, I had this not work, had to delete the AA and recreate, then it worked.

GB

 

[Ludit]

Janni78, I'm still trying to figure this out. The pictures posted, will this work if lets say if I want to test out the AA such as hearing the actual AA menu.

 

[Ludit]

Greybeard191, I'm using the same exact settings. I also changed to another number such as *66 and this also gives me an immediate busy signal. Hmm..

 

[Greybeard191]

try deleting the AA and rebuilding it. Honestly.

GB

 

[budbyrd]

Try changing the name. Some versions have issues with a capital D. On that version we had to start using Open for AA names. (D is a variable in short codes) It is also an issue Avaya fixed and broke in other versions.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[Telecomboy]

The reason I asked the release is that there was a release that didn't work when naming the Auto-Attendant Day. If you named it anything else it worked.

 

[intrigrant]

WorkDay sound nice but Weekend sounds better.
Do as advised, copy the AA, rename it and try that one.
@janni78, the shorcodes you posted are for recording the greetings and I think that is not the problem here.
@Ludit, use monitor to see what happens, use a default filter, enable shortocodes and embedded VM events in the Call filter.
Shortcode must be:
SC=*60
TN="AA:WorkDay" or "AA:"02 if the AA number is 02
Action = AutoAttendant
Linegroup ID must be zero

I usually create a shorthode like *8XX/"AA:"N/AutoAttendant/0 to test AutoAttendants.

 

[janni78]

Yeah, I realized that I'm lost on embedded. Can't remember when I installed an IPO where they didn't have VM Pro.

"Trying is the first step to failure..." - Homer

 

[1043]

Change the word Day to day

 

[intrigrant]

What's wrong with WorkDay?

 

[1043]

It was an issue with 9.0

 

[Ludit]

Quick update!

@Greybeard191, Yeah I have tried deleting and rebuilding but appreciate the advice.
@ Everyone, thanks for the help, I changed to *800 and "AA:"N and that worked quite well.

 

[1043]

IPOFFICE-52338
EVM Auto Attendant name cannot start with a "D". You get [Number Busy].