Search results for query: *

I can't really do some of your troubleshooting steps because I am not at that location. I can however dial the fax from my cell and it work fine. Here is the event report: EVENTS REPORT Event Event Event Event First Last Evnt Type Description Data 1...

I said IP Office b/c when I searched for "invalid set type" or "no Remote Office assignment" all that came up was stuff regarding IP Office.

It also sounds like there are two rings going on at the same time.

The station is a virtual station and I don't use IP Office.

No it does not busy out, and the trace is from a cell phone.

I have a number, 65878 that forwards to an outside line that happens to be a fax line. When I call the number it forwards like it should but as soon as the fax tone starts I get a busy signal. I have the prefix in the ars table with the correct rout pattern. What am I doing wrong? For privacy...

Here is the report from the display events EVENTS REPORT Event Event Event Event First Last Evnt Type Description Data 1 Data 2 Occur Occur Cnt 81 No digits collected 202/13 27A1 08/01/10:52 08/02/13:40...

When people call into VDN 43266 they get routed to vector 202 which will place them into hunt group 12. This all works as it should. My problem is that when people hear all of the messages in vector 202 twice (because it is set to an unconditional loop) they are cut off and receive a busy...

I had a similar problem where the MWI lights stopped working after resetting our CM server. If you go under Configuration > Database, there is a "Fixup" button. It rebuilds all the index files and solved the problem for me.

I have a weird problem. I have a hunt group and some people are reporting that when they call into the hunt group they hear our loop of messages in the call vector 2 times and then are cut off. Does anyone see anything wrong in the programming that would cause this? If no one is logged into...

That fixed the problem! Thank you very much!

I do not have the option to enter a night service destination or announcement extension. That's why I'm trying to do a work around.

These are the options I get when making a hunt group. I have ACD as Y. My group type choices are circ, ddc, ead-loa, ead-mia, pad, slm, ucd-loa, ucd-mia change hunt-group 800 Page 1 of 61 HUNT GROUP...

Extension 62009 is a normal phone. change station 62009 Page 1 of 6 STATION Extension: 62009 Lock Messages? n BCC: 0 Type: 4625 Security...

COVERAGE PATH Coverage Path Number: 124 Hunt after Coverage? n This is the coverage path: Next Path Number: Linkage COVERAGE CRITERIA Station/Group Status Inside Call Outside Call...

I am running CM 4.x and when I create a hunt group I do not have the option to enter the announcement on that screen. I have tried to create a work around but I can't seem to get it to work. What should happen is a call should dial 62009 and then: Call to 62009 ----> coverage path 124...

I mean circuit b.

FYI, the problem has been resolved. AT&T bounced the circuit to clear the slips. The new PRIs were not configured the same as the originals. After AT&T bounced the circuit I was able to change the channel to "b" and it resolved the problem.

I switched my protocol on my end from a to b and that did not seem to work...

We are running on 4.0.12. I suspect that the protocol or the config on the new pri is different than the original and is causing the issue.