CLASS (Caller ID) troubleshooting

[slapin]

So, here is the situation.

3300ICP SW 8.0.11.7

Customer ordered Caller ID on LS trunk lines and I have enabled CLASS in Circuit Desctiption form and ANI trunk in LS trunk COS.
Now I have 4 rings before AA will pickup and no Caller ID. This indicates that system is waiting for Caller ID but not getting it. Telco has stated that the order has been completed and Caller ID is set on all the lines.

Now the question is how to troubleshoot this remotely and confirm that we get CLID or we don't and blame telco?

Butt-set is not an option at the moment

So far I tried to change Trunk Service assigned from AA to one of the extensions. Still no CallerID

Any ideas?

 

[kwbMitel]

You have enabled ANI/DNIS/ISDN Number Delivery Trunk
in the COS of the trunk.

This option is not intended for Analog trunks.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[slapin]

nope. It was not enabled. This COS is a clone from other system which works with CallerID just fine. I feel like I will have to drive over there. At least I don't see any other alternative to troubleshoot it remotely.
I suspect that Telco is BS-ing but cannot prove it.

 

[kwbMitel]

I was soooo certain.

oh well, how about the trk cct descriptor? Class Enabled?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[slapin]

It was not enabled and I flipped it when telco reported order completion. I'm thinking how I can trace this in the system and see in there CallerID detection fase. Some sort of Analog line debug procedure.

 

[kwbMitel]

Hopefully someone else can chip in. I almost never work with analog trunks.

Sorry

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[paterson]

Why not turn on SMDR recording? Then you can look at the inbound call.

_______________________________________________________________

If you did not take enough time to get it right the first time...

What makes you think that you have time to fix it?

 

[slapin]

The problem is I am not sure that Caller ID is coming in. The service can be added to the account but it doesn't mean that guys in the CO actually configured or tested it.

We had multiple issues like this. For example instead of assigning 128000 bps of bandwidth for EF (voice) traffic they actually configured 12800 bps. The case when 0 matters. On the account everything was enabled and provisioned and it was really hard to prove that they have to look closer.

 

[paterson]

You said you want to troubleshoot remotely. If you turn on SMDR for those trunks, then you can look at the SMDR Log Files and see if you are receiveing CallerID on inbound calls.

_______________________________________________________________

If you did not take enough time to get it right the first time...

What makes you think that you have time to fix it?

 

[Canuckvoip]

paterson is on a good track here.
Look at port 1752 with a telnet session and it will give you smdr live.
Or, cuz you are using loop start, get someone with an analog clid phone and plug it into the mod that goes into the controller...
The clid is sent inbetween the first and second ring.

Dave

You can't believe anything you read... unless of course it's this.

 

[slapin]

There is nothing in SMDR.

Two options

1. Telco sending caller id. 3300 misconfigured
2. Telco not sending caller id. 3300 configured properly

The advise will work in case#2. SMDR displaying nothing but trunk number and extension.

But what if I'm wrong and something is up with this configuration or the system is having issues?

So, I'm looking for something lower level. Like shell or maintenance command which will print call processing diagnostic. Actually I gave up. I'm going there and will tap on the line with batset.

Any way thank you everybody for input.

 

[JimHilton]

There has to be something in the SMDR report.

08/22 11:38 00:00:31 T001 016 *2506551234* 301

The above tells the time, trunk call duration and the caller ID. This is from a sx200 not sure how much diff a 3300 is, but you should see something similar, the only other thing that would help verify no CID from telco is if there were ** and no phone number.

If you are seeing nothing, no time stamp etc, check your smdr output options.

Jim

 

[IrwinMFletcher]

Jim, Don't think that will work with analog lines. CLID is inband, so you have to detect it to display it in SMDR. If the 3300 isn't configured properly, a detector won't be lut in the path to detect the signal. Chicken and egg thing.

 

[JimHilton]

Hmmm, that sample is from my 200, as a LS/class turnk. This system was setup as business 1 though. Many "default" options already set. The only thing I had to figure out was outgoing calls.

But as a prove out, i think he really needs to hook up a regular phone with CID on to verify if the telco is providing it or not.

 

[IrwinMFletcher]

Agreed, a phone on the line is the best option.

Just pointing out that for LS trunks, you need a specific detector put into place to detect the CLASS information. So the SMDR won't prove anything if the information isn't there since it can be because A. telco didn't send it, or B. programming isn't right to put a detector in the path. These detectors are limited resources and are not put in by default on every call.