one-X Attendant Console Phonebook empty. How to update?? 1

[avayatech2018]

OK Guys and Gals I'm working on our one-X Attendant console. This stuff shouldn't be this hard. I've been Googling for a couple of days and not finding any answers. How do you go about updating the Phonebook? I went into ASA and did an export of stations. So I have the file per the specs I've read and the YouTube videos I've watched. I've tried various methods to try and get it to show up in console. I've loaded a copy of console on my PC so I have a copy to play with. This all arrived from a dept that uses the console. They had a power outage the other day and I got it back to seeing it's phonebook but she said it's outdated and they have been manually modifying it. Surely we can do an export from ASA on a regular basis and do an import to console right??

40 years in Telecom. 2 months on Avaya! Go easy.

 

[kyle555]

Oh god...its ugly.

Once upon a time I'd setup a scheduled task in ASA to list station every so often and have 1xAttendant import that.

If memory serves, i didn't do a station export but a list station in GEDI and right click, export, save as csv or whatever, and that was what I imported to 1xA. Is that how you're going about it?

 

[avayatech2018]

Hey Kyle thanks for the response. I saw your name come up in my quest to find answers on console on other post.

I've tried using the configuration tool to read a csv file per the documentation I could find. That doesn't seem to work. I tried using the phonebook import within console. That fails with an error about not finding a control file?

OK as I was typing this I tried the list station and the import worked. How crazy is this. The method in manuals and on the web showed saving the file with semi colons. I just did list station and saved with default comma's.

Kudo's to you. I've been wracking my brain for 3 days! I knew it shouldn't be this hard.

Now I need to play with the Busy Field buttons and see how that works.

40 years in Telecom. 2 months on Avaya! Go easy.

 

[kyle555]

You're jogging my memory now!

I think that control file is like a csv definition that outlines what the data formatting will be - like tab delimited, and or with single or double quotes around things, etc. I think I found by accident that list station-->export from ASA and just touch nothing that somehow 1XA has a default control file to read specifically that format.

Glad I could help. Poor you!

For the BLF stuff - and make sure you backup everything to not mess stuff up - I believe as you add keys on the attendant programming in CM that you have to make the parallel programming in some admin/config mode in the console. Be careful!

 

[avayatech2018]

Well I was able to duplicate the Busy Field buttons could be overwritten on the console on my PC. Went over this morning to try and update the users console and no luck. I can do the import and it's happy but I have busy Field buttons that they manually modified in the past that are not correcting with an updated Phonebook import.

I've tried the option to delete the data field or something like that.

Kyle you know how to delete the existing Phonebook by chance?

40 years in Telecom. New to Avaya! Go easy.

 

[kyle555]

What version of one-x attendant do you have? And, have you gone over the admin guides thoroughly?

Remember, it's German engineering, not American. It's highly unintuitive.

Beyond opening the config tool, I can't remember much - I thought there might be a spot to pick a new CSV for a set export and importing it = new phone book? I dunno...

Maybe they added BLFs and the names they added at the time don't match the export you most recently took?

It's a strange animal!