I have a new install of Unity 2.4.6 Unified that is<br> acting oddly.<br><br> From Subscriber -> Profile, the Recorded Voice Option<br> is set to phone, aimed at a extension available via LAN.<br><br> I have used both DNS naming, and IP address for the server<br> location in case a DNS issue was causing a delay.<br><br> When I select to playback, the extension immediatly rings.<br> However, when I answer the phone, it can take up to 10<br> seconds until the recorded name is played.<br><br> This is a repeatable problem on multiple machines, and<br> different accounts.<br><br> What is causing this delay (no there is not 10 seconds of<br> space before the users are saying there name - grins).<br><br>--- Thanks ---<br><br>
My first guess would be a call progress issue (in the case of an analog PBX system, anyway...). We may wait that long to determine if the phone has been answered or not. Particularly if you picked up right away (i.e. Dialogic didn't hear a full "ring cycle" it can take a little longer for it to figure out the line is answered).
but if you're using CM, that wouldn't be the case. I'm not sure what to look for there...
That's a known problem... we think we have a fix for it. The trap connection holder is the guy that keeps the phone session alive while you move around to different greetings/prompts and the like or different messages in VMO so you don't have to reconnect each time.
The "H:\..." drive references is the actual directory to the code on our local build machine here... it's not refering to a directory on your hard drive. It's so the engineers can quickly find the code in question.
- Have opened a case about this with Cisco TAC, this was the first that they have hard about this.
- Did discover that the problem only affects those users who do not login in via NT and 98 to the NT domain that contains the Unity server. Even though they are can manipulate the Unity SAWEB screens all they want after authenticating once for access, and a second time for the media master feature.
Oh... if you're not authenticating on the NT networking, having to do so twice is actually expected behavior, that's not a bug.
Since we rely on NT Challange and Response security, IIS will actually require you to be authenticated before the SA/AA/SM pages are even hit (that's not us asking for the login/PW). Since you haven't already authenticated on the network, it needs to know who you are and what rights you have.
The 2nd authentication with the media master is annoying but unavoidable... there's simply no way around it at present with that security model. For folks not on the NT network, it's something they will have to deal with, at least for now.
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...