"DDD" for Caller ID when on dedicated long distance t1 1

[KenNECIVSIPS]

When a long distance call comes in from our dedicated long distance t1s, "DDD" shows up in the LCD display for Caller ID. Our vendor told us that dedicated long distance cannot show caller ID, because there is no D-channel to serve the data.

Is this correct?

We have been getting a lot of answers from him that turn out later to be incorrect, and we really need the LD CID to work, so Im hoping that someone can tell me exactly what to tell him.

Thanks!

 

[Fixin]

Caller ID can be delivered on a T1 in 2 ways. PRI T1 uses the last channel(D channel) of the T to deliver ID info as well as other important info required to send and recieve calls. It can also be delivered using feature group D inband signaling. The reason DDD shows up is you have the T1 route programmed as 00 in cm 3500. It should be an 04 (tie line). You can give it a new name in cm 3503 and 772.

 

[jgideon]

Well, I'm confused... I took your post to mean that you are placing calls FROM your PBX over a 'plain' T1 (ground start/e&m wink type trunks) to someone who has a CallerID box, and they don't get CallerID.

Generally speaking, to transmit CallerID, you do need to have ISDN-PRI trunks to the outside world.

HOWEVER, depending on what type of switch your long distance carrier uses (and what software release that switch is running), they may be able to program a single static number against the whole truk group. With this method you don't get station-specific CallerID, but at least something could show up.

