[cisco-voip] A log full of "Transient Connection Attempt"

[Robert Singleton]

On Tue, 2007-01-16 at 18:26 +0200, Anthony Kouloglou wrote:
> Yes,
> Ed i found it!! You are right!
> The customer didn't tell me that he had 3 phones that could not
> register because he hadn't configured them for CCM.

I found that the ATA-18X does this, too. I use ATA188's and ATA186's for
paging access, the occasional cordless phone and (somewhat to my dismay,
but that's another thread) fax machines. In those applications where we
only use one Phone port, the other phone port generates these Transient
Connection Attempts. The solution I used was to configure the 2nd port,
even though I don't assign a DN. The idea was that my helper admins
would not have to worry about whether any field device was configured
differently, giving the option to simply swap ATAs in troubleshooting.
Upon reflection, it would perhaps be better to disable the 2nd port on
the device, saving a bit of device weight on the server. There are
enough of these in my configuration to add significant weight to my
overloaded CallManagers.

Besides the obvious mess that transient connections leave in the log,
they do take some CPU time to process for the CallManager, so they
really should be eliminated one way or the other.

Robert