×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

NBX 100 T-1 Digit Counting

NBX 100 T-1 Digit Counting

NBX 100 T-1 Digit Counting

(OP)
Got an NBX 100 sending/recieving inter-office and trunk-to-trunk calls across a PTP T-1. Simple setup, sending/recieving 3 digits for call routing. Remote office has Executone PBX that sends a #-sign to indicate a trunk-to-trunk transfer if the call is originating from an outside line.  Trouble is, I have the T-1 card set up to expect 3 digits, and although the call processor does not view the # as a digit, the T-1 card does. Therefore station-to-station calls go through, inbound calls from telco into remote office destined for local extension cannot be routed to proper extension (too many digits).  Anybody know how to make the T-1 card ignore the #-sign?  Executone says #-sign cannot be suppressed on remote system.

RE: NBX 100 T-1 Digit Counting



try this:

strip the leading digit # in your dial plan for incoming calls hitting the T1 under:

Table Create 2 Incoming DID and Auto Attendant

Then you will need to make a new route to strip the # and you will need to test, test, test to make sure your dial plan is correct on inbound calls at the NBX side


Now that's one way--- if you point the T1 to an automated attendant not being used-- let's say 505 then you could  do so foot work around the AA and get it to route calls but it's cumbersome too.

RE: NBX 100 T-1 Digit Counting

(OP)
Tried the striplead thing - unfortunately the T-1 card is not sending the # to the NCP for processing, so no dialplan or pretranslator entires have any effect.  If (let's say) the remote system is transferring a call to extension 106, it sends #106 across the T.  The T-1 card sees #10 and ignores enaything after that because it has it's expected three digits.  It passes these digits to the call processor, and if you look in the span status under the digital line card, all you get is 10.  The only way I was able to see the # to begin with was through a hyperterm session running on the serial interface of the T-1 card.  Also, since I need three digits to do any kind of routing at all, the AA thing is out because it just sits there waiting for the third digit.  The only thing that I can think of that will fix this issue is to make the T-1 card ignore the #, and I haven't been able to find anything in print that allows you to make any changes to card's behavior. Come on, Big Daddy, there's a $50.00 gift certificate to your favorite restaurant waiting if you can get me out of this one.

RE: NBX 100 T-1 Digit Counting

I am not exper but what are you using for the Network Equip.
Just an adtran TSU..550..or Cisco router?
Is it drop-and-insert or dynamic IP?
You might be able to us the network equip to receive the digits and drop the #. We are doing that with a PTP T1 from an Inter-Tel to a Siemens using adtran 550 (remote) to 880 (host).

RE: NBX 100 T-1 Digit Counting

(OP)
I thought about that, Don, but don't really know if it can be done.  Called Adtran and they didn't seem to think so.  At the remote end is an Atlas 550, and on the NBX side is a TSU 120.  I saw some stuff in the 550 about dial plans and digit filters, but the filter values would only accept numeric values.  It wouldn't take a #.  If you know of something that would do this I could easily cost justify a different channel bank.

RE: NBX 100 T-1 Digit Counting

The STRIP MSD in the Adtran 550 Dial Plan, it takes 1 2 or 3 digits off the front. It doesn't look to see what it is looking at before taking it off.
Again I haven't worked with it I just remember that you could do multi things with the Adtran 550 DP.

RE: NBX 100 T-1 Digit Counting

Here's the example from the 3KB to PRetranslate Inbound Digits on DLCs:

NBX 100, SS 3 NBX - How to pretranslate inbound digits on digital trunks
 
Problem: How to pretranslate inbound digits
 
Fact: NBX 100
 
Fact: SuperStack 3 NBX
 
Fact: NBX Digital Line Card
 
Fact: PRI
 
Fact: T1 (DS1)
 
Fact: Dial Plan
 
Problem: Needs to alter dial plan to convert inbound digits to match internal extension numbers
 
Problem: Needs to create entries to pretranslate in the dial plan
 
Cause: Anytime inbound digits sent from the Telco to the NBX over digital lines are different from the internal extension numbers pretranslation is required. This is configured in the dial plan.
 
