One-X Attendant phonebook

[napy2]

Hello

A few months back we had our Avaya phone system upgraded to the latest version which included having One-X Attendant installed on our reception PCs.

A job was set up on the server to export all stations to a text file which then gets imported into One-X so that any changes we make on the system automatically appear on the One-X Attendant consoles. This works to an extent but for some reason we have ended up with two data sources visible in One-X, one of which receives the updates fine but the other appears to be static and never updates almost like it appeared by means of an initial import when the system was set up.

The two data sources are named "CM Stations" and "One-X Attendant". The former is the one that updates ok, the latter is the static and redundant phonebook containing out of date records.

The biggest problem is when a receptionist tries to look up a name One-X will try using the "One-X Attendant" address book as the primary source meaning a caller may end up going to the wrong person. The busy display icons also appear to get their information from the static phone book and this needs addressing.

Is there anyway to either remove the static phonebook or tell One-X Attendant to use the "CM Stations" address book to avoid this confusion?

One-X Attendant client and configuration tool version - 4.08

The examples below shows "Station, test" which is wrong and is coming from the "One-X Attendant" phonebook and "Station1, test" which has correctly updated from the system and is present in the "CM Stations" phonebook.

Hope this is an easy question but I can't find the solution in any of the Avaya documentation.

Thank you

 

[kyle555]

One-X Attendant is an absolute pig and I'm happy I don't have to deal with it anymore.

Best I can tell you off hand is to go into its settings and see if you can remove the integrated phone book that way.

I think the station export flat CSV file is actually loaded into a database and One-X Attendant is acting as a database server on localhost for the one you want to be using. Nifty when it works and you can push that out to many attendants at once. But, basically you're looking at disabling the integrated telephone book.


And back up everything. Profiles, users, everything. You don't want to program that from scratch!

 

[napy2]

Thank you for your reply.

One-X Attendant is working ok for us although I'm not the one using it (we don't get any complaints about it from our receptionists anyway).

I've had a look through the settings but can't find an option for doing anything with the phone book. I know there must be a way of doing this but for the life of me can't see how?!

As I said before it largely works in that the export from the server generates the text file (or CSV to be more specific) which then does import into the "CM Stations" address book but because the other data source is also present it's using that when doing the lookup (3rd picture) or looking at the busy display icons.

I'm not sure I want to disable the integrated phone book because as you can see the "station1, test" does correctly appear in that which I know is taken from the correct data source "CM Stations" so I presume switching it off altogether (if possible?) would kill that too. I think just disabling the "one-X Attendant" data source or removing it would resolve this but I don't know how.

 

[kyle555]

I *THINK* the one you want is called JOnAS and the ITB (integrated telephone book) is the one you want to turn off.

https://downloads.avaya.com/css/P8/documents/100081872

IIRC, JOnAS is a local database server that gets fed with a flat csv file - which your ASA is exporting regularly. Its the only mechanism to auto-update 1XA. The ITB is a manual import of a "list station" in GEDI that you right click and export from ASA as a one-off. So, turning off the ITB might helpful.

Note that you'll probably have to take the console offline, go into some admin mode, do it, close the app and reopen it. Something to that effect - its finnicky.

 

[napy2]

Yes that makes sense. I've been having a read through the documentation and can see the JOnAS references which is how the "CM Stations" ASA export then import to One-X works so that's all correct.

The integrated address book then must have had the initial import by the phone engineer when he installed it back in November last year and it's never updated since. Not sure what the point of that was as he then went ahead and configured this auto export to import job that JOnAS handles.

If there is some kind of admin mode for Attendant to switch off the ITB then I don't know how to get into this but am slightly concerned that if it does get switched off would this mess up the busy display icons as these seem to point to the out of date data source instead of "CM Stations". Our receptionists use the busy displays quite frequenctly so wouldn't want to mess these up.

Thanks

 

[kyle555]

IIRC, a login of avaya and a password of six zeroes is the default admin login for config.

 

[napy2]

The avaya password was changed but I know what this is and can login to config using it. Where am I supposed to be looking after logging into the config tool as I can only find the part about the Phonebook and Update Service which relate to the export import process and nothing about the ITB?

Thanks

 

[kyle555]

I think "Phonebook" in that context is the Integrated Phone Book and JOnAS is the thing you want to keep.

 

[napy2]

Hello

The option under "Phonebook" says "CM Stations" and this contains all the information for the export/import from what I can tell (using JOnAS) and this all works fine:

This doesn't seem to affect the ITB in anyway though. The file it generates gets picked up by One-X Config and appears in the phonebook on the console in the address book as "CM Stations" so I know that's working. The console itself just keeps referring to the "One-X Attendant" phonebook for the lookups and busy displays...

I think the station export taken from the system when it was upgraded was reimported post upgrade into the address book named "One-X Attendant" and it's remained outdated ever since. I've found the import/export option within One-X Attendant console so the engineer probably used this import to create the data source named "One-X Attendant". There's no option to delete this from the console that I can see though?

 

[kyle555]

OK. You're jogging my memory now. Ignore my previous comment!

I believe you need to login to the config utility within 1XA to disable the flat file phone book we're referring to.

 

[napy2]

Hello

That's ok I'm happy to take any suggestions right or wrong on what to check on because I still can't get this to work

Do you mean the configuration tool as per the last picture above? I don't see an option to disable the flat file phone book in here? There's nothing in the "Phonebook" section (option next to the green tick ) and the "CM Stations" section within it just has what you see in the picture above.

Or are you referring to some kind of config utility with the One-X Attendant console itself?

I can take any screenshots if that helps?

 

[kyle555]

The latter, in the One-X console itself.

I think there's a mode different than the usual mode that lets you in. Have to go in night service first, and there's some icon you click - like the place where you can move around the buttons on the key block and stuff.

 

[napy2]

Ok might be getting somewhere here.

When logging into One-X Attendant using a system admin account there is an option to delete data sets. So perhaps this is the solution? I'm at a point now where I'm thinking doing this might be the answer but am slightly weary about breaking the whole system as I can see clicking this trashing both phone books, the busy displays and everything else here if I click yes.

 

[kyle555]

Windows restore point, my friend.

Welcome the terrible world of console administration!

 

[napy2]

Just thought I'd report back to say this has been fixed and in case anyone else ever has this problem and what the solution is.

The problem was the built in address book which had an import done when the phone system was upgraded. Because the import is static and doesn't get imported via the JOnAS method the records quickly become out of date.

Simply deleting the built in address book as per the picture above removes the built in data source allowing one-x attendant to use the data source set up via automatic import. It is necessary to close the console down and reopen it (or just log out of it and back in again) to push the change through and make the busy displays change.

Many thanks to kyle555 for all the advice.

 

[kyle555]

good to hear!