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 !
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.
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...
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?
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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...