Trying to admin IA770 thru asa and get network connection error.
I have done this on prior releases, this is 6.x. Does it still work or am I missing something? Port 22 is enabled thru the web interface.
I have this issue as well - on CM 5.2.1 and earlier versions there was already a CM and SA login configured and it just needed to be unlocked then it could be accessed via ASA.
On version 6 there are no logins created already, I have tried to create an CM and SA login but am not sure of the criteria (profiles etc's....) for these:
I am sure that once I have added these logins I will be able to access the IA770 through ASA.
CMM is a virtual machine on cm6 and you login via the web browser specifically to do CMM programming. Any login should work. Not sure about ASA connectivity for CMM on cm6. Maybe someone can answer that for you.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting
Yes telnet is enabled. the issue is with valid login when access through port 23 (there doesnt appear to be a CMM only login like in CM5.2). This is 6.0.1 CM
I have been told by AVAYA Tier 3 Messsaging that "SAT" adminstration is no longer supported for users (or Business Partners). You must use the Web Interface only.
This is great because there is currently a bug in CMM for CM6, where you can't setup the auto attendant digit routing (formerly on page 3), it just does not save. You have to have an AVAYA Tier 3 messaging tech set up your auto attendants, until Service Pack 2 for CMM is released on August 15th.
They have a terminal based way in to the CMM administration (backdoor), where they can add/changed subscribers/auto attendants, but it requires the sroot and service login permissions, so not accessable to users any longer.
If you take away the character based emulation interface at least make sure the web interface works. Nothing like letting your customers do your beta testing, AVAYA.
so to answer your question, you will no longer be able to use ASA to administer your audix. They think this is a move forward, I say its a move backwards.
I was afraid that was the answer. I also see it as a step backwards. Im a Huge fan of ASA admin for messaging, sure makes life easier.
If we have no terminal emulation now, how do we do batch uploads? Is there a batch upload through the web interface or are we now required to program 500 mailboxes one by one?
I still trying to get over AVAYA taking away my compact flash backup in CM6
I think if enough people complain, they will put the character/SAT administration back in CMM. It still exists, since that's how the Tier 3 Messaging people got into it and entered my auto attendant data. they claim they had "data corruption issues" between the web interface and the terminal based admin, so what do they do? take away the SAT session based administration!
Wrong answer, AVAYA. (yes, this message is being written to YOU)
Either fix the corruption issue (which BTW, you still seem to have, because newsflash: the web admin for auto attendants DOES NOT WORK), or get rid of web administration. We don't think its needed, and just because the competition has it, doesn't mean WE NEED IT. Quite the opposite, let CISCO and the others have their web administration, we don't want or need it.
We have lost the ability to use "ProVision" to take subscribers from an existing older messaging system, and download them and the COS, and then connect to the new CMM and push the COS and Subscribers to it.
The "migrations importing" they have is a joke. the existing audix has to be a PARTICULAR release for them to even work, so don't tell us the 'crap' you took on our front lawn is really chocolate ice cream we are not buying it.
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.