problems in conference bridge after migrating to 4.1.3SR3 from 4.1.3
very recently i upgraded my CCM from 4.1.3 to 4.1.3 SR3. i use 3725 with DSP farm as conference bridge ( the ios code on 3725 is 12.3.11 T7 )
the conferencing stopped working for me as soon as press conference on my after callint the 2md party, both my calls get dropped.i see that the CCM registers the bridge and also in SCCP config of gateway i see the CCM registered.
for testing purpose i configured one my 3845( with same version) over WAN as my conference bridge and then conference worked fine for me.
there are few command difference in 3725 and 3845 . In 3845 i can configure CCM version as 4.1 and in 3725 i can do only 3.1 or greater. i am not sure if this is problem or not.
in CCM traces i got this unusal error which is attached
Re: problems in conference bridge after migrating to 4.1.3SR3 fr
We are also having the same issue, 3725 used as conf resource, as soon as we press conf button all calls are dropped with fast busy. we are using CM 3.3.5 and IOS 12.3.7T12.
cisco TAC poked around and could not find anything wrong with config (of course, we have other sites with identical config all working ok). so they said it must be bad DSPs even thou there are no DSP errors on the router. i doubt it is DSP issue but i'll let you know when TAC figures it out.
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...