Fix: In this example a 4 digit DID inbound to the NBX is manipulated to the internal call flow scheme. When a 4 digit DID beginning with 6 is sent from the Telco, it will be flagged in the top section (PretranslatorEntry Create - entry 1). in the PretranslatorOperation Create the 6 is stripped in OperId 1 and in OperId 2 it is replaced with a 2 - so 6xxx becomes 2xxx. In PretranstorEntry Create entry (2) 6050 is converted to extension 502 in PretranslatorOperation Create entry 2 OperId 1 with the replace function. The numbers used are arbitrary, however by default for all NBX 100's 500 represents the Default Auto Attendant extension even when using a 4 digit dial plan. It is not recommended to change the Default AA, but to create a new Auto Attendant and assign its usage according to your call flow.
/////////////////////////////////////////////////////////////////////////////////
/ Pretranslators
/////////////////////////////////////////////////////////////////////////////////
PreTranslator Create 1 6000 DID to 2000 Internal
/ PreTransId Entry Digits
/ ---------- ----- ------
PreTranslatorEntry Create 1 1 6
PreTranslatorEntry Create 1 2 6050
/ PreTransId Entry OperId Operation Value
/ ---------- ----- ------ --------- -----
PreTranslatorOperation Create 1 1 1 stripLead 1
PreTranslatorOperation Create 1 1 2 prepend 2
PreTranslatorOperation Create 1 2 1 replace 502
/ End of configuration
 

RE: NBX 100 T-1 Digit Counting

I was on vaction BTW--- meal sounds good.

Now- in NetSet/DialPLan/Pretranslators you must select the Pretranslator that you use and then click on Devices Using and move the T1 channels over to USED List (left side) so that the calls are routed.

I posted a HUGE post but this forum limited my post and dropped off several pages...so I will attempt to create what I said in more posts to follow.

RE: NBX 100 T-1 Digit Counting

I have created for someone, somewhere...a 4 digit to 3 Digit Pretranslator.  Now in the below example you will need to create an entry for each DID number.  The NBX DialPlan does not ACCEPT WILDCARDS.  You may want to try out the below and do some test calls to see if you can get it to work with a few extension numbers...remember to match the PRETRANSLATOR TABLE to the T1 channels... you can easily remove the T1 channels from being Devices Using list if it does not work before you spend a lot of time with cutting and pasting entries.....

/////////////////////////////////////////////////////////////////////////////////
/        Pretranslators
/////////////////////////////////////////////////////////////////////////////////

PreTranslator Create 1 #1XX to #2XX
/                         PreTransId Entry Digits
/                         ---------- ----- ------
PreTranslatorEntry Create          1     1 #100
PreTranslatorEntry Create          1     2 #101
PreTranslatorEntry Create          1     3 #102
PreTranslatorEntry Create          1     4 #103
PreTranslatorEntry Create          1     5 #104
PreTranslatorEntry Create          1     6 #105
PreTranslatorEntry Create          1     7 #106
PreTranslatorEntry Create          1     8 #107



/                             PreTransId Entry OperId Operation  Value
/                             ---------- ----- ------ ---------  -----
PreTranslatorOperation Create          1     1      1 replace    100
PreTranslatorOperation Create          1     2      1 replace    101
PreTranslatorOperation Create          1     3      1 replace    102
PreTranslatorOperation Create          1     4      1 replace    103
PreTranslatorOperation Create          1     5      1 replace    104
PreTranslatorOperation Create          1     6      1 replace    105
PreTranslatorOperation Create          1     7      1 replace    106
PreTranslatorOperation Create          1     8      1 replace    107
/
/
/ End of configuration

RE: NBX 100 T-1 Digit Counting

AND BTW- when you used T1 logging and saw the #10 come into the DLC (T1 Card) and nothing more... well you are on a 3 digit dial plan.  So the PRETRANSLATOR may fake the digits coming in (there are four, not three arriving...#1xx and #2xx) to make it work.

If the above method does not work because of the mis-match, 3 digit vs 4 digit dial plan then I say the next thing to try is to convert your 3 digit dial plan to a 4 digit dial plan and you will still need the PReTransLators above.  Try it without converting to a 4 digit dial plan first.  I've got some other tricks that I will post here too.

RE: NBX 100 T-1 Digit Counting

Here's an example of a user wanting a 4 digit extension to work on a 3 digit dial plan:

Goto NetSet/DialPlan/Modify Extensions and click on the phone you want to become FOOD (3663). Now type in 3663 and make sure the menu states: Change Extension.

Now- this guy's phone will almost work.

Look at the Dial Plan below. Also- use a HUNT GROUP for outside callers to reach 3663 (FOOD) which ring to 455 Hunt Group (Calling) and for Call Coverage of 3663 you must use Mailbox 455 (of Hunt Group) so for Phone Number: paste in: 500FAAAAA4#455#*F assuming that your new Hunt Group is 455 if not, change the 455 to whatever. Now time it so that he gets so many rings before call coverage kicks in. Also map the Hunt Group to a feature code and map a MWI button to his/her phone with ext 455 as the value so the Message Lite will lite on the DSS/BLF.

I tested FOOD on an ATA and it works internally okay... oh yeah-- one more thing... you must create a dummy (phantom user) NetSet/User Config/add user and type in the extension number as 366 and the LAST NAME as FOOD. Now goto UserConfig/User Settings for 366 and click on c all forward and for Call Coverage set it to phone number and the value is 455.

Outside callers even if they try to dial 3663 or 366 (any other digit) are going to route as 366...

Bingo.

I knew it could be done...cause I did it for HELP (4357) and I couldn't remember how til today and had one of those senior ah-ha moments.

DIAL PLAN ((excuse the other odd balls)

/////////////////////////////////////////////////////////////////////////////////
/
/ NBX100 Dial Plan Configuration File
/ Generated from machine nbx100 192.168.2.190 owned by Valued Customer 0
/ Generated on THU JUN 03 17:21:30 2004
/
/////////////////////////////////////////////////////////////////////////////////

/ First, delete all existing dialplan information

Table Delete *
DestinationRoute Delete *
TimedRoute Delete *
PreTranslator Delete *

/ Now, create all dialplan information

/////////////////////////////////////////////////////////////////////////////////
/ Settings
/////////////////////////////////////////////////////////////////////////////////

ExtensionLength 3
ExtensionRange Telephone 100 449
ExtensionRange Park 601 619
ExtensionRange AutoAttendant 500 599
ExtensionRange HuntGroup 450 499
ExtensionRange External 600 799
/////////////////////////////////////////////////////////////////////////////////
/ The ExtensionRange External Setting MUST include the Park range.
/ If the Call Park range is outside of the ExtensionRange External,
/ the Call Park feature will not work.
/////////////////////////////////////////////////////////////////////////////////
ExternalSettings 9 750 500

/////////////////////////////////////////////////////////////////////////////////
/ Dial Plan Tables
/////////////////////////////////////////////////////////////////////////////////

Table Create 1 Internal 3 Digit Extensions
/ Id Entry Digits Min Max Class Prio Route
/ -- ----- ------------ --- --- ------------- ---- -----
TableEntry Create 1 1 0 1 1 Internal 0 4
TableEntry Create 1 2 1 3 3 Internal 0 0
TableEntry Create 1 3 2 3 3 Internal 0 0
TableEntry Create 1 4 3 3 4 Internal 0 0
TableEntry Create 1 5 4 3 3 Internal 0 0
TableEntry Create 1 6 5 3 3 Internal 0 3
TableEntry Create 1 7 6 3 3 Internal 0 0
TableEntry Create 1 8 7 3 3 Diagnostics 0 0
TableEntry Create 1 9 9 8 11 Local 0 1
TableEntry Create 1 10 90 2 64 Operator 0 1
TableEntry Create 1 11 901 4 64 International 0 1
TableEntry Create 1 12 91 9 12 LongDistance 0 1
TableEntry Create 1 13 9101 9 64 AlternateLong 0 1
TableEntry Create 1 14 911 3 3 Emergency 0 2
TableEntry Create 1 15 91800 12 12 TollFree 0 1
TableEntry Create 1 16 91888 12 12 TollFree 0 1
TableEntry Create 1 17 91877 12 12 TollFree 0 1
TableEntry Create 1 18 91900 12 12 Toll 0 1
TableEntry Create 1 19 91976 12 12 Toll 0 1
TableEntry Create 1 20 9911 4 4 Emergency 0 1
TableEntry Create 1 21 9411 4 4 Operator 0 1
TableEntry Create 1 22 9* 4 4 COCode 0 1
TableEntry Create 1 23 8 11 11 Local 0 8
TableEntry Create 1 24 80 2 64 Operator 0 8
TableEntry Create 1 25 801 4 64 International 0 8
TableEntry Create 1 26 81 9 12 LongDistance 0 8
TableEntry Create 1 27 8101 9 64 AlternateLong 0 8
TableEntry Create 1 28 81800 12 12 TollFree 0 8
TableEntry Create 1 29 81888 12 12 TollFree 0 8
TableEntry Create 1 30 81877 12 12 TollFree 0 8
TableEntry Create 1 31 81900 12 12 Toll 0 8
TableEntry Create 1 32 81976 12 12 Toll 0 8
TableEntry Create 1 33 8911 4 4 Emergency 0 8
TableEntry Create 1 34 8411 4 4 Operator 0 8
TableEntry Create 1 35 8* 4 4 COCode 0 8
TableEntry Create 1 36 300 3 15 Toll 0 9
TableEntry Create 1 37 301 3 15 Toll 0 10
TableEntry Create 1 38 1300 3 15 Toll 0 9
TableEntry Create 1 39 1301 3 15 Toll 0 10
TableEntry Create 1 40 333 3 4 Internal 0 11
TableEntry Create 1 41 303 3 3 Internal 0 12
TableEntry Create 1 42 361 3 3 Internal 0 13
TableEntry Create 1 43 1361 3 3 Internal 0 13

Table Create 2 Incoming DID and Auto Attendant
/ Id Entry Digits Min Max Class Prio Route
/ -- ----- ------------ --- --- ------------- ---- -----
TableEntry Create 2 1 0 1 1 Internal 0 4
TableEntry Create 2 2 1 3 3 Internal 0 0
TableEntry Create 2 3 2 3 3 Internal 0 0
TableEntry Create 2 4 3 3 3 Internal 0 0
TableEntry Create 2 5 4 3 3 Internal 0 0
TableEntry Create 2 6 5 3 3 Internal 0 3
TableEntry Create 2 7 300 3 3 Internal 0 9
TableEntry Create 2 8 301 3 3 Internal 0 10
TableEntry Create 2 9 1300 3 3 Internal 0 9
TableEntry Create 2 10 1301 3 3 Internal 0 10
TableEntry Create 2 11 333 3 3 Internal 0 11
TableEntry Create 2 12 303 3 3 Internal 0 12
TableEntry Create 2 13 361 3 3 Internal 0 13
TableEntry Create 2 14 1361 3 3 Internal 0 13
TableEntry Create 2 15 3663 3 3 Internal 0 14

Table Create 3 Least Cost Routing

Table Create 4 Table Name

Table Create 5 Copy of Table Name

/////////////////////////////////////////////////////////////////////////////////
/ Routes
/////////////////////////////////////////////////////////////////////////////////

/ Route Description
/ ----- -----------
DestinationRoute Create 1 LocalCO
DestinationRoute Create 2 LocalCONoStrip
DestinationRoute Create 3 Voice Application
DestinationRoute Create 4 Attendant
DestinationRoute Create 5 H323 ConneXtions Ports
DestinationRoute Create 6 Virtual Tie Line (VTL) Ports
DestinationRoute Create 7 Reserved
DestinationRoute Create 8 8 Pool
DestinationRoute Create 9 RAD
DestinationRoute Create 10 Cell Phone
DestinationRoute Create 11 Park1
DestinationRoute Create 12 AliSecy
DestinationRoute Create 13 Transfer to Ed
DestinationRoute Create 14 Transfer to FOOD

/ Route Entry DestinationExtension
/ ----- ----- --------------------
DestinationRouteEntry Create 1 1 *0001
DestinationRouteEntry Create 1 2 *0002
DestinationRouteEntry Create 2 1 *0001
DestinationRouteEntry Create 2 2 *0002
DestinationRouteEntry Create 3 1 *0003
DestinationRouteEntry Create 4 1 *0004
DestinationRouteEntry Create 5 1 *0005
DestinationRouteEntry Create 6 1 *0006
DestinationRouteEntry Create 7 1 *0003
DestinationRouteEntry Create 8 1 *0008
DestinationRouteEntry Create 9 1 *0001
DestinationRouteEntry Create 10 1 *0001
DestinationRouteEntry Create 11 1 *0003
DestinationRouteEntry Create 12 1 *0000
DestinationRouteEntry Create 13 1 *0001
DestinationRouteEntry Create 14 1 *0000

/ Route Entry OperId Operation Value
/ ----- ----- ------ --------- -----
DestinationRouteOperation Create 1 1 1 stripLead 1
DestinationRouteOperation Create 1 2 1 stripLead 1
DestinationRouteOperation Create 8 1 1 stripLead 1
DestinationRouteOperation Create 9 1 1 replace ,,
DestinationRouteOperation Create 10 1 1 replace ,3018441212
DestinationRouteOperation Create 11 1 1 replace #444,601
DestinationRouteOperation Create 12 1 1 replace 454
DestinationRouteOperation Create 13 1 1 replace ,2407934435
DestinationRouteOperation Create 14 1 1 replace ,455

/////////////////////////////////////////////////////////////////////////////////
/ Pretranslators
/////////////////////////////////////////////////////////////////////////////////

PreTranslator Create 1 4Digit DID 3Digit Internal
/ PreTransId Entry Digits
/ ---------- ----- ------
PreTranslatorEntry Create 1 1 1
PreTranslatorEntry Create 1 2 2
PreTranslatorEntry Create 1 3 3
PreTranslatorEntry Create 1 4 4
PreTranslatorEntry Create 1 5 5
PreTranslatorEntry Create 1 6 6
PreTranslatorEntry Create 1 7 7
PreTranslatorEntry Create 1 8 8
PreTranslatorEntry Create 1 9 9
PreTranslatorEntry Create 1 10 0


/ PreTransId Entry OperId Operation Value
/ ---------- ----- ------ --------- -----
PreTranslatorOperation Create 1 1 1 stripLead 1
PreTranslatorOperation Create 1 2 1 stripLead 1
PreTranslatorOperation Create 1 3 1 stripLead 1
PreTranslatorOperation Create 1 4 1 stripLead 1
PreTranslatorOperation Create 1 5 1 stripLead 1
PreTranslatorOperation Create 1 6 1 stripLead 1
PreTranslatorOperation Create 1 7 1 stripLead 1
PreTranslatorOperation Create 1 8 1 stripLead 1
PreTranslatorOperation Create 1 9 1 stripLead 1
PreTranslatorOperation Create 1 10 1 stripLead 1

/ End of configuration

Step 1: Goto NetSet/DialPlan/Modify Extensions and click on the phone you want to become FOOD (3663). Now type in 3663 and make sure the menu states: Change Extension.

Step 2: Goto NetSet/DialPlan/Export - save your dial plan (backup first) then open up the copy of it and change:

a)TableEntry Create 1 4 3 3 4 Internal 0 0 (you are making the MAX number of digits = 4 (was 3)

b)TableEntry Create 2 15 3663 3 3 Internal 0 14 (This entry under Table 2 DID)

