If you want to log the manager output for debug, you can set the options line in /etc/sysconfig/fop2 like this
OPTIONS="-d -X 15 -l /tmp"

I changed (temporarily, that quickly started adding up to quite a log file) the settings in /etc/sysconfig/fop2 to the above and restarted fop2

The output.log populated very quickly but the error.log got no entries.

The entries in the output.log for Mktg_5 were

127.0.0.1       <- Event: PeerEntry
127.0.0.1       <- Channeltype: SIP
127.0.0.1       <- ObjectName: Mktg_5-in
127.0.0.1       <- ChanObjectType: peer
127.0.0.1       <- IPaddress: {IP_address_of_provider}
127.0.0.1       <- IPport: 5060
127.0.0.1       <- Dynamic: no
127.0.0.1       <- AutoForcerport: no
127.0.0.1       <- Forcerport: yes
127.0.0.1       <- AutoComedia: no
127.0.0.1       <- Comedia: yes
127.0.0.1       <- VideoSupport: yes
127.0.0.1       <- TextSupport: no
127.0.0.1       <- ACL: no
127.0.0.1       <- Status: OK (17 ms)
127.0.0.1       <- RealtimeDevice: no
127.0.0.1       <- Description: 
127.0.0.1       <- Server: 0

127.0.0.1       <- Event: PeerEntry
127.0.0.1       <- Channeltype: SIP
127.0.0.1       <- ObjectName: Mktg_5-out
127.0.0.1       <- ChanObjectType: peer
127.0.0.1       <- IPaddress: {IP_address_of_provider}
127.0.0.1       <- IPport: 5060
127.0.0.1       <- Dynamic: no
127.0.0.1       <- AutoForcerport: no
127.0.0.1       <- Forcerport: yes
127.0.0.1       <- AutoComedia: no
127.0.0.1       <- Comedia: yes
127.0.0.1       <- VideoSupport: yes
127.0.0.1       <- TextSupport: no
127.0.0.1       <- ACL: no
127.0.0.1       <- Status: OK (17 ms)
127.0.0.1       <- RealtimeDevice: no
127.0.0.1       <- Description: 
127.0.0.1       <- Server: 0

This was the same as the entries for the other channels (for which I had NOT yet added the extra channel in the fop2 admin) and no errors/outages were reported even though the registry did show No Authentication.

I don't know where to go now.

I was wondering if the timing settings were such that the Peer never realized the trunk was out, but:

• I had the same settings in the previous (fop1) system that did show trunk registration failures
• the registry settings are immmediately being seen
• I had left the (non-registered) state as is for 15 minutes so I thought that would allow any delays to be recognized

Something is different between ours systems though, since you are getting yours to work, so FOP2 is certainly capable of it. It just is not doing it with my configuration. All the other functinality is working (Extensions grey out when not connected, Conference, Park, Trunks show properly when being used, Toollbar Icon commands work, ...)

One thing I did try: On Mktg_8-out (another trunk, that the outbound routes are configured to use as the first one for local calls) I entered a bad secret in the Rgistration string and the Sip Registry recognized the trunk as Not Authenticated, yet, when I made a local call, Mktg_8-out was still used and the call was completed.

Then I entered a bad secret in the Oubound Settings, the Inbound settings and the Registration string and the Mktg_8-out trunk did NOT process the call; it passed to Mktg_7-out (as it is supposed to).

However, in neither case, did the error.log get any entries.

Is this helping to zero in on the issue?