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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya IP Office Software version 11.1.2.4.0 build 18 released 3

Status
Not open for further replies.

BFG9K

Systems Engineer
Aug 13, 2018
191
AU
No bulletin yet. Any lab rats willing to take the plunge? I'm downloading now

Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia
 
Well at least this answers everyone's questions about IP Office and whether or not there will be another release.

 
Till now no bulletin at all, I think it could mean:
a)Nobody is in charge for it
b)Nobody cares, 'cause it's just a bug fixing suite
c)the doc is in progress

I think they all are really in a trouble waitnig chapt 11 and the related business plan
 
I guess they laid the guy off that does the document and also the manager that was responsible to coordinate it and above that pay grade they simply don't know what is going on in the world as long as they get their big cheque every month :p

or it is the last rise before leaning back to die and the tech side wanted to get the fixes out but not telling anyone what it fixes. Maybe they just made everything work magically so no document needed, HAHAHA

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
Looks like this is just another bugfix release. No new features.

Between the Ch 11 thread, no replies on this thread and almost no other activity on the forum, looks like everyone else has given up on Avaya as well.

Sure, they might continue as a brand but they have definitely burnt any goodwill they had with us over the past 2 years.

Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia
 
I wonder wha the separate .rpm files (vmpro and x-portal) are due for, they are absolutely identical of the ones already included in the linux apps. No description in the Doc !
 
probably to upgrade 11.1.2.3 without upgrading everything.

Useless in my eyes because I rather upgrade it all

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
There is a one big thing in 11.1.2.4
46xxspecial.txt is now also supported for Workplace.

 
And all the fiddly RW_SBC NoUser source numbers for remote extensions behind an SBC are now part of the Manager/Web Manager configuration. Also some settings for remote users of user portal as a softphone.

Workplace can also use the auto-answer feature (though it was designed by someone who didn't understand that not all calls should be auto-answered even if the user selects the feature).

And the restriction on J139 phone features have been removed. All the same IP Office buttons and menus as other J100s on IP Office.

So there is some life in what remains of the IP Office team


Stuck in a never ending cycle of file copying.
 
Bulletin is out:
The SBC settings now being under Network Topology is a welcome change

Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia
 
Had an issue with a new 11.1.2 SP3 not doing an SMTP forward for Hunt Groups
Upgraded to this SP4 and it's still not even attempting an SMTP forward or copy for hunt group messages
* deleted and recreated the hunt group and SMTP goes now :/


New England Communications
 
I ran into the same issue with the hung group voicemail to email. "Broadcast" would work if using VM Pro but not an email address for voicemail to email. I had to do the same thing. Delete and recreate the groups. I created with a slightly different name so I knew it would create a new mailbox. This was on systems that we upgraded. I do not know anything about new systems. I am upgrading two locations next week to 11.1.2.4 we will see if they really fixed the issue.

On the J139 phones did they remove all button restrictions or just the "bridge appearance" button restriction?
Bulletin No. 236 only mentions "bridged appearance".

If your not going to it right don't bother doing it at all!
 
Anther useful fix. I have run into on a lot of 11.1.2.3 systems.
IPOFFICE-170483 VMPro stops intermittently
This release also includes the new certs to get rid of the TLS errors in SSA

I have this running on my lab server and a few other customers. So far no issues.
 
I wonder why Avaya has the "VmPro stops working" so many times in so many releases. It is mind boggling that this is a recurring issue over and over again.
I am working on the IPO since R1.2 and if I had a $1 for each time they did this ... I could go at least for a decent dinner :)

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque
 
Vmpro pro stopping is so intermitent, some deployments, no issues at all. Others every week. It's a huge PITA.
I have to log into those site as part of my weekly tasks to ensure VMPro service is still running.
Hopefully 11.1.2.4 resolves it (for now)
 
@IPOTS, we had this exact issue with one of our Server Editions, the vmpro service would just randomly stop for no reason, nothing in the logs apart from 'Received SIGTERM'. In the end we set up a cron job to stop and re-start the vmpro service every day at midnight which helped but it still stops during the day for no reason sometimes.

Here's the script if you'd like to set this up on yours:

Bash:
#!/bin/bash

#declare mailbox folder name and extension
MBOXNAME="HG4211"
WAVEXT='*.wav'

echo 'Mbox Name: '$MBOXNAME
echo 'File Ext: '$WAVEXT
echo 'Cleaning Mailbox Directory...'
#check backup folder and create if it does not exist
if [ ! -d /usr/etc/opt_bak/"$MBOXNAME" ]; then
        echo 'Directory /usr/etc/opt_bak/'"$MBOXNAME"' does not exist. Creating...'
        mkdir /usr/etc/opt_bak/"$MBOXNAME"
else
        echo 'Directory /usr/etc/opt_bak/'"$MBOXNAME"' already exists. Continuing...'
fi
#make a backup of the mailbox folder
cp /opt/vmpro/Accounts/"$MBOXNAME"/$WAVEXT /usr/etc/opt_bak/"$MBOXNAME"
#store result of copy
COPYRESULT=$?
#check result of copy
if [ $COPYRESULT -eq 0 ]; then
        echo 'Successfully copied files from /opt/vmpro/Accounts/'"$MBOXNAME"' to /usr/etc/opt_bak/'"$MBOXNAME"
else
        echo 'File copy failed, exit code '$COPYRESULT
fi
echo 'Deleting wav files from /opt/vmpro/Accounts/'"$MBOXNAME"
#find and delete any files with extension $WAVEXT with minimum age of 600 min (10 hours)
find /opt/vmpro/Accounts/"$MBOXNAME" -daystart -maxdepth 1 -mmin +600 -type f -name $WAVEXT -delete
#store result of deletion
DELRESULT=$?
#check result of deletion
if [ $DELRESULT -eq 0 ]; then
        echo 'Directory /opt/vmpro/Accounts/'"$MBOXNAME"' Cleaned Successfully'
else
        echo 'Error in Cleaning. Please Manually Check.'
fi
echo 'Deleting txt files from /opt/vmpro/Accounts/'"$MBOXNAME"

Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia
 
@BFG9K, thanks for the script.
There have been a number of reasons why VMPro stops. One was related to the SMTP configuration in VMPro client. If you didn't configure each domain separately it would cause VMPro to stop. Only a restart of the service would correct it.
We had another case where Avaya T4 support took a month to figure out why the VMPro would loose connection. Only a restart of the IPO500v2 would clear it.
Turned out to be a memory leak in which a patch was created.
11.1.2.4 seems to have correct the VMPro stopping. It's been about 15 days now and no issues.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top