The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to resolve the problem of calls that fail to establish due to the Cisco TelePresence Server's Session Initiation Protocol (SIP) message size that is too large for the default maximum incoming size configured on Cisco Unified Communications Manager (UCM).
Cisco recommends that you have knowledge of Cisco Unified Communications Manager Release 8.6.1 and earlier, when deployed with these Cisco TelePresence infrastructure products:
The information in this document is based on Cisco Unified Communications Manager Release 8.6.1 and earlier, when deployed with the these Cisco TelePresence infrastructure products:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
The best way to resolve this issue is to upgrade Cisco UCM to Release 9.1.2 (latest version at time of publication of this document) - which has a default maximum incoming SIP message size of 11000 bytes. This resolution supports the most recent features of the TelePresence Server that are used with Cisco UCM.
Alternatively, you can adjust the "SIP Max Incoming Message Size" on your current version of Cisco UCM as shown here: