NUMBER-TO-SEND OPTIONS ON PRI ISDN

[SYQUEST]

I am setting up a PRI ISDN on a Legend R6.0. The documents show three options for number-to-send:
Station only, Base Number with Station, or Line Telephone Number.

This system is in Hybrid/PBX mode. It has some non-DID numbers in the Dial Plan and could be an issue with the SID-ANI.

Is it possible to get the base number instead or do you just get an invalid number sent?

The docs are not very clear about this. Is this any different in the Magix software versions?

Thanks in advance for any helpful info!

....JIM....

 

[merlinman]

As many of these as I have implemented in the last couple of years, none of my clients needed anything other than what the Service Provider sent as default.

However, it is my understanding that if the provider is not sending what you want, and they allow you to send your own number (some do not allow this) you can send a certain number for each channel/line that you provide.

As you stated above, this would be what you plug in under Line Telephone Number.

The software for PRI is pretty much the same through the releases from Legend R5 and up.

 

[SYQUEST]

The provider in my case is Pacific Bell, and the SSM that I am working with on the Telco orders said on the PRIs they provision, the customer's equipment can "send any number they want" . So I am trying to figure out what would work in this case. This is what I have to work with:
Main number NPA-871-9300 (LDN)
DID #s NPA-680-8540 - 8559
More DID#s NPA-NXX-?4xx - ?4xx
I am adding more DID numbers and may not be able to get any more "680" numbers that will work. I may end up with another CO code.

Is there any logic to the number-to-send in the Legend?
For example, how does the switch handle all three options if they are all populated?
Does one take priority over another?
I was able to populate all options when programming the Legend last nite.
But I won't know how this will work until the PRI is cutover to service this week.

It would be nice if Avaya and others would make this feature more flexible because of the numbers issues that we have now in the industry, and PRI being much more popular these days.

Let me know your thoughts about this.

....JIM....

 

[merlinman]

I have always been of the understanding that you can choolse 1 and oly one of those options.

If I were to do this, I'd just assign the MAIN LISTED TEL NUMBER to each trunk. I asked my clients at a recent install if they wanted each individuals D-I-D to show up and they said "NOT NOT BUT HECK NO!". It depends on the client.

Also, sometimes it's difficult to massage the MAIN NUMBER & Extension around to send out the D-I-D.

So, as I said, it's usually easier to just assign the MLN to the trunks.

As far as: "It would be nice if Avaya ....", well you can forget Avaya doing any more development on this product.

 

[Pepperz]

You can send the base number, say 987654 + the extension number, tnen if you have 4 digit extensions, it would append the "base number" with the extension number. I have found that this is a little goofy, and must be experimented with a little. One problem you have doing it this way is that even a non-DID extension does the same thing thereby giving a bogus result.
Option 2 is to specify a number for each PRI channel. This works fine, and is not goofy, but it must be entered for each channel.
The ideal way for it to work is that ONLY DID extensions would have dial out access to the PRI, and TELCO says it will support it. (Their role is a little murky, but they do have to allow it)

Pepperzgm at gmail dotte comm

 

[SYQUEST]

How does the Legend handle the feature if all three options are populated?

This system I am working on has 3 digit stations in the Dial Plan and a 3 digit feed from Telco.

....JIM....

 

[Pepperz]

Only one can be activated.

Pepperzgm at gmail dotte comm

 

[SYQUEST]

Well, it took all three!

I guess we will see what happens on Tuesday when I test with Telco.

....JIM....

 

[SYQUEST]

Pepperz is right. It takes only one option, but you can populated all the fields for the lines, number-to-send and base number anyway.

Telco turned up the DS1 early since I had all of my stuff ready, they tested to the CSU. But the SSM moved the DD out because PB had not found any usable numbers yet. So I asked the tester to idle up all the channels so I could test the outgoing side of the PRI and actually see if it would work.

Well after I unbusied the B channels in the Legend, I made call attempts. All I got was fast busies. From RA I got a wierd 5 beep tone I have never heard before in the Legend. So I checked the D channel status in Maintenance and it showed the DCH in maintenance busy mode. I tried restoring to normal but it would not stay! It kept on showing busy mode! Telco said the 5ESS was inservice normal. (I will address this in a new thread).

So I started to review all the parameters and previous posts and the Planning Document to see if I missed something. After reviewing and comparing I found in the CBC service table I had all the patterns set to zero for enrty zero.

Once I fixed those I was able to place outgoing calls. That was all done remotely. Back at the customer location I setup some phones to do further testing and see what I could do with the SID-ANI. This was quite revealing.

Pacific Bell said they don't block ANYTHING! And they don't. The LIDB lookup is really COOL. So any number in the LIDB that has an entry (name) will be sent with the number to the called party from the end office.

I ended up just using the line number for SID-ANI because of the inflexible Legend.

One other interesting thing is when you do RA to the PRI it uses the BTN as the SID-ANI. I guess the Legend sends something in the setup message to the 5ESS to insert the BTN as the SID-ANI, because when I placed a call from an MLX station via the PRI to the called number - nothing showed up on the CID display unit. (I removed all entries prior to both tests).

The cutover went pretty smooth yesterday except for one hiccup from PB. The paper work for the "in order" of the BTN. So the main number was out for about 60 minutes. But all the DID numbers moved flawlessly.

It looks like the CO "Trunk Group" structure for PRI in the 5ESS is very similar to regular DID & SUPERTRUNK trunk groups. They have a Trunk Group Number and a Route Index, But the B channels are in a separate group from the D channel. So for PRI in the 5ESS you have two TGNs and one RI. This is good information to have for maintenance purposes.

PRI is definitely different, very efficient trunking. When you call a number that is busy, it tells the Legend to give busytone and releases the B channel to idle.

Any feedback?

....JIM....