DID digits not passed because of T1 provider?

[jayklm]

Ok here is the situation, We have a plain T1 (not pri) going to a 100D card. Our provider is sending 770 as the digits. Calls come in on the main number via the T1. Calls are directed to the auto attendant. Everything works fine. Now we just added 20 DIDs to our T1 service. When a call is made to any of the DID numbers the calls go directly to the Auto attendant. My guess is that our provider is only sending 770 and not sending the corresponding digits. I have the Digits 600 to 619 set up as adjuncts and I have 5 of them on my phone as a primary cover. When I temporally move 770 to something else like 516, all calls coming in (main number or DIDs go directly to the operator). To me this means our provider is only sending 770.

Does this make any sense at all? And is DID on a non-pri T1 possible?

Thanks!

jay

 

[GoKings]

DID is definitely possible on a standard T1. I think that you are correct in what the carrier is doing. Just call them up and be really specific about which numbers need the custom digits 770 and which need standard 3-digit (DID).

 

[franke]

1. Did you reconfigure the T1 to reflect the proper channels are now DID and not C.O.?

2. Did you configure DID to reflect the proper signaling type? (i.e.: wink/wink)

3. Did you configure the proper number of digits you expect to recieve from the C.O.?

4. Did you implement or remove any necessary digit manipulation?

franke

 

[jayklm]

Franke:

I did not configure anything on my side for the "new" DIDs other than setting up adjunct extensions as place holders for DID digits 600 to 619. When we switched T1 providers, we had problems with the digits the CO was passing. They are now passing only 770. On our legend this sends all calls to the auto attendant. The signal type was not changed; it is still wink/wink. Our CO is passing 3 digits consisting of 770. Or legend is expecting 3 digits. Like I said originally, if I renumber the calling group 770 to something else, all calls go to the operator as "unknown DID" or something like that.

I think the next step is to call our T1 Provider and do what GoKing said, be specific on what digits I want sent for each DID number.

Thanks for responding

I will post my outcome when this situation is resolved.

jayklm

 

[Pepperz]

The fact that the numbers are going to the operator, on a "wrong" DID shows that DNIS is being used. See if the provider can "outpulse" specific digits to prove you can capture them where you want, like you are doing on your primary cover buttons, then if that works, and the DID's don't, you know they aren't sending what they are saying. Just keep pushing.

Pepperz@charter.net

 

[jayklm]

It seems that when my rep placed the order, he was not specific enough. The CO programmed the new DIDs just like they did for the mainline (delete 7 add custom digits 770). So the order has be submitted again to leave the main number as is and do a delete 4 for the DID numbers.

To me this sounds like the commonsense thing to do. If someone orders DIDs one would think you would want different digits passed.. Anyway hopefully in a day or so everything will be working…

 

[Pepperz]

Well, there you go, assuming that common sense would be applied. Most of the time we're lucky if there is any kind of sense applied at all, common or not. Common Telco rule, reps are good at taking and placing orders; no so good knowing what those orders do to a customer's PBX.

Pepperz@charter.net

 

[jayklm]

My provider is now passing the right digits! and DID now works.

jayklm