Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Pri Card compatibility
- Thread starter ttech
- Start date
- Thread starter
- #3
Right now I have 016MLX cards in slots 1 & 2 and 2 100D cards in slots 3 & 4, then a mix of 408, 008, and 016ttr cards for the rest, Does this mean I can swap the slots and and the SS/PP porgraming for the PRI's and the 2 016MLS's and it should work
The system has R7V14.2 Software to take care of the old Line 801 being a PRI port bug
The only problem is the callers hear a small FSST sound every 7 seconds or so and it has been doing it for about 5 years but the provider said they are seeing tiny slips coming from the first PRI.
~Don~
The system has R7V14.2 Software to take care of the old Line 801 being a PRI port bug
The only problem is the callers hear a small FSST sound every 7 seconds or so and it has been doing it for about 5 years but the provider said they are seeing tiny slips coming from the first PRI.
~Don~
Well, the problem I saw the first time I did a "M" Mixed with an 016 was the blasted thing would only stay up for about a minute or two, and then it would crash and burn.
I guess it could be that they would hear FSST, but that sounds like a clock issue. (Just a guess).
HOWEVER, if you do go about swapping cards be aware that you could be setting yourself up for a TON of programming changes, depending on how you displace ports in use and stuff.
I guess it could be that they would hear FSST, but that sounds like a clock issue. (Just a guess).
HOWEVER, if you do go about swapping cards be aware that you could be setting yourself up for a TON of programming changes, depending on how you displace ports in use and stuff.
Merlinman,
A little clarification on the use of 517M15 modules with 016TR modules.
Is it only the 016TR analogue station modules that cause the conflict or the 016MLX module also?
And if you put them to the RIGHT of the "M" does that mean to the RIGHT of ALL DS1 modules in the shelf or shelves if you have multiples?
.....JIM....
A little clarification on the use of 517M15 modules with 016TR modules.
Is it only the 016TR analogue station modules that cause the conflict or the 016MLX module also?
And if you put them to the RIGHT of the "M" does that mean to the RIGHT of ALL DS1 modules in the shelf or shelves if you have multiples?
.....JIM....
The deal is this:
Yes, it's an interaction between the 016-TRR & the 100-D modules.
It's best to have the 100-D in the First carrier, and any 016-TRR's to the right.
AAs it was explained to me, if the 016-TRR is to the Left of the 100-D, that will be a problem.
If the 100-D is in the second carrier, and the 016-Trr is in the first carrier, that's worse.
Worse yet is if the 100-D is in the 3rd carrier.
I guess I am going to have to change my design theory all up.
Yes, it's an interaction between the 016-TRR & the 100-D modules.
It's best to have the 100-D in the First carrier, and any 016-TRR's to the right.
AAs it was explained to me, if the 016-TRR is to the Left of the 100-D, that will be a problem.
If the 100-D is in the second carrier, and the 016-Trr is in the first carrier, that's worse.
Worse yet is if the 100-D is in the 3rd carrier.
I guess I am going to have to change my design theory all up.
Thanks Merlinman, let us know your new design layout for this set up when you have it finished.
But in the meantime, even though my 100D modules are 517E15s, is it a good idea to put the 016TRRs to the right of the DS1 module as a standard practice?
I am in the process of converting a Supertrunk to PRI ISDN using a second DS1 module. Currently it is in slot 8 and the temporary will be in slot 13. But to put all the 016TRRs to the right, all I have to do is put the 100D module in slot 4 and shift all the modules to the right and only do a slot renumber since there are no other trunks in between them.
Utilizing a second 100D I can move the Supertrunk T1 to the temporary 100D and reprogram slot 4 as PRI. This way I can have both T1s live to test everything on the PRI before cutover w/ Pacific Bell. And the customer is still in service keeping downtime to a minimum.
....JIM....
But in the meantime, even though my 100D modules are 517E15s, is it a good idea to put the 016TRRs to the right of the DS1 module as a standard practice?
I am in the process of converting a Supertrunk to PRI ISDN using a second DS1 module. Currently it is in slot 8 and the temporary will be in slot 13. But to put all the 016TRRs to the right, all I have to do is put the 100D module in slot 4 and shift all the modules to the right and only do a slot renumber since there are no other trunks in between them.
Utilizing a second 100D I can move the Supertrunk T1 to the temporary 100D and reprogram slot 4 as PRI. This way I can have both T1s live to test everything on the PRI before cutover w/ Pacific Bell. And the customer is still in service keeping downtime to a minimum.
....JIM....
I know a lot of people have something they call a "SuperTrunk".
I do not know what it is.
However, if it is a ROB BIT set up, rather than a Common Channel, then your idea should work just fine.
See, it's not only PRI (Which is the main use of Common Channel) it is ANY common channel set up that can have the problem.
I do not know what it is.
However, if it is a ROB BIT set up, rather than a Common Channel, then your idea should work just fine.
See, it's not only PRI (Which is the main use of Common Channel) it is ANY common channel set up that can have the problem.
I forgot to mention.
You could also back up the Translations,
load them on a Surrogate switch, say in your lab or something,
make your changes for PRI,
save them to a flash card,
and then go make the swap on site with a minimal bit of down time as well.
You could also back up the Translations,
load them on a Surrogate switch, say in your lab or something,
make your changes for PRI,
save them to a flash card,
and then go make the swap on site with a minimal bit of down time as well.
MM,
A "Super Trunk" is a DIOD E&M Tie trunk in a Digital format (T1) with inbound "DNIS", it has an unusual qwerk though. On outbound calls there is usually no "CallerID", not even the BTN is delivered to the called party at least in SBC and Bell South territories, you get "out of area" or a bunch of *'s. This often causes issues with the customers using them because a lot of people will not answer OOA or * calls, thinking them to be telemarketers. Hence the switch to PRI. Of course the carriers often neglect to mention the lack of "CallerID" when they promote them.
A "Super Trunk" is a DIOD E&M Tie trunk in a Digital format (T1) with inbound "DNIS", it has an unusual qwerk though. On outbound calls there is usually no "CallerID", not even the BTN is delivered to the called party at least in SBC and Bell South territories, you get "out of area" or a bunch of *'s. This often causes issues with the customers using them because a lot of people will not answer OOA or * calls, thinking them to be telemarketers. Hence the switch to PRI. Of course the carriers often neglect to mention the lack of "CallerID" when they promote them.
As 'phonesrus' mentioned above SUPERTRUNK is DS1 service offering from Pacific Bell/SBC from 5ESS or DMS100 CO switches that can provide two-way trunks or one-way, DID, DOD, etc with a variety of options including 'hookflash' tranfer, dialplan with Centrex, etc. The channels are E/M signalling and since it is on the 'trunk side' of the switch no form of CID is available and none of the switch providers have ever written any software to support such features. Most of these features are available in the PRI offering, except the 'hookflash' transfer, which gives you the ability to do a DID-TO-DOD transfer disconnect, just like Centrex.
One of the reasons the Supertrunk offering was developed was because during the 1990s PRI equipment in PBXs was too expensive if it was even available from some companies and regular T1 cards cost a lot less and you could get the 'hookflash' transfer feature. This worked great for some types of answering service PBXs and voicemail systems and provided the 'lossless' advantage of DS1.
Actually in the Pacific Bell case the basic PRI cost less than the Supertrunk offering. But my client needs CID outgoing and that is why we are changing it.
Your suggestion to use backup translations is great, but I don't have a Legend in the shop to do that type of setup. So in my case adding the second 100D will work and they get a spare card in the process.
....JIM....
One of the reasons the Supertrunk offering was developed was because during the 1990s PRI equipment in PBXs was too expensive if it was even available from some companies and regular T1 cards cost a lot less and you could get the 'hookflash' transfer feature. This worked great for some types of answering service PBXs and voicemail systems and provided the 'lossless' advantage of DS1.
Actually in the Pacific Bell case the basic PRI cost less than the Supertrunk offering. But my client needs CID outgoing and that is why we are changing it.
Your suggestion to use backup translations is great, but I don't have a Legend in the shop to do that type of setup. So in my case adding the second 100D will work and they get a spare card in the process.
....JIM....
Jim, Around here (Denver) we have a service provider that does PRI really cheap, compared to everyone else. (Or at least, so I am told)
As I understand it, their OUTGOING CID can be tweaked a bit, and they do a GREAT JOB with the Legend/Magix.
It took them a little bit to get ramped up from the time they started, but now I recommend them as the Vendor of Choice.
As I understand it, their OUTGOING CID can be tweaked a bit, and they do a GREAT JOB with the Legend/Magix.
It took them a little bit to get ramped up from the time they started, but now I recommend them as the Vendor of Choice.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question