ok, well I don't have an advanced license and I'm not sure the customer will pay for it, so I will have to see....
Other than that what are the options?
I have a company with two sites connected by VPN with a 406v2 at each location. They are set up with SCN and centralized VM just fine.
What I need to do is make it so a user at each location can be a member of one hunt group.
I'm not seeing the way to do this and have not found the solution on...
All,
Nothing has changed on our config, but now I'm getting a user telling me that when she tries to dial a number that there is a "cannot dial this number" error.
She's trying to dial a 847 Area code. I've already checked the short codes and don't see a conflict.
Here is the log...
Mine doesn't happen after a reboot but rather causes us to reboot.
hmmmm....
For what it's worth, we have 5 systems deployed and this only happens on one of them.
intrigrant,
Here's what happens. If I call the clients site it will ring and then you'll get dead air....sometimes. Sometimes you get the LEC recording.
One user was able to dial another persons extention but no inbound/outbound.
It's almost as if the PRI card or VCM is locking up.
I have this issue that pops up every so often where all calls stop flowing and I get a standard message like "your call can not be completed at this time."
As soon as I reboot the switch it's fine, but that's not really an answer to the problem.
Is anyone else seeing this?
Is there a known...
If I change from Intuity mode to IP Office do the users need to change anything or do they need to only know the new prompts?
Also, will I need to reset up any Auto-Attendant settings?
Thanks!
Ok, so that blocks the creation of the ext., but a user is still created.
When this happens it kills all outbound calls. Is there anyway to block this?
Thanks!
Is there any way to prevent someone from plugging in a phone a creating their own ext?
Someone keeps plugging in a phone at a remote site and it created an ext 9.
That kills all outgoing calls...
Thanks!
yes, we did.
an odd thing just happened. We power cycled the module again.
It didn't work right away, but it started working 10 minutes later.
We've made several successful calls as of now.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.