Jason Jason wrote: > I am using Sipxecs version 3.10.2-013143 2008-07-23T18:09:14 > ecs-centos5 with an Audicodes Mediant 600 Gateway 5.40A.020 for the > SIP Gateway. The issue is when going through call logs, I am noticing > the following many entries of > “anonymous<sip:[email protected]>”. This system has many > multiple menus as well sub menus. Any known issues relating to this?
Those are not a problem - that is the SIP-standard way to indicate that caller-id is blocked. It's probably configured that way on some of your phones (or perhaps on incoming calls). > Also I am noticing when viewing the logs, it displays from as soon as > the user calls, every option they push, extension they get transferred > to. These call reports are being reviewed for meetings, and when there > are about 4000 abandoned calls with 1 second duration in 30 hours, > this seems. Is there ways to minimize the track in the call logs? > Would I have my Audiocodes push out information to a separate CDR > server? You're seeing these in the audiocodes logs? It's probably logging the 'ringing' indications that it gets from the various phones that calls are being forwarded to. If you use the sipXecs CDRs you won't see those as 'calls' unless they are answered. > I have brought up in a previous post about an issue in call park, and > I was told that I am using an version that is very old, and has many > bugs that have been fixed in later versions. Is this the case for this > issue? Would an upgrade to 4.0 solve this reporting nightmare? Upgrading to 4.0 won't change what Audiocodes logs, but it does also have improvements in sipXecs CDR reporting. > As well how difficult is an upgrade to 4.0 with a few Custom Made > Auto-Attendants, Dial Plans, 150 users, 50 Nortel Phones, 5 Audiocodes > Gateways, as we would like the most minimal downtime as possible. There have been a few problems reported with upgrades (see the archives of this list). There are fewer of them with the current builds of 4.0.1, which at some point in the next few weeks will be copied to the stable release area, but in the mean time upgrading to one of the 'nightly' 4.0.1 builds (which, alas, are not happening every night... working on that) should be fine. What model phones do you have? _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
