| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: split |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Senior Member ![]() WhereWolf is sober (maybe....)
Rep Power: 4 ![]() | Can you split a T1? I've got 6 b-channels on a Nortel Meridian T1 attached to a Cisco Router T1 port which feeds IOG to a switch on the far side as Tie Trunks (they are actually Virtual IP trunks because this T1 is a wan connection for the network also) The Brass want to install a BrookTrout Fax server (8 Chan - T1-PRI Interface with a D-Channel) without adding an extra T1 Card in the Nortel (No Room) Can I somehow split the Meridian T1 thru a CSU/D&I box like a Kentrox DataSmart and utilize the 8 Chan + the D Chan out one interface and the 6 B's out the other? Anyone have anything similiar onsite? Is there a better way? Just looking for idea's....Thanks for any info Wherewolf | ||||||||
| | |
| | #2 (permalink) | ||||||||
| Senior Member ![]() slagburn has no status.
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 ![]() | Doubt it - the Nortel system only allows for 1 D Channel so even if you could split it the other device would be left with B's that would have no control mechanism. Now I have split a PRI with traditional trunks, the first 10 trunks are traditional and the remaining trunks are PRI - works ok but it's not being split between two systems. | ||||||||
| | |
| | #4 (permalink) | ||||||||
| Senior Member ![]() WhereWolf is sober (maybe....)
Rep Power: 4 ![]() | The Analog Brooktrout isn't a very good option, becasue in the T1 PRI version, you actually get a card that's a full T1, but software unlocked for the channels, so we start with 8 and grow to 16 (or 23). Slagburn, The 6 B's aren't using the Dchannel now....because the other side of the circuit doesn't have DCH capabilities. So I'm not sure what the difference would be? Just trying to wrap my head around it..... Thanks for the feedback. Wherewolf | ||||||||
| | |
| | #5 (permalink) | |||||||||
| Senior Member ![]() slagburn has no status.
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 ![]() | Quote:
Since this isn't ISDN and there isn't a D-channel involved you can split the T-1 up any old way you want. Just build the trunks into different routes. | |||||||||
| | |
| | #6 (permalink) | ||||||||
| Senior Member ![]() WhereWolf is sober (maybe....)
Rep Power: 4 ![]() | Thanks for the info, when you look at the 6 trunks (channels) in OTM on Loop 10, OTM calls them B-Channels, so I was try to keep the terminology in line....maybe that's where I went wrong. Thanks again for the input Wherewolf | ||||||||
| | |
| | #7 (permalink) | ||||||||
| Senior Member Fletch is Nortel E911 PLM
Location: NORTEL - NJ Rep Power: 6 ![]() | Is there a DCH assigned to the first 6 channels now? If OTM is using the term B Channel for a non PRI trunk, then I'd like to know about it so I can submit a CR to get that changed. The term B Channel should be specific to a PRI connection. __________________ Fletch For more on Nortel E911 Solutions on the web: http://nortel.com/e911 Don't forget to register for the FREE E911 Webinar on Oct. 30th! http://thevoicereport.com/E911 | ||||||||
| | |
| | #8 (permalink) | ||||||||
| Junior Member ![]()
Rep Power: 0 ![]() | Doesn't Look Possible WhereWolf. You have 2 devices providing input to the M1 PRI DDP. No T1 Splitter cable to the M1 that I know of. You can deliver 1 T1 CAS from the M1 to 2 devices, but they must appear as 1 signalled group, but you cannot receive 2 separate T1's into the Same DDP. Interesting if you could, I will keep watching. | ||||||||
| | |
| | #9 (permalink) | ||||||||
| Junior Member ![]()
Location: Missouri Rep Power: 6 ![]() | About the only thing that would come close would be the Adtran Atlas 550. I believe it can emulate both ISDN on both NET and USER sides and do some switching depending on the digits sent, etc. Give their pre-sales tech line a call - they're ususally pretty good about discussing this kind of "what-if" scenerios. | ||||||||
| | |
![]() |
| 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 |
| Split Mode | ERR3056 | Meridian Systems | 20 | 02-04-2008 10:28 PM |
| T1 Red Alarm | m_steeler | Meridian Systems | 5 | 04-30-2006 06:43 PM |
| Strange Problem with a T1 isdn with SBC | yuvami | Meridian Systems | 2 | 04-29-2006 01:51 PM |