Hi Greg,
It seems you are asking me to configure your asterisk to replace agentcallbacklogin? I can only help you configuring fop2, and suggest asterisk configs, but not configure your whole dialplan. FOP2 works very well with agentcallbacklogin too. It is not a behavior from FOP that you want in FOP2, but forwardport the asteriskcallbacklogin application that was deprecated since asterisk 1.6.
I do not understand your Local/XXXX and SIP/YYY relation. That is something that you choose to do in your dialplan logic. But it does not make any sense just by reading your post. How do you relate a device with an extension? I have no idea, you never mentioned how either. And it does not matter. Your dialplan is yours, but do not expect tools to match your criteria or ideas on how things should work.
If you want the agentcallbacklogin behaviour, then use agentcallbacklogin in asterisk 1.4, or switch to agentlogin that works in a similar fashion also in 1.6 and 1.8. FOP and FOP2 track devices/channel names. They do not track other things. You must define a button to track a real asterisk device/channel, with just one exception: user&device mode for freepbx.
You can try to mimic freepbx user and device mode, where you setup buttons like:
[USER/1120]
and then you create astdb entries mapping users and devices, in the way that FreePBX does, that is quite complicated and that I do not even remember exactly how it is done, there is a userloginlogout.agi , AMPUSER astdb entries to play with, etc. I think that your idea of how things should work is more like this freepbx mode. With this mode you track "extensions/users" and not "devices". To dial an extension you always dial the extension number, but it might rang a different device depending on where the user is logged in. As this behaviour is not something you can do with asterisk applications (like agentcallbacklogin or agentlogin) and it is just a total invention using dialplan, agi, astdb, etc, it is IMPOSSIBLE for any application to accommodate everyone's needs/dialplans/ideas/idiosyncrasy. Freepbx User & Device mode is one way to do it, and fop2 only supports that way. But in that mode you will only see user/extension buttons not directly related to a device.
The label renaming in fop2 works by matching the extension and context for a Local queue member, or by agentlogin events. It renames ONLY on queue membership.
I am not going to review all your screenshots, dialplan or ideas as I do not have the time and fop2 will probably not match or will work the way you want. I already mentioned the way fop2 works, and it makes absolute sense. I think you have to try to replicate the userevents and astdb entries for freepbx user&device mode to have something similar, where you see buttons for PEOPLE/EXTENSIONS, and they are not related to a particular device as the relation is done at the time they login into the system.
best regards,
