We are using ACS 2.6 to track incoming and outgoing calls from two AS5300's each using a different carrier. In the CSV the callerid field is being populated, but with one carrier it shows up with the calling from number/calling to number and on from the other carrier it is only showing up as the calling from number. Has anyone seen this problem? Is this a problem with the caller-id setup with the carrier or the acs server? I guess the true question should be: Where does acs obtain those numbers to populate the spreadsheet?
Re: ACS version 2.6 TACACS accounting CSV file format
ACS simply writes down what it receives from the AS5300, it doesn't do anyting intelligent with it. The problem is the AS5300's are sending this information to ACS differently. This is probably because of how your carrier does it, or different q931 signalling or the like.
On each AS5300 do:
debug aaa accounting
and you'll be able to see the records that each AS5300 is sending. You'll see they're different, what you do then is up to you. You can talk to your ISP and see why their different, or try changing your AS5300's config to match perfectly, but if you have different signalling methods on your lines then there may be little you can do.
In short though, this is very unlikely to be an ACS problem, since it just records what it receives from the AS5300's.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...