1010 Dialing is Costing Us Money 1

[joembass]

We switched our Hospital over to SBC thais past January.

However, we are still getting bills (to the tune of $1,700.00) per month.

SBC says the problem is in our Definity setup.

I looked and sure enough there seems to be a proble, but I don't know how to get rid of it.

I have 4 route patterns, but only 2 with a 1010 number inserted into them. Here's what they look like...

Route Patterns 1 & 4 seem to be the problem.

Display route-pattern 1

Grp# FRL Pfx # Inserted
Mk Digits Digits
1: 2 4 1 1 1010XXXX
2: 1 5 1 1 1010XXXX


Display route-pattern 4

Grp# FRL Pfx # Inserted
Mk Digits Digits
1: 2 4 1 1010XXXX
2: 1 5 1 1010XXXX

The route-patterns below seem to work fine.

Route Pattern 2

Grp# FRL Pfx # Inserted
Mk Digits Digits
1: 2 0
2: 1 5


Route Pattern 3

Grp# FRL Pfx # Inserted
Mk Digits Digits
1: 2 0 1
2: 1 5 1


I would appreciate any help anyone can give me.

joe

 

[Dunstan]

Unless you want people to be able to manually PIC (Dial 1010 numbers) then you should remove those entrys or deny them. I cannot think of a business where it would be a good idea to even allow that.

Also ask SBC to put a PIC freeze on your circuits (this should stop any slamming).

In short unless you want the users to be able to pick their LD carrier just remove the 1010xxxx from the inserted numbers section on the RP

 

[joembass]

How do I remove the numbers?

 

[bdelmar]

do a change route-pattern and you'll be able to remove the 1010xxxx

 

[joembass]

Do I remove the 1010 numbers and leave all of the other sttings alone?

 

[bdelmar]

yes, just remove the "1010xxxx".

 

[Dunstan]

remove ecrything under the "inserted digits" section in the route pattern and then place a test call.

 

[joembass]

Thanks bdelmar & Dunstan. I'll try this and get back to you both.

joe

 

[mikeydidit]

Their is another alternative to consider. We use a service provided by Spectracorp. We actually get paid for these types of calls and provide our patients with a less expensive means of calling loved ones from our hospital while doing so. For more information call them @ 1-800-375-7945.

Mike Jones
Louisiana State University Health Sciences center

 

[joembass]

Thanks Mike. I'll look into Spectracorp.

I've read lots of your posts, and have learned a lot from them.

 

[joembass]

As a side note, to my 1010 dilemma, I wanted you all to know that I have already done the following;

Reconfigured Route-Patterns 1 & 4 (The ones with the 1010 routing) to be identical to Route-Patterns 2 &3 , and deleted the 1010 numbers in the Inserted-Digits field.

This did not work, but if what you're suggesting is to just delete the 1010 fields (and that's all) for Route-Patterns 1 & 4 (the bad route-patterns), then I'll try that and see how it works.

Thanks,

joe

 

[mikeydidit]

Glad I could help Joe. It's great to have a centalized place for so many to turn to for help with their systems. Spectracorp can guide you through the route patterns, and can also provide help with (0) operator assisted calls too.

Have a good one.

Mike Jones
Louisiana State University Health Sciences center

 

[TivoNut]

The best way to do this is to change the ARS table to deny access to any route table. It's quick and easy and you don't have to mess with the route patters.

Do "change ars ana 1"

You'll see something similar to:

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
101xxxx0 8 8 p1 op n
101xxxx0 18 18 p1 op n
101xxxx01 16 24 p1 iop n
101xxxx011 17 25 p1 intl n
101xxxx1 18 18 p1 fnpa n
10xxx0 6 6 p1 op n
10xxx0 16 16 p1 op n
10xxx01 14 22 p1 iop n
10xxx011 15 23 p1 intl n
10xxx1 16 16 p1 fnpa n

Change the "Route Pattern" for any and all of these to "deny" and save the change. Problem solved. When you're done, it will look like this below:

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
101xxxx0 8 8 deny op n
101xxxx0 18 18 deny op n
101xxxx01 16 24 deny iop n
101xxxx011 17 25 deny intl n
101xxxx1 18 18 deny fnpa n
10xxx0 6 6 deny op n
10xxx0 16 16 deny op n
10xxx01 14 22 deny iop n
10xxx011 15 23 deny intl n
10xxx1 16 16 deny fnpa n

 

[TivoNut]