c)DestinationRoute Create 14 Transfer to FOOD (route Description)

d)DestinationRoute Create 14 Transfer to FOOD (Routes)

e)DestinationRouteEntry Create 14 1 *0000 (Route Destination)

f)DestinationRouteOperation Create 14 1 1 replace ,455 (Route Operation)

Make these changes and SAVE as different file name (FOOD or something identifibale) then import to your NBX Dial Plan

Now:

Set Call Coverage of 3663: you must use Mailbox 455 (of Hunt Group) so for Phone Number: paste in: 500FAAAAA4#455#*F assuming that your new Hunt Group is 455. ALSO DO THE SAME FOR THE HUNT GROUP 455... you MUST paste in 500FAAAAA4#455#*F and change your timers to 12 seconds for a few rings before Call Coverage is invoked. The ext 3663 is A MEMBER of HG 455 and Logged IN/Locked.

Also map the Hunt Group to a feature code.

Map a MWI button to his/her phone with ext 455 as the value so the Message Lite will lite



Under this setup when I dial 3663 it rings an ATA port (old ext # 200) and since Call Coverage for 3663 is HG 455 that's where the internal caller ends up if the user 3663 does not answer. Then dialing from the 500 AA/Menu if I dial 366, 366x then the caller rings the station and after the timeout period for the HG 455 expires, the call goes into voice mail box of 455.

This works on my system and I'm running OS 4.1.77

Now if you want to use a Phantom...I suggest you get it to work on hardwired phone first then play to use just a phantom which whould also work.


This line of thought is to use as a reference... stick again with the PreTranslators above and hopefully- those will work for your T1 getting the # as the first digit.  The NBX must receive the # sign !

Why ?

Think about your AA function of #.  If the NBX does not process # then it's not in compliance with the NANDP (North American Network Dial Plan).

The dial plan manipulations using PreTranslators should work.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close