I am seriously puzzeled! I entered the 9 1 xxx-xxx-xxxx an AT&T wireless number into the SNR filed on the users 7975G phone, check this out, when I call the DID of the users 7975G desk phone from the very AT&T wireless phone that is entered into SNR expecting the call waiting to come on the AT&T phone showing the system calling me back and the SNR workign corectly right. Nope! The call waiting does not come back but insted the call goes directly to the AT&T wireless voicemail having never showed up in call waiting, strage? That means that the system is sending the call out to the Cell but somehow AT&T is seeing that call and sending it directly to VM, strange, yes, but I tested this no less than 10 times. I even called AT&T to make sure that call waiting was enabled, it is, I asked what AT&T's timeout is to VM and it is set to 30 seconds, wierder yet, I tested the AT&T wireless phone by placeing two sepeate land line calls to it and the call waiting and VM no answer timmer of 30 seconds is working correctly(tested many times). Even stanger yet!!! yes, I call the 7975G's DID from another phone and it does not ring the AT&T cell phone at all and goes to the CUE voicemail. Yes, thats right!!!! The strangest is yet to come! So if you are still following this, when I place the call from the AT&T wireless to the 7975g's DID the 7975G does ring as it should, despite the fact that the call gets picked up after 2 or 3 rings by the AT&T voicemail(having never showed a call waiting incoming mind you) the 7975G continues to ring,,,, and,,,, to really put me into a twilight zone, I picked up the 7975G to see what would happen and it intercepted the connection to VM and connected me to the AT&T phone! This is CIA type stuff!
OK, what in he LL kind of crazy SNR app is this. Does cisco have some kind of way to tell if its a VM versus a live voice and sort of soft connect the call? Does ATT know that the call comming from the UC520 system is a some kind of crazy coded industry standard SNR call? Did I just discover the earth is flat?
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...