Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2.1 Update Feedback

Status
Not open for further replies.

bigjohn8210

Technical User
May 26, 2004
323
GB
I have been playing around with 2.1 software


The Phone Manger and Softconsole works Great 2.1

The Voicemail Pro works great for one of my clients
I tried to install this with IMS and no emails when around the building


V2.1 Manager Works fine with 2.0 and 2.1 software level boxes


But 2.1 on the boxes has caused me to have invalid licenses and when you reboot the unit it works Great and latter goes to ivalid.


What have you Guys and Gals experiences been
 
invalis licences is caused buy using a 2.0 manager to programm a 2.1 switch, check the rest of the posts here if you whant feedback on 2.1
 
Ok i will test this this weekend on my system at home but i have been told by a few of the many dealers i do installations for that this is an issue. Not a posted issue on the avaya website but maybe i could have been using 2.0 or some files were left behind.
 
I am not supprised that your dealers have said it is an issue, it has happened on a number of our sites after upgrade.
in all casses the customer had an old 2.0 manager installed on one of there PC's that they used to make changes.

We have also had casses where 2030 pphones have switched to auto answere mode for no apparent reason, again a 2.0 manager had been used on a 2.1 switch.

V2.1 when administered correctly is probably the best release of IPO to date. the only bugs I am aware of are all relativly minor ( and can be corrected easily).

 
Time profiles still don't seem to be working for me in 2.1 - my time profile keeps coming in about 12 minutes late!Set the time server of the IP Office to the actual IP address of the IPO, and also kept it at 0.0.0.0. Is this a bug as my disti has said there has always been a problem with the IPO keeping time, even in the Alchemy days. I'm sure I'm the only one having problems with time profiles! And yes, the manager server DOES have the correct time!!
 
I just put in a new R2.1 install and am having no end of BIZARRE problems with it. Brand new VMS server PC running a clean install of Win2k Server, brand new IPO equipment, properly upgraded to 2.1

Receptionist CANNOT transfer callers to anyone on the phone (!), assisted transfer action is not working correctly, pressing a q-status button for queue A is stealing calls already in progress with another agent from queue B (!), ICLID on PRI is hit and miss with no apparent pattern to when it works and when it does not, VM messages not being delivered intermittently, the list goes on....

I'm starting to wonder if I have a bad control unit, unfortunately the client is a 2 hour drive away so it's hard to justify popping in to swap it out 'just in case'.

I don't think I'm in Kanzas anymore...

[morning]

Peter

 
What have you done to it peter?
I have never seen an IPO behave this badly before & I suspect neither have you.
could you not try a copy of th CFG in a test system to prove the fault to the cfg or the hardware?

(I know I am probably teaching my grandmother to suck eggs here but it is 23:30 here in uk)
 
can you not get some kind of remote access (vpn or similar)to the Manager and VM PC? Configs do get corrupt - so try a good old factory default and start again from scratch. If same prob again, DOA it!
 
Started sucking the eggs last night before I left - created an exact mirror (403 AND VMS setup) here in my lab, will be troubleshooting with it today. Still good advice though.

Remote access... this is a funny one.. yes, but what I have to do is pcanywhere dial-up from toronto to edmonton - then, using the much smaller screen (incompatible video settings) on that desktop I use netmeeting desktop sharing across a narrowband (about 64k) connection to kitchener, again unable to use the full-screen desktop sharing option. So, now I'm looking at a smaller window on my PC which is looking at a larger window through a smaller window, thus giving me scroll bars I have to haul around at dialup speeds to see everything.....

[morning]

Peter

 
Now you see why I run Manager , call status & monitor loocaly Via an ISDN nectwork connection to the remote IPO.
I only resort to VNC for VM Pro admin (& ebvven this can be done localy if you can be bothered to sort out the file sharing correctly)
 
Oh, no arguments, if I had the option to do what you do I would be all over it like flies on honey (or to quote the great Woody from "Cheers," like flies on dead squirrels). Unfortunately, Avaya doesn't consider North America an important enough marketplace to bother tweaking the BRI trunk interface so it will work here.... *sigh*

Peter
 
I am still unsure as to why you have the problem, cant you route data calls on your t1 circuits?

that is what I do with customers that have Pri here (actualy it is in buy default)
Incomming call route - number blank, bearer DATA, dest DialIn.
Im sorry I do not know enough about the capabilities if the US telecom network but not being able to accept data calls on a t1 would seem most strange to me.
 
Sorry, didn't mean to give the wrong impression. Of course I could do this for custs that have PRI or T1 - what I am getting at is if BRI were available ALL my custs would be accessible in this manner. Not to mention the cool videoconferencing posibilites, etc. As it is, the smaller sites are stuck with analog trunks - and often unwilling to pay the extra pittance for a modem2 card at that.

Of course there is the issue that my office is one of those "smaller" sites stuck with analog trunks, not needing enough lines to justify putting in a PRI here. I guess I could ask the boss to spring for a dedicated BRI line and purchase an ISDN modem.... hehehehehehehehehe

Peter
 
ahh yes, small sies & alog lines.
I forgot about them, they would be a right pain.
I would sugest you look at getting the remote PC to act as a router so that you can still connect localy - albeit at a slower rate.

BTW at a push if the site does have ISDN you can connect from your cell phone as a V110 call ( although it is very slow)
 
Now THAT is an interesting thought..... hmmmmmmm. Have you tried this?
 
I have seen it configured on the INDeX IVM, which is an windows NT based product.
IN Remote access Service if yoi select the TCP/IP parameters there is a tick box for entire network or this computer only.
give it a try & let me know.

 
If I can get the right cable and get approval to sign up for it I will. Not convinced it will work here in North America as I get the feeling cell phone calls are being routed through an analog modem bank at the CO here. Not for sure, just my feel based on the language used on my cellphone providers website.

Peter
 
Oh by the way, on the major problem described above, I think I have the problem. It appears that weird and wacky things happen when you try to send a caller to a queued/still queued callflow when there are no free voicemail ports! Can't confirm this until I get the client to purchase more ports (they need them anyway, definately hitting 100% port contention FAR too often), but I will keep y'all updated.

Sounds like a messed up error trapping / exception handling routine in the 2.1 firmware.

Peter
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top