| | #1 (permalink) | ||||||||
| Guest
| Hi, We have a Norstar unit installed in one of our offices. When a user makes an outgoing call "unknown caller" shows up on the receiving end. Is this something that our provider needs to correct, or is it a programming feature on the Norstar? We have 20 channels on a T'1 from the Telco provider for call processing. My experience is with Meridian Option 11, 61's etc. I know how to program outgoing caller id on these systems, but Norstars are a mystery to me. Thanks. | ||||||||
|
| | #4 (permalink) | |||||||||
| Junior Member ![]() ![]() Pirates_Ghost has no status.
Location: The other side of the Lake from work Rep Power: 12 ![]() | change auto attendant/directory recording Quote:
| |||||||||
| | |
| | #5 (permalink) | ||||||||
| Senior Member ![]() Ramjet is wore ass out from the holidays!
Rep Power: 8 ![]() | T1's do not provide outgoing caller id with one exeption. There is a service from your LEC called a digiloop. This will allow for otg clid on those channels, and those channels are otg only. Other channels will be provisioned for incomming calls be they DID or setup just as an analog line would be. To be able to specify the otg clid, you would need a PRI circuit. Then you can set the clid in the OLI section of line access in N* programming. | ||||||||
| | |
| | #6 (permalink) | ||||||||
| Guest
| This is exactly my problem. My provider (is that what LEC means?) is Sprint. I have a T1 with a Mainstreet channel bank hooked to my 8x24 Norstar. When I was with AT&T about 5 years ago, outgoing CLID was no problem. Ever since I switched to Sprint, people get "unknown" etc. Sprint says I have to provide it via my PBX. I don't really have a PBX as I understand it, and certainly I can't find CLID anywhere in my documentation. Sorry for being an in-house simpleton, but I can't understand the previous message that talked about being able to provide outgoing CLID myself...can I make it work with this setup, or must I call Sprint over and over until they will finally listen? Thanks wise ones | ||||||||
|
| | #7 (permalink) | ||||||||
| Senior Member ![]() Ramjet is wore ass out from the holidays!
Rep Power: 8 ![]() | Sorry, you will not be able to set any CLID with an 8x24, not to mention a T1. You will have to upgrade to a MICS and go with the previously mentioned "Digiloop" or a PRI circuit. The 8x24 does not have the capability to connect a T1 or a PRI directly to the KSU. | ||||||||
| | |
| | #8 (permalink) | ||||||||
| Guest
| OK, very good to know. Thank you RamJet. So that must mean that AT&T was somehow providing me my outgoing CLID before? Is there some magic phrase I can use with Sprint to get them to provide it? (Hopefully something less severe than threatening to walk) Or maybe I'm wrong about AT&T having been able to provide it...? | ||||||||
|
| | #9 (permalink) | |||||||||
| Junior Member ![]()
Location: A telco building [Maybe 500 miles east of Tiverton, Ontario (CANADA)] Rep Power: 5 ![]() | Quote:
1. RTFM, there's no OLI control on RBS T1's 2. Generate OLI/CLID from their CO, just like ISDN BRI 3. tell them they're morons again Even if you had a PRI, the KSU/PBX couldn't generate CLID because it's connected to a channel bank, which basically converts your T1 into 24 analog trunks. YMMV though, I don't know about american telcos, but that's how it works in Canada... besides, ALL my clients have switched to PRI since a while back. | |||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Help! Disable outgoing caller ID | lunaemica | BCM and Norstar | 3 | 11-10-2003 04:50 PM |
| Help! Disable outgoing caller ID | lunaemica | BCM and Norstar | 2 | 10-21-2003 08:32 PM |
| AUDIX could not capture the external caller ID | waynelin | Merlin | 2 | 08-07-2003 01:45 AM |
| Caller ID name on SBC PRIs | jheath | Meridian Systems | 1 | 07-20-2003 10:59 PM |
| Block Caller ID? | Wildman | Meridian Systems | 6 | 03-10-2003 04:26 PM |