IPO Rls 12.1 Latest Updates 2

[William C290]

Hello ...

I received an update from the T4 engineering that the release 12.1 has been delayed TENTATIVELY by 2 weeks (till 25th November) for GA since there were some high priority issues detected, forming the reason of this change of plans.

 

[derfloh]

Usually they deliver those issues first and fix them later

 

[biv343]

So they're jumping right to 12.1 instead of releasing service packs for 12.0? Guessing its a ploy to be able to say anything 11.X is unsupported.?

I'm just starting to get the few systems left in my patch up to 11.1. I'm not too concerned with Avaya support short of hardware replacements - support seems to be a never ending cycle of sending configs/logs/and repeating sending configs and logs.

 

[digital12188]

Sort of on same subject waiting for 12.1 release to come out. I have a customer that did some vulnerability scans on their network and they came back saying that Apache Tom Cat with 11.1.2.3.0 build 47 needs to be version 9.0.90 or later and they want us to upgrade them. But from what I can tell with release note and other information I can find 12.0. Apache Tom Cat Version is 9.0.86
Customer says they are requesting 9.0.90. So hoping 12.1 has 9.0.90 version.
Anyone have information on that?

 

[IamaSherpa]

Avaya did teh same as R10.0 to R10.1 just after a very little time. I suppose (I hope, to be honest) they were inn a hurry due to CentOS bugs so the easiest and quickest solution was R12.0, this could explain the lack of product infos, the mistakes in official docs and so on. Ho to explain to end users who just migrated to R12.0? Ask to Avaya.

 

[William C290]

Once again Avaya was not honest with us.

 

[IamaSherpa]

We all know their sailorman words, moreover let's say they also removed all the already published R12.1 docs....

 

[William C290]

Finally, Rls 12.1 is now Available on PLDS, and will soon be released on the support site.

 

[scudworth]

It's up on the support site now.

 

[IPOLackey]

Finally we get a system hamburger!!!

▪ Launch System Status (system hamburger | Launch SSA)

 

[derfloh]

What??

 

[sizbut]

It's a tasty skeuomorph.

 

[William C290]

How to upgrade from Rls 12.0 to Rls 12.1 ( VMWare) ?
Is using the same way ISO Transfer ?
Because I start to day upload the iso image to the server but when they have 98% uploading the server stop working, when restarting it, the VM faild to start .

What is the process to upgrade to Rls 12.1 ?

 

[IamaSherpa]

How to upgrade from Rls 12.0 to Rls 12.1 ( VMWare) ?
Is using the same way ISO Transfer ?
Because I start to day upload the iso image to the server but when they have 98% uploading the server stop working, when restarting it, the VM faild to start .

What is the process to upgrade to Rls 12.1 ?

To be honest since since R11.1 has been released I have often had problems whille upgrading, that's why where possible I personally prefer just provide single backups (IP Office, VM, etc) and rebuild the machine in the newest release, restore it all and then re-host the licensing

 

[Shaun E]

Found a bug in 12.1 Server Edition already. If you move the default gateway to LAN2 it leaves the LAN1 default gateway in place and load balances between them.

Was tearing my hair out for a bit trying to figure out why there were RTP issues on external calls (which go through LAN2) until I manually removed it.

 

[William C290]

Upgrade IPOSE Rls 12.0 to Rls 12.1 on the VMWare Platform, is this using the same standard iso process, or there is additional steps that must to done before?

For Media Manager should I stop the service before the upgrade or leave it?

The main need for the Upgrade is to get rid of the emergency mode when adding a hard disk for recording.

What happened to us exactly is that I uploaded the iso to the server in the usual way and when it reached 98 %, the VMware became very slow and VM restarted when it started after about an hour and a quarter, we found that the IP had returned to the default and when we configured it again and I entered the web manager, I found the copy loaded and when starting the upgrade, a failure message appeared " Yumy Upgrade Failed"

 

[nnaarrnn]

Upgrade IPOSE Rls 12.0 to Rls 12.1 on the VMWare Platform, is this using the same standard iso process, or there is additional steps that must to done before?

For Media Manager should I stop the service before the upgrade or leave it?

The main need for the Upgrade is to get rid of the emergency mode when adding a hard disk for recording.

What happened to us exactly is that I uploaded the iso to the server in the usual way and when it reached 98 %, the VMware became very slow and VM restarted when it started after about an hour and a quarter, we found that the IP had returned to the default and when we configured it again and I entered the web manager, I found the copy loaded and when starting the upgrade, a failure message appeared " Yumy Upgrade Failed"

