We have a new issue... when they pulled the supply and put the new one in, upon boot, it displays Sanity Error. The thought was the Cmos battery was dead and it lost its settings. New battery is in... Sanity Errors even on the old power supply. What can we check to see what got...
Joe and gang, the director of engineering for that radio station is a top notch engineer/designer and he found that the power supply he replaced it with does not include the -5 volts that the DSP section needs. So, he has the correct supply coming on Friday. He found that these newer ATX...
yuck! I think the mother board is ok as the rest of the audix system seems to work... you can make users, change passwords, etc. I work for IheartMedia and we have a lot of radio stations that used to use Avaya, so we are hoping one of our other stations have some cards we can use. Waiting...
I will have them check... I would think it would be the same as when I traced a station, I saw it dialed one of the stations... traced it again, it dialed a different station, same no audio. I cant check directly as I am doing this remote and am not in that market. DSP board is a good idea to...
One of our markets had a power supply failure in it's Intuity Audix system. they replaced the supply. If you dial audix, it answers but you do not hear the typical "welcome to audix" Same if you call an extension, it covers to h99, hunt group is sending it to one of the 12 analog stations set...
I got this solved... luckily I have access to the original programmer from our BP who set a lot of this up. these 2 numbers were not in the Private Numbering table. I didn't know that table even existed lol. Luckily he said he forgets that table often... however in my case, I never knew it...
Extension is 82468
VM box is 82468
Coverage path is 5 (5 rings)
After 5 rings it goes to H99 which dials the audix extension but instead of it going to the users mailbox (and playing the greeting) it is asking fo the extension and # sign.
trace of this station looks no different that traces...
So this ended up being expired certs, both on our local system manager and a disaster recovery ess at our data center. I didn't know it but the GRreplication does indeed replicate to the ess. Also the replication was failing due to the NTP ip that our BP used on the DR ESS is not longer...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.