Calling Party Number is transmitted forward with the call, while Calling Party Name is 'retrieved' via a database lookup done by the receiving telco. (I'm assuming calls in the US.) If the two companies don't play nice, the called party may see the correct number, but 'out of state' instead of the name.

What carrier do you use? Almost all of the tier1/tier2 carriers can do this programming in at least part of their networks.

 

[KenNECIVSIPS]

No, when a call comes in to our PBX (2000 IVS2) through the PRI, we get caller id info (just the number, can we show the name there?). But whena call comes in from the outside to our PBX on one of our dedicated t1 lines, we only see "DDD" on the LCD screen.

Fixin, you said "You can give it qa new name in 3503 & 772" what are we renaming? the DDD?

Thanks!

 

[jgideon]

Ah, okay, receiving a call on your PBX delivered by an LD carrier. What is the signalling on this T1? Am I save in assuming that these incoming long distance calls are to a toll-free number?

PRI is much easier to get CallerID number on than a 'plain' dtmf/mf T1. However, that is possible too. What you're probably looking for is ANI and DNIS delivery from your long distance carrier. You'll probably have to do programming on both ends to make it work. Are we discussing an NEC pbx (your nickname made me think twice)? Unfortunately I don't get to program NEC's, just use them, so I can't direct you there.

Typcially when an LD carrier delivers a toll-free call to you via T1, they can specify the format of what's delivered. The most common I've seen is *ANI*DNIS*, or *ANI*DNIS*infodigs, so something along the lines of *npanxxnnnn*nnnn*


As far as name delivery on your local PRI trunks, it is sometimes available depending on equipment on both ends. You have to be running NI-2 protocol, and your LEC/CLEC has enable the feature, and your PBX software has to support it.

 

[KenNECIVSIPS]

hahaha, I forgot my nick was created when I used a definity. I loved that definity system, and these NECs are driving me crazy! LD comes in to both regular numbers and 800 numbers. When you say "you'll have to do programming on both ends" what do you mean by "both ends"?

Thanks,

 

[jgideon]

If it's a plain T1 from your LD carrier, and they're currently sending you 4 digits (say) to match your extension and route your toll-free's to the right place, when they change to send you ANI and DNIS together, instead of just DNIS, you have to change your side to expect the extra digits, or the calls will start to fail when they make the change.

Also, you may need to double check your tone receiver resources--you'll be going from 4 digits to probably 16, and you might end up with some contention.

 

[dontworx]

If you wan't caller ID/ANI on a t-1 in a neax 2000 you have to have feature group D set on the T-1 from the Phone company and have a 4-rstb card to recieve the ANI from the phone company. The real challenge is to find someone from the phone company who knows how to set up feature group D.

 

[KenNECIVSIPS]

So fixin, why do we set cm3500 to 04, when this is not a tie line (I think of tie line as tying 2 PBXs together)?

Thanks,

 

[pave35]

There is no need to change CM 3500 to a 04. The current setting you have of 00 is fine.
If you do upgrade to the ANI make sure you inform the carrier that the circuit must be MF inbound and DTMF outbound.
As for the PRI you can get name display (if provided by the carrier) on either NI2 or Northern Protocol (sometimes incorrectly called NI1).
As for the difinity they are nice as long as you want to stay in side the box. Just plug in and go. Once you have to start making a system jump hoops the NEC runs rings around the Lucent. Not to mention it's half the price and the hardware seems to be far more robust.

 

[Fixin]

Going by the tech support cheat sheet, the route SHOULD be set to Tie line in 3500. Then change the name in 3503 for the route to 00. Then put the name of your choice in 772>00> name using charactor codes.

 

[KenNECIVSIPS]

Thanks guys, Now our vendor is saying that the systems we have (2400 IVS2 and 2400 IPS) cannot handle the inbound caller id on Dedicated T1 lines, but we can purchase another system that will handle it. This sounds completely incorrect. Is there some documentation I can point to in order to dispute this? Thanks so much.

Just to clarify, he said that a normal PRI t1 can deliver the CID we need (and it does, for local calls), but not dedicated t1 lines.

 

[KenNECIVSIPS]

Fixin, can you send me this "tech support cheat sheet" that you mention. Is that a cheat sheet for setting up LD CID? (I can only hope!

 

[Fixin]

Below is the basic assignment for a 24 channel T1 B8ZS/ESF with wink signaling. Trunk route and trunk numbers are examples only.

1. Take note of, or set the sense wheel on the 24DTA card e.g. 4

2. CM 050>04>09

3. CM 0701>0400-0423>D100-D123
Note: All channels must be assigned.

4. CM AA00>04>0

5. Reset switch.

6. CM 3000>100-123>10

7. CM 3500>10>04

8. CM 3504>10>2

9. CM 3509>10>03

10. CM 3520>10>00

11. CM 3521>10>02

12. CM 3524>10>2

13. CM 3546>10>1

14. Reset the T1 card.

If receiving DID digits on the T1 the following may also be required.

15. CM 3512>10>3 (if receiving 4 digits) or 2 (if receiving 3 digits).

16. CM 3517>10>11 if 1 digit deletion is required on the received DID #.

17. CM 3518>10>0 (if digit conversion of receiving digits is required).

18. CM 200>52>804 where received DID digits are 5200-5299.
Note: Received digits must = a station number regardless of if they are to be converted to another number or not.

18. CM 7600>5200>XX where DID 5200 is sent to bin XXX.

19. CM7601>XXX>200 where DID that was sent to bin XXX is terminated to stat

 

[Fixin]

ISDN PRI Basic Assignment IVS2/IPS
The following is an example only for programming required for basic ISDN PRI
assignment. Wheel settings, trunk numbers, etc. are examples only.
1. Take note of, or set the sense
Wheel on the 24DTA, SC01, or
24PRTA/B card e.g. 04 and 05
2. CM 050>04>09
CM 050>05>12 (24PRTA/B or
SC01)
3. CM 0608>0>05
4. CM 0701>0500-0523>D100-D123
5. CM 3000>100-122>10
CM 3000>123>11
6. CM 3002>100-122>18
7. CM 3003>100-122>18
8. CM 3040>100-122>18
9. CM 3041>100-122>18
10. CM 3007>100-122>000-022
11. CM 3019>100-122>XXXX
Where XXXX= the last 4 digits of
CPN to be sent.
12. CM 3034>100-122>00-15
NOTE: Steps 10 and 11 are for CPN
on a trunk basis. Use CM 1212 and
CM 1213 if CPN is required on a
station basis.
13. CM 5005>00-15>YYYYYY
Where YYYYYY= the area code
and office code of CPN to be sent.
14. CM 3500>10>00
15. CM 3504>10>2
16. CM 3509>10>08
17. CM 3516>10>0
18. CM 3518>10>0
19. CM 3528>10>0
20. CM 3590>10>3
CM 3590>11>3
21. CM 3593>10>00
22. CM A900>0>123
23. CM 410>50>05
CM 410>57>05
24. CM 482>04>0
25. CM AA00>04>0
26. CM AA06>05>20 (AT&T)
21 (Northern)
28 (NI2)
27. CM AA14>05>0 (for PRTA?B only)
Some further LCR programming may be
required depending on the ISDN
protocol utilized in CM AA06.
See CM 8A5XXX>157-164.
NOTE: The D-channel trunk route has
only one CM set other than default. CM
3590.
Name Display is only available with the
PRTB card utilizing 2100 series s/ware.

 

[KenNECIVSIPS]

Where did this come from? Do you have an "offifcial" pdf or something you can send me? Right now they are denying that it is even possible, so I have to get as official as possible. Thanks!

Email it to kennethwsmith -at- yahoo.com if you can. Thanks!

 

[HarrisD1200]

jgideon has this totally right. Despite my handle, I am a translator on Nortel DMS-100, DMS-250, and DMS-500. On a Long Distance PRI, I can always send Calling Number, and can send Calling Name if the protocol is NI-2 from the DMS-250 to the CPE. Since your problem seems to be on the Robbed Bit Signaling Long Distance T1 (has to be E&M Wink), I will confirm that I can send variations of *10 digit ANI*DNIS* on that as well. Obviously, there can't be name sent on this. Seemingly, you need to find out 100% from your Long Distance T1 provider whether they can provide this or not. If it's a DMS, it require a software option (SOC code NSER0001) that is purchased. And yes, finding someone who knows in the CO whether they have this option, and how to use it is the trick. Once you determine that the CO can provide it, you then need to worry about the CPE side, which I can't help with. Luck to ya!