Sure... Unity looks up the forwarding extension in the database... that includes extension numbers of all subscribers (including alternate) and call handlers... if a match is found the call is forwarded to the greeting conversation (i.e. the transfer rules are skipped) for that handler or subscriber.
You can check the Call Viewer application (which you can get in the tools depot or in the unity program group) to see exactly what's coming in for the forwarding extension on these calls - presumably 3333 and 4444 are being presented to us.
Your customer is doing something else to forward the call to unity that you're not aware of. This works if the Forwarding Number is set to the same extension. To do this, he's either configured a CTI Route Point or dummy phone with those same extensions and configured them to CFwdAll to Unity. In the dummy phone's case, you don't need to do that because the phone doesn't really exist.
The call hits the CTI Route Point or dummy phone and gets forwarded to Unity. Unity sees the forwarding number as 3333 or 4444 and hands it off to whatever object it has that also has those extensions. That's how this works.
He has a forward rule called corporate configured as "forward station any, DNIS any, ANI any, send greeting for coporate greeting". My understanding is forward rule used normally forward from one specific station. Is that usual like this forward any to one greeting? Will there any problem?
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...