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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Magix 4.0 - How to change outbound CLID to match DID number?
- Thread starter IPOJIM
- Start date
tdaugirdas
Technical User
You can program outbound caller ID under lines/trunks, PRI, Numbr to Send, Line Telephone Number, enter - then enter the 1st B channel line tunk and key in the 10-digit number to send with no spaces or dashes. You can also send the equivalent of the DID number per extention (under the Base Number with Ext option). However - you have to first see if the Telco will accept your "outbound" caller ID info - and they have to flip a switch to allow it.
The typical default for all of your B channels is the main number for the company.
Normally - you can ONLY send outbound caller ID for numbers that are ported and/or part of the inbound DID range. You CANNOT send anything else - such as a "blank", a number not proted through your PRI service, etc..
Tom Daugirdas,
President
STCG, Inc.
stcg.com
The typical default for all of your B channels is the main number for the company.
Normally - you can ONLY send outbound caller ID for numbers that are ported and/or part of the inbound DID range. You CANNOT send anything else - such as a "blank", a number not proted through your PRI service, etc..
Tom Daugirdas,
President
STCG, Inc.
stcg.com
This feature is VERY limited. If all your numbers, DID and MAIN are the same NPA-NXX and all your stations have DID assignments, then it will probably work for your system.
BUT, if you have ANY variation in the above requirements, you will have problems!! Any non-DID station's CLID will consist of the NPA-NXX plus the non-DID station number. So when a call is placed by that station, that number shows on the called party's Caller ID box. If the NPA-NXXs are different for the DIDs and MAIN number, you can only have one choice!
Avaya never did their homework to fix this problem on the Magix! It is the same on the Legend. No flexiblity at all!!!
....JIM....
BUT, if you have ANY variation in the above requirements, you will have problems!! Any non-DID station's CLID will consist of the NPA-NXX plus the non-DID station number. So when a call is placed by that station, that number shows on the called party's Caller ID box. If the NPA-NXXs are different for the DIDs and MAIN number, you can only have one choice!
Avaya never did their homework to fix this problem on the Magix! It is the same on the Legend. No flexiblity at all!!!
....JIM....
- Thread starter
- #4
Jim,
Sorry not know what NPA-NXX refers to. Most of the numbers are DID there with the same area code but with two possible prefixes, 272 and 292. There are four presented digits and they match the extension numbers (last 4). Can you advise on the definition of NPA-NXX and how it applies to the info in this post? Thanks for helping - Jim V
Sorry not know what NPA-NXX refers to. Most of the numbers are DID there with the same area code but with two possible prefixes, 272 and 292. There are four presented digits and they match the extension numbers (last 4). Can you advise on the definition of NPA-NXX and how it applies to the info in this post? Thanks for helping - Jim V
tdaugirdas
Technical User
If the exchanges are different (272 and 292) - and the DID ranges do not overlap - then you can only send your main number - which is probably what is happening now anyway.
If EACH DID range covers ALL of your extentions - then you should be able to use the Base number with extention option - however - you will only be able to use a single prefix (either 272 or 292) - but not both of them.
Tom Daugirdas,
President
STCG, Inc.
stcg.com
If EACH DID range covers ALL of your extentions - then you should be able to use the Base number with extention option - however - you will only be able to use a single prefix (either 272 or 292) - but not both of them.
Tom Daugirdas,
President
STCG, Inc.
stcg.com
- Thread starter
- #6
tdaugirdas
Technical User
Yes - they are - so that should work. But -remember you need to call your Telco first - to even find out if their switch can accept outbound caller ID from the Legend - and you need to preprogram it BEFORE they flip the switch - or your T1's will be unable to make any outbound calls.
Tom Daugirdas,
President
STCG, Inc.
stcg.com
Tom Daugirdas,
President
STCG, Inc.
stcg.com
The official name for an Area Code is Numbering Plan Area or NPA, and for Central Office Code is NXX (prefix or exchange code), refering to the digits N = 2 thru 9, X = 1 thru 0. If you want to find out more visit NANPA's website nanpa.com NANPA is North American Numbering Plan Administration.
Going back to the question at hand, if your DID numbers for 272 and 292 come in on different PRIs that may work by setting up each PRI accordingly to send number by station. I have never tried it this way, because all the Legend/Magix I have worked on have only one PRI. So you will have to experiment with the PRIs to see what the limitations are with multiple PRIs on the switch.
Are the DID numbers for 272 coming in on one PRI and the 292s on the other? Or are they all coming in on both PRIs?
How Telco routes the DID numbers will make a difference. You will want them as separate Trunk Groups in the CO switch, which means your PRIs will be separate from that side of the facility.
One point of information, the term "ported" or "porting" only refers to telephone numbers that are using Local Number Portability or LNP, when you change service providers or switches and take your numbers with you, not when routing DID numbers to a facility, like PRI or on DS1.
By the way, if your service provider is the current AT&T footprint, they are not restricting numbers to send on PRIMARY ISDN.
....JIM....
Going back to the question at hand, if your DID numbers for 272 and 292 come in on different PRIs that may work by setting up each PRI accordingly to send number by station. I have never tried it this way, because all the Legend/Magix I have worked on have only one PRI. So you will have to experiment with the PRIs to see what the limitations are with multiple PRIs on the switch.
Are the DID numbers for 272 coming in on one PRI and the 292s on the other? Or are they all coming in on both PRIs?
How Telco routes the DID numbers will make a difference. You will want them as separate Trunk Groups in the CO switch, which means your PRIs will be separate from that side of the facility.
One point of information, the term "ported" or "porting" only refers to telephone numbers that are using Local Number Portability or LNP, when you change service providers or switches and take your numbers with you, not when routing DID numbers to a facility, like PRI or on DS1.
By the way, if your service provider is the current AT&T footprint, they are not restricting numbers to send on PRIMARY ISDN.
....JIM....
memphisribs
Vendor
Sorry but the Number to send is system wide not by PRI cards
You are out of luck
43 years in the business and counting.
You are out of luck
43 years in the business and counting.
tdaugirdas
Technical User
Well - It may not work - as noted by Memphismribs. I have never tried it with two different prefix exchanges. However - as I noted - if the DID ranges overlap, i.e, the 272 range is 2100-2199 and the 292 range is similar - like 2300-2399 - so basically the calls all route to the same extention based on the last 4 digits - you could pick a single extention range (starting with 272 or 292) to send as outbound caller ID.
Tom Daugirdas,
President
STCG, Inc.
stcg.com
Tom Daugirdas,
President
STCG, Inc.
stcg.com
Ok...here is what I have done in the past. You could assign half of your B-channels into one pool, and the other half into another pool. Let's use 70 and 890. Then you would assign the B channels in pool 70 to outpulse the 272 numbers and use pool 890 to outpulse the 292 numbers, either by extension or however you choose. Then, using ARS, you would assign pool 70 as an outgoing route in table 25 and table 26 (assuming you have a Magix) as route 1 and assign it a FRL of 4. Then assign pool 890 as route 2 and assign it a FRL of 3. Next thing you would do is assign change the FRL restrictions of all the extensions dialing out with the 272 number to a FRL of 4. Here is what would happen, and extension dialing out with a 272 number would hit route 1 and be able to dial out, using the B channels with the outpulse digits that you set up with 272. Any extension that has a 292 number would try to dial out could not dial out over route 1 because of its low FRL, it would be forced to dial out over route 2, pool 890, using the outpulse digits that you set up for the B-channels in pool 890. This is a little advanced but it does work. some conflicts you might run into is if pool 70 is busy or oos, any extension with a 272 number would still be allowed to dial out over route 2, causing a conflict. I pre-warn my customers that this might happen, but probably will be rare. There is way to many programming sequences to go through here....if you are willing to continue with this..I will post them for you.
A.J. Wiesner
AT&D Communications
A.J. Wiesner
AT&D Communications
- Thread starter
- #12
Thanks, AJ, Tom, and Jim. I will be getting over to the site in the next week to lay out the findings here to the management, they can decide how they want this handled. From what I learned here, staying with one NXX is preferable, somehow they got a new range of numbers on the new NXX so maybe we can revisit finding numbers on the primary NXX even if they are not sequential and retire the new ones quickly. More to come as I run this past them next week. Thanks again! Jim V (IPOJIM)
blinking123
Technical User
Using the instructions provided here, we've updated our 'number to send' to base + extension and yippee! our outbound caller id finally reflects the DID (which matches the extension).
But our outcalling stopped working. Our outcalling extensions are 7128, 7129, 7130 & 7130 - and our DIDs (extensions) are 5000 to 5499. Do I need to change the VM extensions to something in the 5000 to 5499 range?
Much obliged for all of your enormobrains...
Annie
But our outcalling stopped working. Our outcalling extensions are 7128, 7129, 7130 & 7130 - and our DIDs (extensions) are 5000 to 5499. Do I need to change the VM extensions to something in the 5000 to 5499 range?
Much obliged for all of your enormobrains...
Annie
I have ran into this before. I believe the Vendor was QWEST.
Who knew the Phone Company was so smart?
You will have to change your OUT-CALLING extensions to match something in your D-I-D range.
Hopefully, you have some available D-I-D's in your range.
Who knew the Phone Company was so smart?
You will have to change your OUT-CALLING extensions to match something in your D-I-D range.
Hopefully, you have some available D-I-D's in your range.
annesmith,
Who is your service provider?
The problem with the LEGEND/MAGIX is, there is NO allowance for non-DID stations when using "base + station" number for CLID. Unless the provider's switch is blocking, the call should go thru. What will display on the CID in that case, is the NPA-NXX+ whatever station number is assigned. So if your provider is blocking anything other than your DID & pilot number if provided, then that may cause calls to be blocked. It would be telling if you could place outbound test calls on the VM ports and see what happens.
Pacific Bell/SBC/AT&T(current ILEC name) does not block on any PRIMARY ISDN.
....JIM....
Who is your service provider?
The problem with the LEGEND/MAGIX is, there is NO allowance for non-DID stations when using "base + station" number for CLID. Unless the provider's switch is blocking, the call should go thru. What will display on the CID in that case, is the NPA-NXX+ whatever station number is assigned. So if your provider is blocking anything other than your DID & pilot number if provided, then that may cause calls to be blocked. It would be telling if you could place outbound test calls on the VM ports and see what happens.
Pacific Bell/SBC/AT&T(current ILEC name) does not block on any PRIMARY ISDN.
....JIM....
blinking123
Technical User
Me'thinks not being able to make any outbound calls probably doesn't have anything to do with Number to send, but thought I'd ask:
We just installed a new block of DIDs:
Existing block: 401-264-5000 thru 5039
New block: 401-263-5250 thru 5269
re-numbered a non-used extension 5003 (is able to make outbound calls as 5003) to 5250.
We were using "base plus ext" number to send, but the new 263-5250 is unable to make any outbound calls.
Changed to "Line number to send" but still not able to make outbound calls from the new 5250 extension.
While I love listening to the Magix error warbling, the other staffers are getting annoyed. Any suggestions where I might find the problem would be greatly appreciated.
We just installed a new block of DIDs:
Existing block: 401-264-5000 thru 5039
New block: 401-263-5250 thru 5269
re-numbered a non-used extension 5003 (is able to make outbound calls as 5003) to 5250.
We were using "base plus ext" number to send, but the new 263-5250 is unable to make any outbound calls.
Changed to "Line number to send" but still not able to make outbound calls from the new 5250 extension.
While I love listening to the Magix error warbling, the other staffers are getting annoyed. Any suggestions where I might find the problem would be greatly appreciated.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question