I may have misunderstood the problem initially. Do you have users dialing 1010 codes (which my suggestion will stop) or is the switch inserting 1010 codes on all outbound calls? If it's the latter, then you do need to remove the Inserts from the route patterns, and make sure your calls are going over the correct SBC trunk group. We have separate local and LD SBC trunk groups on our switch.

 

[joembass]

Hi TivoNut,

No. Users are not dialing the 1010 number. The 'system' is evidently automatically inserting the 1010 acces number when the offnet by dialing 9.

So, if I understand you correctly, the ONLY thing I have to do is just delete the 1010XXXX in the "Inserted Digits" field?

The only trunks I have are;

Trunk 1 - "Hospital"
TAC=101 Group=co, # of Members=7, COR=1, CDR=y
Trunk 2 - "Hospital Out"
TAC=102 Group=co, # of Members=10, COR=1, CDR=y
Trunk 3 - "Hospital Direct In"
TAC=103 Group=did, # of Members=6, COR=1, CDR=y
Trunk 4 - "Hospital Direct In Dial"
TAC=104 Group=did, # of Members=4, COR=1, CDR=y

The route patterns are as described in my first post. Route Patterns 2 & 3 work fine, and are not 'programmed' with 1010 numbers.

Route patterns 1 & 4 are my bad boys, and since Ttunk 1 is 'co', and Trunk 4 is a did, doesn't that mean that my real problem is Trunk 1??

Why would anyone put 1010 numbers on a did trunk??

 

[TivoNut]

Yes, simply removing all of the inserted digits will pass the dialed number, unaltered, to the trunk line. Whatever LD you have PIC'd to the line will take the call. The 1010 codes override the default PIC, so that is definitely the problem.

As to why, could be any number of reasons. Perhaps this was cheaper at one time. Perhaps whoever configured it was getting a kickback of some sort. Who knows, but 1010 codes really aren't needed today with all the deals out there. I only use them in occasional testing.

 

[Dunstan]

Like we stated earlier if you want to stop people from having this access remove the inserted digits portion on your RP/TG's.

If you want to further restrict this you can ask your carrier SBC I think you said for a "Pic Freeze" on your account. Keeping people from inadvertantly switching your services.

 

[joembass]

It didn't work.

First, I deleted the 1010 numbers in the 'Inserted Digits' field on Route-Patterns 1 & 4. Within 30 minutes people were calling me about not being able to make long distance calls.

I then returned everything to the way it was before.

Then I went to Route-Pattern 1 and deleted the '1' in the '# Digits' column and the 1010XXXX in the 'Inserted Digits' column.

Again no luck. So I returned everything back to normal until I get some input.

Thank you,

joe

 

[Dunstan]

Joe,

I was trying to tell you to test the calls after you make the changes lol. Never make RP or TG changes without testing them....

Some suggestions.

Depending on your release of software you can do the following (post release 9ish I think).

Step one
While at your terminal.....and near a phone type

"list trace station xxxx" (insert the phone extension you are using where the x's are).

Pick up the receiver and place a long distance call to any number that would route over those tg's and RP's.

Print the screen or save it so you can post it back here...The list trace will show you how the call went out etc and help us help you troubleshoot.

Next remove the 1010xxxx from the inserted digits section (bear with me I know you did this already).

Now do a second "list trace station xxxx" on the same extension you used last time and try to dial the same number again (You said that people couldn't get out so do this only long enough to run the trace on one call then re-insert your 1010xxxx string as it was before).

Now post both the first call list trace here in this thread along with the second call (which I assume will be a call that was blocked based on you saying end users couldnt call out after you remove the inserted digits).

We (people who frequent the boards here) should be able to tell you why it is being blocked or what the problem is based on the two different call traces you post and rec a solution.

I want you to know that it is not common (at least in my 15+ years of PBX work) to have to put 1010 aka pic codes into a rp or TG....While it may be common for some types of busineses it is not overall something you normally see in an outbound TG to the PSTN.

The reason for this is most carriers can handle this on the CO side and most businesses I have worked with prefer to lock down who carries their LD traffic for precisely the reason you are posting here...

If you want the easiest fix without getting to the root of the problem with the TG's and doing list traces then you can do one simple thing.

Call your LD carrier ask them what they want you to use as a PIC code on LD traffic and simply put that number behind the 1010 portion of the inserted digits i.e. 1010321 this will force the first digits sent to your LEC on that pipe to be their respective LD code.

That is klugie imo so I suggest you do the list traces and post them...Many people here can assist.