Incomming DID's to a RAN

[GHCSCOMM]

We have an CS1000M 7.0 with two Verizon DID PRI’s. We are changing telephone exchanges, I need a easy way to take all the incoming numbers ( approx. 6000 ) to this route and send them to a RAN indicating the exchange has changed and to call the new number. If I give them an intercept treatment will it do the same for internal calls? IDC table is a lot of programming. Any ideas Thanks.

 

[bigindian65]

it will not do the same for internal there is a DID field and a Station field as 2 of the 4 fields for each type in int data block

Mato' Was'aka

 

[GHCSCOMM]

Ok then now how do I get the DID's to the intercept treatment? Change the LDN from 4 to 5 digits? Will that affect internal or point to point calls?

 

[bigindian65]

could just use vacant number routing and send DID call to RAN in INT_DATA

Mato' Was'aka

 

[GHCSCOMM]

Yes, but how do I get the DID calls to the vacant number routing
I have INT_DATA set to CTVN (ovf ovf ovf ran).

 

[jaxuser]

Check this out...if you want all call types to go to RAN then CTVN = ran ran ran ran
next prompt would be your ran route number.
This will play the ran for callers and they will have to hang up and dial the new number.

LD 15: Customer Data Block
Prompt Response Comment Pack/Rel

Intercept treatments determine the action
performed when a user makes an invalid call.

Each intercept prompt requires four entries
representing the type call:

INTR (NO) YES
• first entry = station/DISA
• second entry = attendant extended
• third entry = TIE trunk
• fourth entry = CCSA/DID trunk

One of the following responses is required for
each entry:
• ATN = Intercept to Attendant
• BSY = Busy Tone
• NAP = Not Applicable
• OVF = Overflow Tone
• RAN = Intercept to Recorded Announcement
• SRC1-SRC8 = Announcement Source
Channel
The defaults are shown for each Intercept prompt.
If RAN is specified, you are prompted for the RAN
route number.

 

[NortelGuy1979]

If I read this right, the question is, the NPA and DID are staying the same, but the NXX is changing. So what used to be 310-555-1212 will now be 310-666-1212. However, VZ is sending 4D dialed number for both NPA-NXX, so the PBX thinks they are correct.

You need to have your telco send a different number of digits on the old NXX (probably 5, if they can) and then the PBX will give intercept treatment, which you can send to fast busy, RAN, etc.

For Paetec, I think it's called FlexDNIS where they can send varying digit lengths on the same route; you'll have to ask your provider.

Matthew - Technical Support Engineer Sr.

http://www.linkedin.com/in/matty79

 

[GHCSCOMM]

My issue is these numbers are at the moment working DID/Internal numbers. How do I get the DIDs that have programmed numbers to the intercept treatment? I have at the moment the old DID exchange is in one route while the new exchange is on another route. Both exchanges are working at this time. I need to find a way to intercept the old exchange route only.

 

[NortelGuy1979]

So have the provider change the number of digits on the old PRI that the old NXX comes in on - presto, you'll get intercept. Just like I wrote above.

Matthew - Technical Support Engineer Sr.

http://www.linkedin.com/in/matty79

 

[GHCSCOMM]

I'm actually recieving 7 digits from Verizon. LDN is set for 2000 ( 4 digits ). Can I just set the LDN to 20000 ( 5 digits ) making it a vacant number.

 

[GHCSCOMM]

They want to charge us big time for that. I was hoping I could do something with the switch.

 

[NortelGuy1979]

Can you print both RDB, and show an inbound call on both routes? Also your LDN_DATA block? If you're receiving 7 digit on both routes, but have 4 digit extensions, and you change the LDN to 5 digits, then everything will intercept unless your extensions are 5 digits.

Am I correct that only the NXX is changing, but the NPA and DID extension are remaining the same? So either way VZ is sending the call is currently valid?

If they're sending 7D on both spans, then build an IDC on the "old" span that converts. Assume your NPA-NXX is 310-555 and you have DID in 1xxx, 2xxx, 3xxx, 4xxx, 5xxx, 6xxx (6000 DID). Assume your new NPA-NXX is *not* 310-777

IDGT 5551
5551 7771
IDGT 5552
5552 7772
(etc thru 5556)
Then it's an invalid number, and you'll intercept. At least in theory; I've not tried it and we don't have the DID facilities in our lab for me to test...

If that doesn't work or my assumption on your issue isn't correct, we need more details

Matthew - Technical Support Engineer Sr.

http://www.linkedin.com/in/matty79

 

[GHCSCOMM]

If the carrier send us more digits the switch is only going to see the last 4 with a LDN of 4 digits correct

 

[GHCSCOMM]

Yes only the NXX is changing. The old DID exchange route is in switch "A" the new DID exchange route is in switch "B" and route the necessary numbers over to "A" via a TIE PRI.

 

[NortelGuy1979]

Per the NTP:
LDN0 must be defined for ISDN PRI DID service.
The length of LDN0 determines the number of
trailing digits translated as the dialed DN on PRI
DID routes.

That being said - you can override it with IDC and translate the leading digits.

Matthew - Technical Support Engineer Sr.

http://www.linkedin.com/in/matty79

 

[GHCSCOMM]

I will try changing the LDN in switch "A" and see what happens. I cringe at having to set up IDC for all those numbers.

 

[NortelGuy1979]

Since they're separate swwitches, you're fine changing the LDN in switch A. That little part was omitted. However depending on your tieline type, you may run into a problem there... you don't have to make 6000 IDC entries. Only one for each leading set of digits. If all your old NXX are 555-1xxx, 2xxx, 3xxx, 4xxx, for example, then you're just going up to 6 entries. You can do partial DID translation.

Partial Digit Conversion
Not all of the digits received from the Central Office (CO) are converted.
The remaining digits may remain unchanged, and the whole string of digits
is forwarded to the Directory Number (DN) translator.
It is possible to convert a partial string of digits to another partial string of
digits of a different length (for example, 23xx to 4xx or 2xx to 49xx). The
range of DNs to convert can include a mix of DN lengths.

Matthew - Technical Support Engineer Sr.

http://www.linkedin.com/in/matty79

 

[GHCSCOMM]

Thanks everyone. I did an IDC table to RAN route.