sundance-communications.com/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems outbound caller id

Techs,
I have a Definity G3 V11 and all of the sudden my ani won't display a name or #. I was going trough some ARS and Routing tables earlier in the week and think I might have made a change somewhere. I called my carrier and they said they are publishing my number and It's not on thier end. Is there a field I might be over looking? When ever someone calls from the site using either trunk (only two onsite) (one local one LD) the caller id shows unknown and doesn't give off a #. Thanks in advance!

If you have standard two-wire trunks, which it appears that you do, your switch can't be causing this. Of course, it's remotely possible that somehow you have enabled digit manipulation in ARS to insert a *67 prior to the outbound digits being sent. I really, really doubt that you did this accidentally.

Try making a call to a number that's known to be within the same CO first and see if the CLID information shows. Remember that it must be another number that is carried by the same service provider; for example 305-761 can be carried by any service provider within the same geographic area now. If at&t is your local service provider, then make sure that your local test calls are made to someone who is also an at&t customer.

Next, try calling a number that is perhaps across town, but not long distance and check. DON'T test this using a cell phone.

Next, using each one of the trunks, make a long distance call to a known valid test number and see what happens.

Lastly, preface the number you dial with 1010288 to force the call through ATT for the long distance test calls and see if there's any change.

You really cannot rely upon test calls to cell phones since they are almost always routed through a toll switch, even if the cell phone has a local number.

My guess is that the issue is in a toll switch between your local end office and the destination. This happens pretty frequently nowadays since many service providers are going with VOIP-based switching and they don't really know what they are doing.

Don't take the carrier's word for it in your case. Do a variety of tests like those that I have mentioned and then some. These days, you have to do the telco's troubleshooting for them unless you want the problem to last forever. Sad but true.

I hope that this information might help you.

Ed,
Thanks for all the help. I will continue testing this morning and let you know what I find.

Your using PRI's, right? What do you have in 'cha isdn pub'

if it is something that YOU did, you might try doing a list history

Liquidvw- I do have numbers in the "isdn pub" but they are not showing when calling out.

Blklabs- I have a bad habit of using the change command instead of the display. Something I will be working on from now on!

do a 'list trace tac XXX' and make an outbound call. Maybe that will give you some clues as to what is hitting the trunk.