E & M T-1 with Caller ID - Norstar MICS 4.1

[Tigerrco]

My client has changed from a PRI to an E&M T-1 set up as a 2-Way DID by the Carrier. Caller ID doesn't work; the carrier says it will if I program in the * format:
*clid*address* Any ideas or suggestions are most appreciated.

 

[jerryreeve]

I have been told by the local rboc that t-1's don't pass Caller ID. If you get this working please let me know so I can get something else working. thanks.

JerryReeve
Communications Systems Int'l
com-sys.com

 

[jgideon]

You're actually getting *ani*dnis*... i'm not sure how to programm it on a Norstar, but look for ani/dnis configuration. Bell would be sending you CallerID instead of ANI. This usually isn't available from a LEC for CallerID.. I'm surprised they're doing it for you.

 

[Norstarguru]

The Norstar System can recieve Caller ID from the Lec, but the CO must deliver ANI/DNIS in DTMF mode.

 

[Tigerrco]

I am answering my own question as I have found a solution:
The Local Phone service provider(RBOC)is Nuvox Communications.
They were able to set up their E & M T-1 in *ANI*DNIS * format to send Caller ID Info. On my 4.1 MICS, I just programmed the Lines as E&M, Wink, Answer mode: Auto, changed ANI to Yes & left DNIS as No.

I'm now receiving Caller ID # info but not name. Thought everyone would want to know this success story.

 

[AlquestTech]

Yes. (PRI allows for the most information to be transferred (down to the system ID and Statioon level.)
Just curious as to why the customer changed from PRI to E&M T-1 setup. With PRI call by call service they certainly could configure Tie Service, two-way DIDs etc, and still have better Caller ID featuring, including passing extended caller ID(to the station level).

Just curious is all...

 

[salo0920]

Tigerrco,

I followed your suggestion here and got the callerid (number, no name) passed through to my Norstar MICS via a standard T1 E&M (no PRI).

HOWEVER, now how do I get the callerID information to go BACK to the telco using the same circuit?? In other words, it seems that Norstar will support the *ANI*DNIS* incoming format and let the telco pass the callerid info through (BTW, this is known as Feature Group D), but how do you get the Norstar to SEND callerid information over the T1 E&M in the same way that it receives it???????

I would think there would be a setting for this.

Thanks,
Harold

 

[PERRYPJ]

YOU DON'T LEC WILL HAVE TO SEND YOUR MAIN NUMBER, OLI ONLY WORKS ON ISDN-PRI

OLD ROLMEN WORKING ON NORTELS

 

[salo0920]

PerryPJ,

You mean the Norstar will take and display ani digits but not send them? Is there no option for this?

 

[jgideon]

With an E&M wink setup, when originating a call, the PBX can only transmit dialled number. Perry is correct--if you're trying to transmit a CallerID, there can only be one number assigned to the whole group, at the LEC CO level.

Also, this isn't true FGD signalling. True FGD signalling would have start and stop tones, along with ANI info digits and some other stuff, if memory serves me correctly.

Also keep in mind that ANI isn't necessarily Calling Party Number.

 

[Tigerrco]

Just to report back to whoever was asking about extended Caller ID with E&M T-1 vs. PRI. The Caller ID number goes to the transferred Norstar station(I tested it on a call that was answered by Auto Attendant). Any thoughts about differences between T-1 & PRI?

 

[timhunt2]

I have issues with passing caller id on a pri.
1. clid is passed - to an extension by dialing a did/targ. line.
2. clid is passed - to vmbox mess. env. when dialed directly by did then fna/cfb to vm.
3. clid is passed - to a station when transfered by AA.
4. clid is not passed - through AA then fna/cfb to vm
(message envelope).
5. clid is not passed - to smdr6 output when station is dialed through AA.
6. clid is passed - to smdr6 output when dialing to did
and call is answered at the set.
Any hints? thanks