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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Configure T1 and Lines to Appear on DLC 2

Status
Not open for further replies.

bzgal

Programmer
Mar 21, 2009
15
First off I haven't configured a Legend in 9 years so I'm very rusty at this lines stuff. I have a customer with a Legend R6 that has a T1 coming in and will have DIDs. The T1 programming seems fairly easy because I've done the extensive programming of a PRI. I just want to make sure there aren't many steps to programming the T1. Also with the DIDs, the client doesn't have the DID module so I'm thinking i can just configure them on the 408 card as trunk because telco is sending 4 digits so the digits will match the extensions. Then how does one put the CO lines on the operator phone? I'm sure they should be placed into a pool and then touch the lines accordingly. So with all that being said...my questions are: How do I program a T1 on a legend? How do I set up the DIDs and how can I make their ported lines appear on their DLC? Even if you can answer one question, it's very much appreciated.
 
You won't have any "lines" - you will receive everything as DID or DNIS digits, which will be routed to extension's SA buttons. For your Operator, put additional SA buttons on the phone to receive multiple calls.
 
That makes sense but that means it's easier than I thought. Are you saying I don't have to configure lines/trunks for all the DIDs? as long as I renumber the extensions with the appropriate DID digits it will ring accordingly? now with the lines that are being ported should I put those in a pool and place them on the DLC? thank you sooo much!!
 
When lines are "ported" to a T1, they behave just like DID numbers, except that they don't necessarily fall into a sequential "block" of numbers. This is DNIS, or Dialed Number Identification Service.

This also means that you need to find out exactly what digits the provider is planning to send for each ported number. Many times, it may be the last 3 or 4 digits on the old number. If that number starts with a 7, 8, or 9, you will have conflicts with the Merlin's existing dial plan, and unless your T1 is a PRI, you can't manipulate those digits. If there is a conflict, many providers are flexible enough to send a string of digits that will route the call to your desired destination.
 
The customer keeps telling me it is not PRI. Their DIDs are 7700-7999 and 4 digits are being sent.
 
You will want to print your existing dial plan, then renumber everything that starts with 7 to something else, like 6. That is, default extensions in the 7100 range, renumber to the 6100 range. Adjuncts from 7300 to 6300. Calling Groups from 770 to 670. etc. Look in your feature reference under dial plan to see a grid of default numbering, so you will see everything that needs changing.
 
gotcha gotcha gotcha. now with that being said. I just found out that 1 of the main lines being ported end in 7700 which is a conflict with their DID. I know renumbering is omething that is system wide. do I just not use their DID 7700 and when I assign 7700 to their DLC hope it's their main line? or is that where the cross connects come in?
 
Well depending on how your client is using the 7700 numbers, if it is their main number, you can assign that to the DLC and you will have two 7700 numbers, one from each NXX code! If that NXX-7700 number you are adding to the Trunk Group is used for something else like a fax or special dept. then you need your Service Provider to change the four digits being sent to something else in your dial plan that works.

I would like you to clarify "lines being ported".

-The term "porting" gets misused these days. It means phone numbers that are "moved" from one provider to another or different CO switch to another using LNP (Local Number Portability).- Changing a phone number from a line to DID is NOT porting!

That being said, you are having phone numbers ported to this service provider and they will arrive as DID numbers in the Trunk Group? Or something else?

When using DS1 with DID the channels/trunks are usually configured as 4-wire E/M wink-start, and can be one-way or two-way. On the Legend/Magix that would be a TIE type configuration. If they are two-way then you can put the trunks in a pool for outgoing access. Since there is NO digit translation for this type of trunking in the Legend/Magix the digits sent are what you get. This is why you need to plan and review this very carefully so you don't have any gotchas! The 408 module you mentioned in your original post, is it going to have any analogue lines on it?

....JIM....
 
I will put the analog lines on their 012 module. their digital phones will go on the 408 gs/ls mlx and 008mlx modules. when I say ported they r moving from one location to another so don't want to loose their established numbers. so they're being sent to their new location with a block of DIDs. now when u say put the trunks in a pool. 70 is usually VM then 890 is usually trunks. with the T1, DIDs and ported numbers should I put the main lines in a pool? I just thought it would be easier when placing on the DLC or anyone covering. there are about 5 main lines. another reply said to put additonal SA buttons which I would make the last 4 of the incoming main numbers. hope I didn't confuse you!! thanks!
 
The analogue CO lines would connect to 5 line/trunk ports on the 408GLM modules NOT the 012 module. The 012 is for analogue STATIONs for things like faxes and 2500 sets. The default pool is usually 70, which is also used with ARS, but because of the DID number conflicts with the Dial Plan the items mentioned in the above posts would apply. So those numbers would change to what ever digit series you pick for that range. Then the channels/trunks on the DS1 would be in another pool depending how you decide to route outgoing calls.

Moving locations is not porting! So you are moving 5 analogue CO lines to a new location. Those lines would have appearances on the DLC along with SA buttons to accommodate the DID calls directed to the DLC. And the actual phone numbers assigned to the 5 CO lines have NO effect on the DID numbers, since those lines are on their own ports and work as standard POTS lines.

....JIM....
 
now that makes total sense to me. 10 years ago I would have lines going in every port that could hold a trunk. at this site that isn't the case. all of their numbers are DIDs and they have no CO lines. I guess times have changed and it's just a little easier.
 
So I take from your response that there are NO analogue lines/trunks going to the 408GLMs? They have a DS1 for all incoming and outgoing traffic. The CO switch is sending 4 digits. So besides the DID block NXX-7700-7999, what are the other numbers that are being added?

....JIM....
 
the random fax and direct lines that are being moved. some are 33xx, 11xx, 4xxx and some are 00xx and 9xxx. I have them giving me other digits for the ones beginning in 0 and 9. the only numbers they don't have are 6xxx and 8xxx which is now part of my system dial plan.
 
Thanks to everyone for their info. The cutover went well thanks to your help. I renumbered everything in the dial plan and did come across some gotchas. First when I switched from PRI to T1 the memory of the B channels stayed behind so I had to go back and delete those. Then when I chose T1 I didn't hit enter after it was selected so I couldn't choose what kind of lines they were. Otherwise..not too shabby. Thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top