You don't use ISOs for virtual machines....

 

[William C290]

Hello @nnaarrnn: I follow this process from the Upgrade manual and the machine is VMWare. Page 107

What you suggest to use ???

 

[Shaun E]

Has anyone else noticed 3 digit shortcodes starting with 1 do not seem to work?

I created two shortcodes both going to Voicemail Collect - 105 and 205. The former returns busy but the latter worked.

105:

 11:19:32    2605785mS CMTARGET:     ac1f640b50000536 357.1342178614.0 74 Test User.0: TimerExpired cause=CMTCDelayedProcessing
 11:19:32    2605785mS CMTARGET:     ac1f640b50000536 357.1342178614.0 74 Test User.0: LOOKUP CALL ROUTE: GID=0 type=100 called_party=105 sub= calling=xx calling_sub= dir=out complete=0 ses=0
 11:19:32    2605785mS CMTARGET:     ac1f640b50000536 357.1342178614.0 74 Test User.0: ADD TARGET (N): number=105 type=100 depth=1 nobar=1 setorig=1 ses=0
 11:19:32    2605785mS CMTARGET:     ac1f640b50000536 357.1342178614.0 74 Test User.0: CancelTimer CMTCDialToneTimeout
 11:19:32    2605785mS CMTARGET:     ac1f640b50000536 357.1342178614.0 74 Test User.0: NO INITIAL TARGETS: ??
 11:19:32    2605786mS CMTARGET:     ac1f640b50000536 357.1342178614.0 74 Test User.0: Fallback() targeting failed

205:

 11:19:55    2629521mS CMTARGET:     ac1f640b50000539 357.1342178617.0 75 Test User.0: TimerExpired cause=CMTCDelayedProcessing
 11:19:55    2629521mS CMTARGET:     ac1f640b50000539 357.1342178617.0 75 Test User.0: LOOKUP CALL ROUTE: GID=0 type=100 called_party=205 sub= calling=xx calling_sub= dir=out complete=0 ses=0
 11:19:55    2629521mS CMTARGET:     ac1f640b50000539 357.1342178617.0 75 Test User.0: ADD TARGET (N): number=205 type=100 depth=1 nobar=1 setorig=1 ses=0
 11:19:55    2629521mS CMTARGET:     ac1f640b50000539 357.1342178617.0 75 Test User.0: SYS SC: 205 3  sc=type=VoicemailCollect code=205, num= callinfop->sending_complete=0 secondary_dialtone=
 11:19:55    2629521mS CMTARGET:     ac1f640b50000539 357.1342178617.0 75 Test User.0: ADD VM TARGET
 11:19:55    2629521mS CMTARGET:     ac1f640b50000539 357.1342178617.0 75 Test User.0: MakeVoicemailTarget pbx=<null> local=1 type=1
 11:19:55    2629521mS CMCallEvt:    0000000000000000 0.1342178619.0 -1 BaseEP: NEW CMEndpoint c4082d60 TOTAL NOW=3 CALL_LIST=1
 11:19:55    2629521mS CMTARGET:     ac1f640b5000053b 0.1342178619.0 75 RAS.0: ADD PRIMARY
 11:19:55    2629521mS CMTARGET:     ac1f640b50000539 357.1342178617.0 75 Test User.0: ADD VM TARGET: SUCCEEDED
 11:19:55    2629521mS CMTARGET:     ac1f640b50000539 357.1342178617.0 75 Test User.0: CancelTimer CMTCDialToneTimeout
 11:19:55    2629521mS CMTARGET:     ac1f640b50000539 357.1342178617.0 75 Test User.0: INITIAL TARGETING SUCCEEDED

This also broke longer shortcodes starting with 1 such 11 digit NANPA dialing (as soon as you dial 3 digits it returned busy) but I've worked around it by setting the dial delay count to 4.

Replicated on Server Edition and IP500.

 

[nnaarrnn]

Hello @nnaarrnn: I follow this process from the Upgrade manual and the machine is VMWare. Page 107

What you suggest to use ???

Page 9 it literally says "• Avaya only supports IP Office virtual machines created using the virtualized server images supplied by Avaya."

I see it does show updating via ISO, but It's been my experience that v12.0 is actually v11.notreallyworking.1.goodluck

I had to create a backup and deploy 12.1 fresh via OVA deployment.