Search results for query: *

Thanks, AvayaTier3! Good to know.

I think I answered my own question- I created a new COR with FRL 0 and changed calling permission to all other COR's to "no", having it tested.

I failed to mention this is a prison and these are phones inmates use in privacy booths to talk to their attorneys. I know, weird.

Hi, Def G3 v9- looking to restrict ANY outbound calling- internal, external or otherwise. We're using a COR with FRL 0, using restrict outward but that seems to allow internal calling. Any way to do this with a COR? My workaround is hotdial to a dead number but I thought I might be missing...

Turns out we already have that card. However, I feel vindicated about the cause. Thanks again.

Yes, this is exactly it. After we contacted Network services they insisted that there were no configuration changes, however in the course of their investigation the issue has now stopped (guessing they discovered a process running and stopped it). However, I think this is good advice to upgrade...

It is and yes, that does seem logical. However, all 4 of our systems SIMULTANEOUSLY quit responding and they are spread all over the state. And they are not networked together. The only commonality is that they are on the same WAN. WEIRD.

Hello, We have several Definity G3r v9.5 which we access thru INADS via the CLAN. This has been working flawlessly for 10+ years. Recently, both the INADS and local terminal access are being repeatedly disabled. By which I mean not only can we not access the PBX remotely from ASA (communications...

Thanks, I'll try that.

It's to send operator "zero" calls back to the main CCR so callers can pick a department. We don't have a receptionist and no one is monitoring the gen delivery mbx.

Seems like this should be simple: BCM450, I want to have a DN to forward or route internal calls to an existing auto attendant. I created the SDN but when I dial the extension from my phone I get "not in service". Am I missing a setting somewhere? All my other AA's are answered by target lines...

It was my version, recently reloaded new PC with older BEM, and now that it is updated the hunt group will accept a DN. I found that info on older post from snowman50, so thanks in both places!

DN'S 221-411 Application 600-699

I did find documentation on this, at the avaya site (they are loosening up their access to user manuals-- whoo hoo!) According to the manual, it should be as simple as using any spare DN but every DN I try produces an error. Additionally, I have had to restart BEM several times when the error...

Any possible DN that I enter gives me an error: "Error happened. Error Detail: 701 is not a valid DN" My last DN is 699 so it's definitely unassigned. Any other suggestions? thanks!

Hunt group DN's do not appear to be defined on my BCM 450 in the dial plan and of course Hunt Group page tells me all the DN's I entered are invalid. How do add hunt group DNs to the dial plan? Thanks!!

I will try that, thanks.

Ah, that's what I thought. There are no destination codes configured. I was told by a programmer that these were only used with a PRI T1, but we do not have one of those. Is that the problem?

Where would I locate the absorbed length? Thank you.

We also checked the set restrictions on the voicemail DN's.