Digit Conversion/DCS Elimination/Public Network 1

[GARYGOYKE]

Here's a good one.

Have a Definity Version 4 I believe, it's old, I know that.
So it's not feature rich.

Switch currently has DCS but changed the far end to IP telephone and the Quality of Service on the trunks is horrible. They want to be able to dial a 4 digit extension located at the remote switch and instead of routing it out the DCS trunks, they want to convert the digits to insert the area code and local exchange and route over the public network.

Example:
User dials 4004, system translates to : 9, 4124754004 over the public switched network.

I am thinking that this can be done, but.....I don't have vectoring. This will affect the dialing of about 500 extensions, resulting in all calls going out the public network. I realize that there could be traffic issues involved and alot of translations, but this is what they need to do. The simplest solution, would be to dial the entire 10 digit number to reach the other office, but after 10 years of dialing 4 digits, this is how this has to be done until the quality of service issue is resolved.

The solution that is coming to mind is to set up all of the extensions as local and call forward or remote call coverage them...UGH! Let me know if I am missing something.

 

[Ronster]

I don't know what features you have, but try this:

Change UDP 4

In the UDP table insert AARCode 123 (or something else that won't interfere with other AAR entries) in the appropriate place.

change AAR analysis 123 (123 replaces the first digit of 4004):

          Dialed           Total     Route    Call   Node  ANI
          String          Min  Max  Pattern   Type   Num   Reqd
    123004                6    6     55       aar          n

Change route-pattern 55:

                            Pattern Number: 4

   Grp. FRL NPA Pfx Hop Toll No.  Inserted             
   No.          Mrk Lmt List Del  Digits              
                             Dgts
1: 1    0                    3    94124754

Hope this helps. If you need more detail, let me know.

Cheers, Ronster

 

[Bobg1]

Ronster
could that cause problems with other stations if they are using the 400 series for others?

Gary
Another thing you could try if you want, make 4004 a station, no need to for hardware, then set it to forward to the number. You would have to make sure you use a cor that can forward outside.

 

[GARYGOYKE]

You got me going in the right direction and here is what I did.

The simplest thing for me to do after looking at all of the information given to me was to change the route pattern that existed.

I changed the trunk group to group 1 and deleted 3 digits and inserted the 1412269 and all worked well. I left the internodal routing in there as the backup route since there are only 15 trunks in group 1.
The only other problem that I had was a range of extensions that had a different prefix of 1412375 and I created a seperate route for them. That was the only thing I had to do differently or those calls would have been prefixed by 1412269 and terminated in the wrong place.

Thanks guys, never did too much with AAR until now, and I see exactly how it works, I usually only had to route new extensions to different nodes and never really paid attention to how it all worked behind there.

Thanks again.

Gary

 

[Ronster]

It's perfectly fine just to use AAR to put in specific digits to be translated. This would be what you did if you only have a few 4xxx numbers to be routed elsewhere.

Bob, you're right. Using UDP can interfere with other extensions in the same range. You would use UDP if there was a whole range of numbers you wanted to translate. If Gary wanted to re-route all numbers in the 4xxx range it would be much easier to use UDP. But you can define UDP for a range of 1000 numbers or for a single number. try typing "change UDP 4" and "change UDP 432" to see the difference.

Cheers, Ronnie

PS If you found this helpful a purple star would be appreciated. Ronster