cannot get FOP2 buttons to retain Group info

[joecronin_mtxit.com]

We have recently implemented a new IVR sub menu on our FreePBX phone server, part of this required that some remote users have two extensions to allow them to 'work' in different groups at different times by placing the uneeded extension on DND.

Example - User X is on extension 301 normally, however when he is working on a particular job role he is on extension 321. He puts ext on DND when he needs to be working on 321 and vice versa. Both extensions are custom devices in that they route through to the remote user's home land line. They are in separate hunt groups with different display names.

This system works fine.

However, the issue that I have come across is that within FOP2 buttons I cannot add these 2nd extensions into the relevant group - although the box flashes green once I put the group name in it and then submit changes and apply config, the group box remains blank which means that these extensions do not appear anywhere in the FOP. Ideally I need the 1st extension to stay in the 'Remote Workers' group and the 2nd extension to appear within the relevant box in FOP2. I have created these extensions as FOP2 users with the same configuration as their main extension.

I think there must be a bug in the system that does not allow this configuration to display correctly within FOP2 as the original extensions no longer appear in the FOP2 buttons menu though they do appear in FOP with the display name of the 2nd extension...

Has anyone else got a similar set up and has come across the same issue? If so have you found a workaround in this instance or is it 'as is' for now?

[nicolas]

Try setting max_input_vars in php.ini to a higher value. There are many posts in the forum talking about it:

View Post 1245
View Post 1775

Remember to reload/restart the web server after doing the change in php.ini

Best regards,

[joecronin_mtxit.com]

HI Nicolas,

Thanks for the reply - I have looked at those suggested posts and they don't seem to be relevant to our particular issue, apologies for the misleading subject as this seemed to be a result of the actual issue:

It looks as though FOP2 and PBX cannot handle two extensions pointing to the same virtual destination - as soon as we modified the destination number of one of the extensions and refreshed the FOP buttons it was able to 'see' both extensions displayed correctly within FOP2, though they were pointing to different external numbers.

There was an issue in the script on the back end which was preventing the correct config upload and we corrected that. However the above issue persists. Is this by design or do you know of another workaround? If so, I appreciate I may need to repost with a more relevant subject!

Thanks

Joe

[nicolas]

FOP2 does not care about virtual things, it monitor devices, what is your button.cfg file in one of those cases you mention? What you cannot do is monitor the same device twice, having for example

[SIP/100]
type=extension
extension=100
label=something

[SIP/100]
type=extension
extension=101
label=another

The above won't work well, status for SIP/100 will be reflected on one of the buttons only.