I think what intrigrant is saying is to put Line Appearance buttons on the extensions and set them to immediate ring so they will ring immediately on the phones, regardless of the hunt group design.
Have you been able to watch in Monitor? What if you set up a hunt group with only the remote users in it and do some testing? That might pinpoint where the disconnect is... do the users have the ability to log in and out of the group?
And technically, you don't have to have two or more systems... it works on just one system, too. You set a login code for the User, but it's pretty easy and works well.
According to the engineer that's been working with them, where we stand now is the licensing for the endpoints is on the IPO, the rest are on the WebLM. The system is now recognized as a branch; however, when they launch IPO Manager from System Manager, the Users section is grayed out, so they...
Haven't had an active role in this one recently, but the last I heard was that they had us re-host the licenses on the IPO itself instead of the recommended WebLM. Since I haven't been told it's ready for programming yet, I think they're still working on it.
Have opened a case with Avaya for an IPO 9.1 (was upgraded from 9.0 prior to any calls) that is being set up as a distributed branch office off a CS1000. The IPO connects to the WebLM, but doesn't see the Enhanced or any other valid licenses. Also, getting some authentication errors in the...
I don't have a system in front of me, but I believe users can still see the caller ID on a group call if the name is short enough or they press the details button.
Are they truly floating throughout the day or are they typically sitting at a different desk each day? It might be an opportunity...
I think it's more along the lines of the SIP extension registers to the Primary via IP address, so if the Primary is down, then it can't register. I'm not sure that if it fails to register, if there's a way to get the IPOCC to try the secondary?
Scenario: By default, the IPOCC (9.0) is configured to communicate only with the Primary IPO Server (9.0). Server goes down and Secondary Server takes over.
What, if anything, can we configure or implement in order to continue using the IPOCC?
Thanks in advance!
Here's another one that doesn't have the Attendee pin, but does use variables. I'm planning on adding the Attendee PIN's to it, but just haven't had the time yet...
HOWTO: Create a Conference MeetMe menu with TUI modifiable passwords
Just to add a side note from experience :) ... you can also put H + the Group Extension number (H2002 for example) - in case the name ever changes, it won't break the functionality.
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.