IDC table issue

[Johnthephoneguy]

has anyone ever seen an IDC table not work correctly? I have an inbound 800 number with DNIS 1380, I went to the IDC table and attempt to send that to 8065. SO my idc table reads

1380 8065

just like it should. I am on the correct IDC table, I even went so far as to build it in the others to make sure. I have other Toll Free hitting the same table and they work fine.

i can also go to Dchannel messaging and see that I am hitting the PBX, and also show that I am calling 8065, but the phone doesnt ring. I changed the table to send it to 4997 instead to test and it didnt work, seems like it is just the one number 1380 isnt working.

Any other ideas to try?

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[bigindian65]

have you verified the dnis with the TF provider? Checked route for DNIS yes?


Mato' Was'aka

 

[bigindian65]

you stated other toll free are fine, so I guess it is yes on the route, my apologies.

Mato' Was'aka

 

[GHTROUT]

It would be my guess that the carrier entered the 1380 wrong, and they are sending to something else.

~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]

 

[hypnotic101]

If you go into ld 96 and turn on msgi on that DCH you should be able to call the 800 # and see what they CO is sending for incoming digits. From there you should be able to determine what you need to put in your IDC table to correct the issue

 

[Johnthephoneguy]

On the dchannel I see the DNIS they are sending but my IDC table isnt sending it anywhere, i get open ringing. All other IDC entries for that route/table work correctly. If the Co entered it incorrectly i would see the incorrect number I thought, but I do see the actual DNIS 1380 come across.



JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[GHTROUT]

Interesting. What if you OUT and rebuild the IDC value? Or build a duplicate IDC table, and assign that new one to the route? I know, it does not make sense, but if the table is smallish...an easy test.

~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]

 

[Johnthephoneguy]

I called the smartest guy i know and he suggested the same thing, change the route and the DNIS table and see what happens, we just haven't had the chance to try that yet.

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[phonz1]

or put in the whole inbound number in the table 800 xxx 1380

 

[bigindian65]

I don't remember that call....sorry mid day humor....

Mato' Was'aka

 

[Johnthephoneguy]

lol Today it is much appreciated! Need a good laugh when things that appear so simple (idc table) just do not work as they are supposed to!

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[tnphoneman]

I have seen the problem using IDC table 0. Create another table using a table number other than 0 if that is what you are using.

Signature===========================================

http://www.greatwhitetechnologies.com

Aastra Authorized Reseller

 

[Johnthephoneguy]

We are using IDC table 3.

So Sprint changed the DNIS they are sending. I can now use the IDC table and send the call to an internal DN and it will ring. (this is a toll free number coming in) and it works internally. If I build an acd maxp 1 and forward it off site to another toll free it does not work. Other numbers we have in the same type configuration do work. I have verified trunk to trunk is good even though we have others that are using it with no problem. I also tried building a phantom 500 to dcfw to the external toll free and it does not work either. They are sending DNIS of 8596.


8596 also falls in my DID range, it is not programmed other than the IDC. However, if I do call the DID number 240-555-8596 it will forward out to the tooll free and work correctly, it is only the toll free inbound that is not working.


JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[bigindian65]

on your phantom (just checking) did you CLS CFXA and FTTU?


Mato' Was'aka

 

[Johnthephoneguy]

yes, the phantom would not let me put the dcfw to the toll free without cfxa and I verified fttu. if I dial my DID it will work.

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[telebub]

Does the toll free come in on a different T-1 and route than your DID?

War Eagle!
Lions Baseball '09!

 

[Johnthephoneguy]

It does come in on a different route.

So now they are sending the Toll Free calls to a DID and everything works as planned.

Weird that it wouldnt work coming in on DNIS. We now have the calls coming in and working fine with all the same programming (the DID hits the same acd queue that was programmed for the DNIS).

One of those quirks I guess.

Thanks for the suggestions anyway!

JohnThePhoneGuy

"If I can't fix it, it's not broke!