We are trying to create general messages and we have a person recording the messages in a seperate room due to background noise. While recording the user hung up without hitting the pound button to stop recording and then the phone that was connected to that message was hung. It seemed as if the phone was hung until the recording played out its default time? Is this true, is there any way to get around this?<br><br>thanks,<br>John<br><br>
I'm assuming this is a TRAP call from the client machine, right? This sounds like it could be one of the TRAP timing bugs that was fixed in 2.4.6 build 102 (not sure what version you're running). Depending on the timing of the hangup the TRAP session can stay open (and leave the port busy) indefinitely.
If you're already at 2.4.6 102, I'd definitely report this to TAC and get a ticket open so we can investigate. If not, I'd reccomend getting to 2.4.6 and seeing if that takes care of the issue.
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...