cfw busy instead of unregistered - if TCT device created
we have csf devices configured for jabber for windows, For the case that the user isn't logged in the Jabber Client, we have configured call forward unregistered (CFUR). This works as expected, but when we add additional TCT device (jabber for iPhone) with the same number, CFUR doesn't work anymore because the the CUCM signal busy now (if both Jabbers offline). Thats the wrong behavior from my point of view.
What can we do to avoid this, any suggestion are welcome.
you have identified this correct; in order for jabber for iPhone users to get the CFUR to work appropriately you will need to configure Mobile Connect; until then the behavior you reported seems working as designed. Please refer to the following link to learn more about how to configure mobile connect;
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...