CDR Configuration with Syslog server issue

Unanswered Question
Sep 7th, 2010
User Badges:

Hi @ll,

I'm trying to configure the gateway to output CDR to a syslog server. The GW sends the details to the syslog server, but the PeerAddress field is always empty - this field contains the calling/called party information. Is there anything left to be enabled so this information is transmitted to the syslog server?

This gateway is connected to the PRI using MGCP. Any further details that you may need in order to help me out, just let me know.


service timestamps debug datetime msec
service timestamps log datetime msec localtime





logging trap debugging
logging facility syslog




gw-accounting syslog

logging IP Syslog Server

And this is what I get in the Syslog server, as you can see, I cannot identify the caller ID nor the calling ID.

Tue 9/7/2010 3:54:10 PM : IP >>INTERNAL.Notice<<<45>66342: Sep  7 15:54:10.433: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId 90742C70 B9B611DF 9F168719 71C4F24E, SetupTime 14:59:20.333 CET Tue Sep 7 2010, PeerAddress , PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 14:59:20.333 CET Tue Sep 7 2010, DisconnectTime 15:54:10.433 CET Tue Sep 7 2010, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 164468, TransmitBytes 26314880, ReceivePackets 164211, ReceiveBytes 26272488

Thanks in advance,


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (4 ratings)
Luis Ruiz Lopez Wed, 09/08/2010 - 03:38
User Badges:

Hi testeven,

I was following that documentation to configure it but it doens't work. I tried adding this to my config:

aaa accounting connection h323 start-stop tacacs+

aaa authentication login default group tacacs+ line
aaa authentication login vtymethod group tacacs+ line
aaa authentication login conmethod line none
aaa accounting exec default start-stop group tacacs+
aaa accounting commands 15 default start-stop group tacacs+
aaa accounting system default start-stop group tacacs+

Since I don't have radius in this GW I didn't put aaa accounting connection h323 start-stop radius, and given the fact that I don't have h323 configured but mgcp I also tried to put the same but with mgcp.

Is this only allowed for H323 connections? I have other GW working fine with H323 configured as it connects to the CCM and the Nortel PBX, but this one above nothing...

Any ideas?


testeven Wed, 09/08/2010 - 13:39
User Badges:
  • Cisco Employee,

Hi Luis,

With MGCP, you can use the CDR application with CallManager rather then using AAA accounting.  
MGCP voice gateways do not support accounting via RADIUS.

emresumengen Mon, 10/25/2010 - 05:28
User Badges:

Hello Tere,

I was wondering if that means CDR logging via syslog "is NOT SUPPORTED" on MGCP runnning voice-gateways?

I have a customer that only needs voice gateways who does not want/need a UCM (for other purposes). Is UCM _required_ here as a gatekeeper-like position, to provice CDR, or is it a best-practice recommendation?



testeven Mon, 10/25/2010 - 10:34
User Badges:
  • Cisco Employee,

Hi Emre,

That's correct, MGCP is not supported for CDR ans Syslog server. Please refer to the information below:

"To collect basic start-stop connection accounting data, the gateway must be configured to support gateway-specific H.323 
accounting functionality."


MGCP is a master / slave protocol. If the Cu wants to pull CDR ( Call Detail record ) info to a billing server, that can be done on the Call Manager itself. However, if the customer requires to capture CDR from the gateway itself and send it to the ACS,
then he needs to use H323 protocol for his voice gateway.

For more info refer to:



If this post helps, please rate!


This Discussion