I worked around this issue by taking a totally different approach to the problem. I created and ACD path and had the call interflow to a system speed call and transfer the call. This also required the updating of several COS options to allow the call to transfer outbound with the original calling party ID. My hope this MiContact Center captures the call counts to this ACD path for them to have a record of the number of calls.
Here are the changes I had to make to allow the call to transfer from the NuPoint over the SIP trunks and pass the original calling party ID.
Trunk COS
Changed Originator's Display Update In Call Forwarding/Rerouting to YES
Public Network To Public Network Connection Allowed, set to YES.
NuPoint COS
Display Held Call ID on Transfer to YES
Public Network To Public Network Connection Allowed, set to YES.
SIP Peer Profile > Calling Line ID, updated both options below to YES
Public Calling Party Number Passthrough
Use Original Calling Party Number If Available
In not answered the call will recall the call back to the system and reroute to the customers general delivery mailbox. The call was recalled to the MiVB ACD path, not the interflow extension. I made this ACD path extension a call director mailbox within NuPoint and sent the call to the customers general delivery mailbox.
So now I have a call being picked up by a NuPoint Call Director mailbox, transferred outbound to a cell phone, recalling back to the PBX and into NuPoint which reroutes to a general delivery mailbox if not answered by the user that has the cell phone.
If I could set different ring tones for DSS/BLF keys on a Mitel MiNet 6900 IP phone all if this could have been avoided......hopefully this helps someone in the future.