Is there a limit on the maximum content-length supported by CUBE for a SIP call? We have two peerings with CUBE with ASR SBCs and when the SIP INVITE with SDP content length is 1233, the call is processed properly and is successful. But, when a SIP INVITE with SDP has a content length of 3168, ASR SBC receives a 100 TRYING from the CUBE and then there is no response, and the call fails.
I know without the SIP logs from the CUBE it is a bit difficult (we are still awaiting SIP logs), but just wanted to know if very long content-length can cause issues and if there is any limit on the maximum supported by CUBE?
The following section from the reference Cisco document does refer to content length, but I'm not sure if this applies as a general rule or is meant only for modifications with SDP
"The maximum SDP header length is 2048 characters. If any header length exceeds
the maximum value after a rule is applied, that rule will be ignored, and the changes are not
applied. If the total SDP length exceeds 2048 characters after modifications, all changes to the
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...