Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Somehow activated line-based Call Barring and can't disable it?? 5

Status
Not open for further replies.

RFMJohn

IS-IT--Management
Mar 28, 2019
4
US
We have an Avaya system running IP 500 V2 8.0(44). We used to have external Music on Hold, but got rid of it recently. I went in to set it back to WAV. At first, I tried to upload it using TFTP -- with no luck. Some further reading indicated that that method wasn't really the way to go any more -- so I uploaded it manually via Embedded File Management.

To test this, I was dialing *341# to try to listen to the MOH. When I did this, I got a message that said "Use of Network Services is barred." I then went back to working on getting the MOH to work. While I was doing that, someone in the office mentioned that they couldn't dial out on one of the lines (the one that I was working with). It gives a message stating "Outgoing, national calls, and calls to mobile phones are barred."

Very odd! I couldn't find any reference to that message online. We have 5 lines -- and I can dial out just fine on any of the other 5 lines, but not on that one -- from ANY phone. Even a System Level 2 phone. Again, the problem is not phone/user/station-specific. It happened to ALL users on ALL phones on that one line.

During testing, I figured I'd try to repeat it on another line. Sure enough -- as soon as I enter *341# on another line, I get a "Use of Network Services is barred" message -- and then, after that, all numbers dialed on that line from any phone -- including even just short codes -- give the "Outgoing, national calls, and calls to mobile phones are barred" message!

I've rolled back to previously saved setups. I've done full reboots. Nothing seems to bring those lines back. Any thoughts on what I might be missing? I am certainly no Avaya IP 500 expert. I know enough to make some normal button and short code changes when needed -- but I've tried everything I can think of and anything I can find online related to call barring. Nothing seems to relate (especially because everything I can find is more about doing user/extension-based barring, not entire lines).

Note that the MOH stuff never worked for me. The logs show it trying to load it from the SD storage and then gives an error that it "failed to load" with no reason. I've removed it since then -- but now I'm starting to wonder if something got corrupted when it was trying to load/play it -- that has affected the line or security settings? Again, I'm open to suggestions here! Thanks!


 
I think you're dialing *34 on an OUTSIDE line and not to the IP Office, because that recording is not coming from within the IPO

NANPA lists *3X - Reserved for expansion to 3-digit VSCs but maybe your carrier has implemented it for a feature. You would need to find out the vertical service code to undo what you have done there.

And check your short codes, make sure that *34N; exists as Hold Music / N / LGID 0
 
These are all analog POTS lines from Frontier -- nothing special. I doubt that is the issue.

That being said, I'll certainly check it tomorrow by plugging a phone directly into the line before the IP Office to be sure.

- John...
 
TTT is 100% correct. Those prompts did not come from the IP Office, they came from the line. Your dialing *341# went to the external line.

I can't be sure about why external calls then stop but from your description the cause and effect does seem pretty clear.



Stuck in a never ending cycle of file copying.
 
Hey -- just wanted to thank the two of you. You were both absolutely correct. Got to work this morning and plugged straight into one of the analog lines and got the same message.

It was indeed with the lines themselves. Somehow, we had dialed some feature/shortcode into the line that disabled all calling on the lines. (Basically, I think it was *341# since I was trying to play back the MOH.) They said that they knew of no such code that would do it, but that my lines were all disabled except for the one. So, they re-enabled them and now all is back to normal. (Still can't get MOH to play my HoldMusic.wav file, but that's another issue.)

Again, I doubted you, but you were absolutely correct. Thanks!
 
Hey now -- I said that I doubted it, but also immediately said that I would still check it as soon as I could.

Then, when it turned out to be the case, I immediately admitted my mistake and thanked them both for their advice.

What more do you want? The problem is people that won't listen and just complain about others. That isn't what happened here. I followed the given advice and then thanked them repeatedly after admitting that I was wrong.

So much for not being a douche to a guy that took the advice, gave thanks, and admitted his mistake. Sheesh.
 
Another Star for RFMJohn for handling that comment with grace. Some people get a little snarky, and you didn't. Kudos!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top