Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

CDR reporting using Avotus

Hi there -

We are running several CUCM clusters -- 7.1.3 -- and have enabled CDR on all.  We sftp the records to our third party CDR vendor who is Avotus.  We have hit a problem with Avotus which seems to be caused by the way CDR records are generated in CUCM.

Configuration of one site that we are using to try and solve this issue:

2 - 3845 voice gateways

each 3845 supports 8 PRI's connected to serial interfaces

we have three carriers providing PRI services for this site

we spread the PRI's across both voice gateways to minimize outages if one fails (each voice gateway has PRI's for all three carriers)

The issue is:

A cdr record has the IP address of the voice gateway as the "destDeviceName" regardless of which serial interface actually routed the call.  The bulk of our gateways are H.323 however we do have two that tie to Nortel PBX's using QSIG (which is great for CDR because the actual serial interface is noted as the "destDeviceName" in the CDR record) but we do not want to convert everything to MGCP.

Avotus actually told us that the only way to get reliable traffic / usage reporting using their services was to dedicate a voice gateway to each carrier rather than mix them on one.  This does not seem to be a practical solution and would require a lot more hardware as this is a typical set up for us.

I have not been able to come up with any solution to this problem.  If Avotus could use the partition information in the CDR record we might be able to combine that with the gateway IP to "guess" what PRI was used but it's not ideal.

Has anyone come across this?  Any ideas on how / if we can get the serial port information for an H.323 call into the call record?

Thanks,

Les

  • IP Telephony
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: CDR reporting using Avotus

Hi Les,

Unfortunately, there is no way to get the serial port information for an H323 call into the CDR.

The call handling for an outbound H323 call (i.e. from IP phone to PSTN) is as follows:

- The CUCM sends the call to the H323 GW.

- The call will match an inbound Voip dialpeer on the H323 GW.

- The GW then dispatches this call to the PSTN based on the outbound POTS dialpeer that is matched. The GW never sends any corresponding information to the CUCM. Hence, CUCM never knows the exact PRI that is used when the call exits the gateway towards the PSTN side.

The only information that CUCM has is the H323 GW's IP address (which is what is reported in the CDR).

I know that this will not help to resolve your issue, but I hope the above information answers your question.

-Nikhil

2 REPLIES
Cisco Employee

Re: CDR reporting using Avotus

Hi Les,

Unfortunately, there is no way to get the serial port information for an H323 call into the CDR.

The call handling for an outbound H323 call (i.e. from IP phone to PSTN) is as follows:

- The CUCM sends the call to the H323 GW.

- The call will match an inbound Voip dialpeer on the H323 GW.

- The GW then dispatches this call to the PSTN based on the outbound POTS dialpeer that is matched. The GW never sends any corresponding information to the CUCM. Hence, CUCM never knows the exact PRI that is used when the call exits the gateway towards the PSTN side.

The only information that CUCM has is the H323 GW's IP address (which is what is reported in the CDR).

I know that this will not help to resolve your issue, but I hope the above information answers your question.

-Nikhil

New Member

Re: CDR reporting using Avotus

Thanks Nikhil

This was the final determination that I arrived at too but I was hoping that there was some other option.

Appreciate the input.

Les

920
Views
0
Helpful
2
Replies
This widget could not be displayed.