Known Issue: SIP Domain Issue
From DocWiki
(Difference between revisions)
(New page: '''Back to IM Compliance Main Page:''' Known Issues: IM Compliance) |
|||
| Line 1: | Line 1: | ||
'''Back to IM Compliance Main Page:''' [[Known Issues: IM Compliance]] | '''Back to IM Compliance Main Page:''' [[Known Issues: IM Compliance]] | ||
| + | |||
| + | |||
| + | If you configure the SIP domain with upper case letters, for example Cisco.com instand of cisco.com, you may experience problems with instant messaging. This is a limitation of some versions of Cisco Unified Personal Communicator. | ||
| + | |||
| + | |||
| + | <h2><tt> What Caused it?</tt></h2> | ||
| + | |||
| + | Typically, this failure happens because the Cisco Unified Personal Communicator regards the IM as coming from a different entity for which availability information does not exist. | ||
| + | |||
| + | |||
| + | <h2><tt> What Can You Do? </tt></h2> | ||
| + | |||
| + | In Cisco Unified Presence Administration, change the proxy domain to lower case. | ||
Latest revision as of 11:46, 21 January 2011
Back to IM Compliance Main Page: Known Issues: IM Compliance
If you configure the SIP domain with upper case letters, for example Cisco.com instand of cisco.com, you may experience problems with instant messaging. This is a limitation of some versions of Cisco Unified Personal Communicator.
What Caused it?
Typically, this failure happens because the Cisco Unified Personal Communicator regards the IM as coming from a different entity for which availability information does not exist.
What Can You Do?
In Cisco Unified Presence Administration, change the proxy domain to lower case.
