incoming CDR

[coniglio]

hello, everyone. I had an unsolvable problem I posted a few weeks ago which, thanks to the magic of CDR, I seem to have solved. But now I have a new problem...I turned on incoming CDR on my T1 and I also programmed internal CDR (ICDA) on the voicemail ACD agents for the purpose of trying to trace some calls. Once I did this, the folks in this office started seeing the last four digits of my firm's number, and then the inbound caller ID info. Example, xxxx-5551212 (whereas previously they only saw 5551212). So, I set Incoming CDR back to NO on the route but they're still seeing the extra lead digits. I have NOT put the ACD voicemail ports back to ICDD yet because, I learned the hard way that when I changed them to ICDA I loggged them all out on the Octel 250 side and I don't know how to log them back in. But once I turned OFF incoming CDR on the route shouldn't that have been enough for their displays to revert to showing just the incoming phone number? thanks in advance for your help. Happy Friday.

 

[hawks]

THe ICDA in the CLS is for "Internal Call Detail" not "Incomming Call Detail

 

[coniglio]

I know. I didn't think that the ports being set to IDCA vs. ICDD was a factor, but they're still seeing the extra lead digits even though I turned off Incoming CDR on the actual route. Do you have any suggestions? Thank you.

 

[acewarlock]

CDR has nothing to do with CLID to the outside world. you must have made another change your not telling us about.

 

[coniglio]

I swear I did not. On the route I set INC from NO to YES and I allowed ICDA on my voicemail ports. I've since set INC back to NO but the last four digits of my firm's number are still showing in front of the caller's phone number. I have all the luck, don't I?

 

[coniglio]

my CDR vendor just sent this to me:
Call Info Display
__________________
Display
Access
Prefix
Disallowed

It is probably set to Allowed.

However, I don't know where I go to implement this change. Can you point me in the right direction? Thank you and have a great weekend, everyone!

 

[lretrievers]

I don't think this is a CLID issue; it is a display issue internally from how I read it. There is a place where you can replace the ACOD with the route to the DNIS in the display, I am just trying to remember where it is. It sounds like this may have been turned on.

 

[coniglio]

Well, I found DAPA (display access prefix allowed) but I never touched DAPA/DAPD so I'll have to look around a bit. and, yes, it does seem to be an internal display issue. They either see the ACOD (I assume they see that when the caller is blocking their own caller ID) or they see the last four digits of my firm's #. What a nightmare. I'm going to look at DAPA for now. Thank you very much.

 

[acewarlock]

I'm confused who's called id is showing, the person external to the PBX is seeing the CLID of the PBX or is it showing the phone number of the person calling the PBX on the display? these are 2 different issues.

 

[coniglio]

The employees in my firm(which is 3000 miles away so I can't look for myself) are now seeing the last four digits of their own office's #, followed by the incoming caller's phone number. Before I set incoming CDR to yes in the route they weren't seeing this. I never thought turning on incoming CDR would affect their display info that they see when calls come in but apparently it has. Before, they would just see 555-1212 but now apparently they're seeing 9999 (last 4 digits of their own office's main #) followed by the phone #. so they're seeing 9999 555-1212. Sometimes they're seeing the T1 access code instead of the last four digits of their own phone #. 6005 555-1212. I always get the good ones.

 

[lretrievers]

Just turning on CDR would not have done this; I believe DAPD/DAPA is controlled at the set level.

 

[acewarlock]

This is a new one on me, in my 25 years working on Nortel systems I have never seen a display show you you say. unless it was beening transfer from another ext. Maybe it's the Vmail ports you changed that is doing it.

 

[coniglio]

Yes, it is, but I've since found out that's not the fix. And it didn't make any sense to me either that my turning on incoming CDR and allowing interal CDR on the voicemail ports would've caused this, but shortly after I made these two changes they reported to me they were now seeing the extra digits on their caller ID displays. Hopefully I will figure it out because they're all pretty annoyed now.
thanks for your help.

 

[coniglio]

Leave it to me to have a scenario that, in 25 years, has never been seen before. I'm going to change the voicemail ports in my PBX back to ICDD, except I can't even do that yet because changing them causes the ACD ports in the Octel to log out and I don't know how to log them back in and my Octel vendor is not around today.

 

[acewarlock]

On the only Octel I ever worked I just rebooted the Octel after I made all the changes.

 

[johnpoole]

to log those ports back in, grab a but set, dial ##xxxx, usually any 4 digit number, look up login code in ld 57 ffc, and look up the allowed passwords in ld 23 prt scb.. that acod looks like a cdr prompt, ld 21 prt cdr, but your right, i've never seen that either.. your seeing the acod and the dn. name to acod new name xxxx then leave the acutal name blank? it worth a shot

john poole
bellsouth business
columbia,sc

 

[coniglio]

Hi Johnpoole, they're not logged out on the PBX side. They'll be logged out on the Octel side.

 

[coniglio]

I thought I'd let everyone know that someone set DNIS to YES on this route (and I somehow missed it when I printed out the route) and that's what caused my firm's last four digits to show in front of the caller's number. And -NDGT was set to 4, which is why only the last four numbers showed. Just in case anyone else runs into this problem. Thank you for all your help.