Search results for query: *

I've seen this happen quite often when the installer used the .iso to deploy into ESXi rather than the .ova....

Try 9999 instead of CRAFT.

For this question - I think the answer is Split DNS and WiFi. I think I've had to answer it before as well.

I can't remember exactly, but I think there was a change in 9 or 9.1 for failed registration attempts and then the IP address was blacklisted for xx amount of minutes, with that period of time extended for each subsequent attempt. I don't think it was a configurable setting...it was just hard...

I spoke to Avaya about this a few weeks back. It seems to only be an issue on upgraded systems, no issue on new boxes - or at least not for me. I had the issue on 3 that I setup on lab systems as 9.0 then upgraded to 9.1 To fix them, I copied the >REQUESTPIN.vmp file to the /opt/vmpro/...

Virtual SE licenses are for virtual servers only. The other SE keys are for physical call servers in the solution. So if you had 1 virtual IPOSE and 3 IP500's hanging off it as expansions, you'd need 1 virtual SE license and 3 "physical" SE licenses. If you build it in ASD, it'll give you...

Seems a bit ridiculous that it isn't supported on the 9500's, but 1400's are all good..

I think there is a difference in what you need to do based on the product. Holdmusic has shown above how to register an XT5000 which is different to an Elite bridge product. From memory the bridges don't register as an extension, and instead you use a trunk to connect the two, whereas the...

Assuming this is the same as the older 3050 VPN software, I set a few up a little while back. I never logged in as root, always logged in as admin. The admin password is set during the initial command line setup phase.

I've seen this issue a few times on server edition. There's a field under system->telephony where you need to set the maximum number of sip sessions for each primary/secondary/expansion system, otherwise you get the 503. I have a vague recollection of if you have the trace option for sip set...

To explain further look at the topic. Its number is 1001 So we need to use a shortcode to manipulate the To header in the call, which is what the funky shortcode does. If we dial 11001, the system actually dials 2099, but alters the To field in the invite to what was dialled by the user/ipo...

As well as being logged into the agent app, have you signed on to the agent group? Depending on how the agent privileges are set, an agent may log into the application, but be signed out of all agent groups until they sign into the agent group(s).

The short code is still wrong. One too many X's. If you used the short code as you have it currently, you will be trying to route to topic 11001. Change the code to 1XXX

Have you changed the hostname and statically assigned the ip address of the machine, and then run the hostname update utility? I seem to remember this needs to be done. I remember there being a text or rtf file on the desktop, if you follow the instructions in there, it should get you going.

I always worked off this page: http://marketingtools.avaya.com/knowledgebase/businesspartner/ipoffice/mergedProjects/SE_SolutionOverview/index.html?SolutionSpecification.html&1 But I've just noticed that it refers to the R610, not the 620. Take a look and check it against the details on boot...

I had some funny stuff happen to a site when my licenses weren't valid (virtual server was moved to a new host and mac changed, which invalidated licenses). Specifically, the issue I saw was that tabs disappeared from the config screen. I fixed the mac address issue and all was fine again...

Go to Administration, UI config, and open the UI config for the agent in question, scroll down on the selected elements field and make sure the button appears in there. If not, find it in the available elements field and add it to the selected field.

I'd just reinstall the ISO again and do the ignition again. It'd be good if they gave us a way to run ignition again....

Peter - thats only true when virtualised isn't it? The SID should remain the same on a physical server. The SID is on one of the labels of the server, so if it changed, there'd be all sorts of issues.

Are the licenses for the correct server? If you did the ignition process yourself, perhaps the SID that the licenses were ordered against is what you setup as the secondary... EG disti ordered keys against one server (primary), shipped your 2 servers, and you have setup what they meant to be...