I asked if i could send a config but the company policy prohibits it. But i can tell you that the config is very staightforward.... No fancy stuff.
I thought it had something to do with the autodetect encapsulation command you can set on the serial interfaces but what i did ......it sure did not work.
The message is there approxiamately every 10th caller......There is however no relationship between for example analog/isdn and the error........... But the calls were not connected if the error came along.
Another odd thing was that the person that dialed in.......did not get connection.....tried again.......and there was success.
The only thing i could find was that if the callload went up the problem pooped up.
There are no other messages before or after.......
I really don't see any mention of this message in the last 18 months, so this could be a new issue. I would suggest you open a case with the TAC, include the serial config (if possible), the version, and the logged messages, so that this can be further pursued. I can't say right now what the cause is, what a workaround may be, or what the effect (aside from a failed call) is.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...