invalid button assignments 2

[Z-man]

As some of you may know, Colorado was hit hard by some fires that destroyed homes and businesses. One of my customers was affected to the point that they can't really get access to their office until next week. Call this site B.

they are part of a SCN. They have another office that some of the users are going to go to for a few days. Call this site A.

When users from Site B try to login to their own extensions at Site A, it comes up with "invalid button assignment" on the phone once it is logged in. Both sites are 9.1.

Any thoughts?

 

[TouchToneTommy]

Your buttons are being assigned via User Rights. You need to have the same User Rights at both locations, so when the phones failover, it can populate the buttons.

Create a User Right at Site A with the same name as the assigned User Right at Site B. Add the buttons, and you can also have the shortcodes in the new User Right point to local resources (Like if they dial 9N at Site B it goes to ARS 53, but at Site A maybe the equivalent 9N should go to ARS 52)

 

[Z-man]

Tommy,

site B is online, they just can't occupy the office for a few days. But the system is up and running and everything. Should they not be able to just do a login across the scn and be fine? obviously, that is not working now...

 

[TomMills]

They will be able to login, but as TTT say's, the invalid button assignment error you see is because the User Rights need to exist on both systems with the same name.

APSS/ACIS/ACSS-SME
not arrogant, just succinct.