CDR On BCM 400 3.6

[bcmpimp]

I have done this a few times but it has been a while. I need to set up the CDR on a BCM 400. I have the client wrapper downloaded and also set up the CDR in the BCM to pull. (I also tried push-daily but I think it needs to be pull.) I set up a user id as my network log on and gave it CDR access. I do not nor do I want this BCM to be on the Domain. I open my client wrapper and set my server but it just sits there and does not pass any raw data. What did I forget? Thanks all~

 

[redcomet]

Use the CDR Pull Client Sample Application.

 

[biv343]

If you're working with the real time CDR, make sure that the user ID you use to log onto your PC is also defined in the BCM user manager as a member of the CDR user group. It sounds like you may have done that already, not sure though. Make sure you specify the name of the BCM in the real time screen (not IP address). Also, make sure you can ping the BCM by name.

Have you applied the CDR patches for release 3.6? There were some quirky things that got fixed related to CDR, but I believe most of those fixes applied to systems that were upgraded to 3.6, not shipped with 3.6.

 

[3Sixty]

You do not need to set the BCM to push or pull the data on the transfer parameters the client works in real time and collects the data from a port on the BCM.

What type of OS on the PC?

You set up the user on the BCM to have the same details that they use to login to the network.

Do not worry about the domain.

You should get the information by setting the BCM server IP address on the CDR client wrapper then clicking start.

Marshall

 

[bcmpimp]

Ok...The CDR Pull Client Sample is on the Client Download page..right... Same as CLient wrapper? Or should I find o 3.0 machine and look at the download client page for it? I have the BCM set up to pull, my user name is set in cdr user group, I open the client wrapper and populate the BCM ip address and click set server then start and the ip address grey's out like it is working but it just sits there...no raw data passing. The PC is running xp pro with sp2..(good old sp2). I should give myself admin rights to the pc huh? Biv343 says that I should put the BCM name in on the client wrapper but that did not work.. I have always put the ip address...what now? Thanks all in advance~

 

[3Sixty]

Have you got the inbuilt firewall enabled on windows XP or has windows switched on the inbuilt firewall.

 

[bcmpimp]

No it is turned off. I noticed that there are a few new patches out for CDR Push/Pull that I am going to load...I will post results...any additional help?

 

[3Sixty]

You do not need to have the BCM pull or push if your are using the cdr client.

The only thing you need to do is to set up the BCM user to have access to the CDR group on the BCM.

I am guessing the user has to logon to the windows xp machine.If not this will cause a problem.

 

[bcmpimp]

The user is my user name and password.
I log on the the machine.
I set my user name in the cdr group on the bcm.
It is the same on all places.
I log onto the bcm, the network and the PC in question all with the same user id and password.

 

[bcmpimp]

Loaded patches...did not help. I verified that Windows XP sp2 has built in Dcom blockers. Tried the same set up on a PC without SP2 and it worked like a charm

 

[MarcusTT]

I too have experienced problems getting the CDR Client Wrapper to work with BCM 3.6. Have you managed to get it working on any OS? My client is only interested in realtime stats so CDR Pull/Push isn't an option. Thanks.

 

[BizFoneGuy]

I just started a forum on this same topic and will now cancel it.

I too have windows xp on my notebook with SP2. Is there any way to turn of these so called "Dcom blockers"? Or some other method to make it work? I thought I was loosing it, because the setup seems so easy yet it wouldn't work for anything?

Thanks.

 

[spotless]

This thread is a bit confusing:

The Live Client (realtime data using sockets) was not added to BCM until BCM 3.7. Version 3.6 (unless it is a patched version) is still using DCOM. DCOM has various issues and should probally be re-installed, configured etc... if it is this issue.

The CDR Pull mechanism did have a series of issues in 3.6. Make SURE that all the latest patches have been applied. Additionally, the client wrapper also had problems. The fact that the BCM is not on the same domain could also be an issue. I am not sure, but I think you need to define the domain and cdr user on the BCM to get it working. I have also had problems in the past if my windows login was the same as the cdruser.

I hope this helps.

Stockman16