You'd think this one would be straight forward...
In Call manager, I have a Hunt Pilot (1045) which has only the reception number (1010)
the Hunt Pilot forwards to my Exchange AA Pilot (1045) after x many rings... the idea here is that when the receptionist is away, she can log out of the hunt group and the exchange AA takes over (or if the pilot times out).
However --- Exchange is trying to handle this as a voicemail call, as the call is technically a forwarded call. This is driving me bonkers.
If I remove the UM hunt group for that number (1031), I can call the extension directly, however when the call is forwarded (say from an inbound call) exchange UM errors with .
Reason: "The Unified Messaging server cannot find a valid UM hunt group for "1031" associated with UM IP gateway "x.x.x.x"."
With the hunt group enabled,
The user with extension "1045" on dial plan "umdial" is not enabled for Unified Messaging.
clearly - it's trying to handle the forwarded call as a call to its voicemail system .
I can't find a good way to strip the forwarding headers in CUCM, and I can't work out a way to force 1031 to be an AA call (regardless of sip forwarding headers)... any ideas?