BCM50r3.0 Auto-attendant issue

[yankblan]

I've seen it on a couple of 3.0 and so have some of my colleagues, and no patches so far or work around work consistently: I set the AA to answer after 2 rings (CLID), but the AA answers immediately.

Of course, I started with the basics, like ring services, prime sets, forwards and all.

Weird thing is, if I set it at 4 rings, it answers after 2. So I thought, that's it! I'll leave it like that, but I can do 6-7 tests and one will answer after 4 rings, thus I cannot use it as a work around.

Any suggestions or experience with that issue?

 

[ironhorse17]

I would listen,monitor with butt set, if it is a good ring cadence 4 seconds: 1 second of ring 3 seconds of silence no stuttering maybe you have noise on that line or a ground and test all the lines to AA individually for response.

 

[cook1082]

Does it happen if you call the roll over lines and not just the main number? Say not 61 but 62-63-64 etc...

 

[yankblan]

Cook, yes, doesn't matter which line, and only on 3.0. I guess I'll look at what horse is talking about; maybe there's an issue with the firmware that make them more sensitive to it, kind of like the 1.0 with the trip ring current issue they had.

 

[telcodog]

I think you'll find that the calls are ringing in with a double interrupted ring. The rings are just long enough to fool the AA. It's really only ringing twice but because of the interrupted cycle, the AA thinks it rang 4 times. This is usually the way the telco signals you that you have voicemail messages on your line. Those features should be turned off if the lines connect to a pbx though.

If you listen with your butt set like ironhorse says, you'll hear it right away.

 

[yankblan]

All right, I'll take a look next time I get there; my customer isn't even aware of the problem, so until then I'll keep it to myself!

That said, if the ring cadence really is off, do you know if in general telcos care about it or will I get a shrug and a so what if I report the problem?