Updating VM Pro when AutoRecord is active 1

[SCNIPOffice]

Hi all,

Something that's been occurring that I think I've pinned down. When using the save & make live feature in VM Pro 8.0.1011 (and earlier versions did this as well), where we have a custom AutoRecord module in place, it appears that pressing the save & make live button when a call is currently being recorded through the autorecord module causes the system to begin playing voicemail prompts to callers that are being recorded.

Callers will hear "Welcome to Avaya IP Office, please enter your password...."

Any thoughts on a way to ensure this doesn't happen (aside from saving changes only when the module is not in use)? For our busy SCN, it's difficult to find a moment when there are no calls recording to save changes.

 

[amriddle01]

It's a known bug, restarting the service cures it until the next change, awaiting a fix

 

[unencrypted]

Having the same issue with system that uses Contact Store for recording. Will try rebooting all systems at EOD. Thanks for the tip, amriddle01

__________________________________________
Programming & Technical Support
Avaya IP Office 500v2
Nortel BCM, Norstar, CallPilot
Cisco UC500

 

[amriddle01]

No need to reboot, just restart the vm Pro service on the server

 

[SCNIPOffice]

I have found that pressing save & make live as soon as no calls are in AutoRecord will correct the issue, but I'll try a service restart next time.

 

[tlpeter]

I have raised this as a bug in the 8.1 trials and they fixed it.
I will ask if this fix will also be included in 7.0 and 8.0

BAZINGA!

I'm not insane, my mother had me tested!

 

[Lodde]

I raised this on 8.0 and I have recieved a PB for VM Pro which helped the issue.
So I assume that it will be included in the next Maint Rel for 8.0

http://www.tek-tips.com/viewthread.cfm?qid=1678280

Regards Lodde

 

[CarGoSki]

dbgview shows what is happening:

22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Configuring for reliable disconnect, IDLE time is 300.000s
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Receive OPEN "" for session 000095f0, call-id 42742, mailbox <vrlauto>, access 4 (VMClient:025A5EB0)
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Access = ACCESS_UNCLUED_VOICEMAIL:
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Mailbox: vrlauto
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Calling Party: 5556667777
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Display String: 5556667777
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Target Party: 7726
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Greeting Modifier: MainGroup
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Language: enu
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Call Ident: 42742
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Call Status: Unknown (0)
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Call Type: External
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Call Direction: Incoming
22/05 11:18:48.734 DbgOut (01,5) 3720,3768: DllMain(hinstDLL=0x10000000, fdwReason=DLL_THREAD_ATTACH)
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Called Party: 5707
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - DDI Number: 5798
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Calling Party Name: 5556667777
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Called Party Name: Patrick Gould
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Caller Party Offset: 0
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Target Party Offset: 0
22/05 11:18:48.734 vmprov5s (09,6) e88, 29c: Session: 000095f0 - Called Party Offset: 0
22/05 11:18:48.734 vmprov5s (0c,9) e88, 29c: SessionManager::RealMailBox(pbx=<02491020>, name=<(null)>, cli=<5556667777>)
22/05 11:18:48.734 vmprov5s (06,9) e88, 29c: VMailBox::FindMailBoxByCLI - pbx=<02491020>, cli=<5556667777> returning 00000000
22/05 11:18:48.734 vmprov5s (06,9) e88, 29c: VMailBox::FindMailBox - pbx=<02491020>, name=<5556667777>, flags=<BYEXT | BYINCDISABLED> - Mailbox not found
22/05 11:18:48.734 vmprov5s (0c,8) e88, 29c: Standard=00000000 vrlauto
22/05 11:18:48.734 vmprov5s (02,8) e88, 29c: > VoiceMailDialog::VoiceMailDialog(075B0490, client=025A5F18)
22/05 11:18:48.734 vmprov5s (07,8) e88, 29c: > IntuityBase::Begin(075B0490 00000004)
22/05 11:18:48.734 vmprov5s (24,8) e88, 29c: > SoundBiteList::AddAnnouncement(075B145C 815 (0 0 0 0 0 0 0 0 0 0) 00000000 (null) 00000000 true false)
22/05 11:18:48.734 vmprov5s (0c,8) e88, 29c: > SoundsManager::AddAnnouncement(815 02A4DB08 enu 02A4EB90[32] true false)
22/05 11:18:48.734 vmprov5s (24,5) e88, 29c: Successfully determined fragments for announcement 815 using language enu, fragments are "287,97"
22/05 11:18:48.734 vmprov5s (0c,8) e88, 29c: < SoundsManager::AddAnnouncement()
22/05 11:18:48.734 vmprov5s (23,5) e88, 29c: SoundsManager::ConvertWAV(0258B8F8, "C:\Program Files (x86)\Avaya\IP Office\Voicemail Pro\VM\Wavs\enu\287.WAV" [uLaw], 075B0490) - Took 0 ms to process, return is 26240
22/05 11:18:48.734 vmprov5s (23,5) e88, 29c: Succeeded in loading sound bite "C:\Program Files (x86)\Avaya\IP Office\Voicemail Pro\VM\Wavs\enu\287.WAV" [uLaw]
22/05 11:18:48.734 vmprov5s (23,5) e88, 29c: SoundsManager::ConvertWAV(0258B8B0, "C:\Program Files (x86)\Avaya\IP Office\Voicemail Pro\VM\Wavs\enu\97.WAV" [uLaw], 075B0490) - Took 0 ms to process, return is 20480
22/05 11:18:48.734 vmprov5s (23,5) e88, 29c: Succeeded in loading sound bite "C:\Program Files (x86)\Avaya\IP Office\Voicemail Pro\VM\Wavs\enu\97.WAV" [uLaw]
22/05 11:18:48.734 vmprov5s (24,8) e88, 29c: < SoundBiteList::AddAnnouncement()
22/05 11:18:48.734 vmprov5s (07,8) e88, 29c: > IntuityBaseNode:laySoundbiteList(0756EDC8 true true)
22/05 11:18:48.734 vmprov5s (07,8) e88, 29c: < IntuityBaseNode:laySoundbiteList()
22/05 11:18:48.734 vmprov5s (07,8) e88, 29c: < IntuityBase::Begin()
22/05 11:18:48.734 vmprov5s (02,8) e88, 29c: < VoiceMailDialog::VoiceMailDialog()

 

[unencrypted]

@amriddle01: true enough. i was able to confirm the vmail greeting stopped with just a service restart. did a reboot of server & ipo at day's end just to "start fresh"

Hope there's a patch soon. my tech support guy informed me yesterday that r7 has the same issue. looks bad to issue new version with old problems

Avaya IP Office
Programming & Technical Support

 

[CarGoSki]

Patch issued for R8.0.1009 and 8.0.1011

JIRA IPOFFICE-26365

You are welcome.

 

[CarGoSki]

It will be GA in Q3-2012

 

[tlpeter]

And again nothing on the caveats site!!!

CarGoSki, i am running 8.1 and it is solved for me already.


BAZINGA!

I'm not insane, my mother had me tested!

 

[CarGoSki]

Yes the service level is in a downward spiral.

Avaya sent us a notification that they would prefer for us to open cases with them via the new website v.s. a phone call. Naturally there are many issues and they say that they are addressing them. I did see one issue addressed where you have to enter the complete sold to number including the leading three zeros. They repaired this by labeling the field "Enter the leading three zeros"

Even though we have a block of hours for IPO and the sold to number for that I now have to enter the sold to number and select a active company control unit that was registered.

We have a dedicated Avaya T3 tech for all of our IPO cases however so far any new case opened via the new website gets assigned to someone else and it is always 24 to 48 hours later that they realize and reassign the case to the right guy.

They have delayed working on a case when opened via the website each time because they need basic information like control unit type and current firmware release. However the site does not ask those questions so the answers can be populated.

They have delayed working on a case when opened via the website several times because the need basic data such as cfg and dbgview traces and sysmon traces. However they rarely seem to look at the attachment section of the case to determine if the information already exists and is available for use.

They have delayed resolving a case frequently by not performing proper internal search to see if a patch already exists. Instead you have to jump through hoops and spend money to upgrade a site to the newest version "hoping" that the issue resolves.

The caveats section is the worst case of a promise with no delivery since well.. since their new website opened. Since they apparently insist on providing such poor service via all of the reasons I have outlined we need access to "every" bug found and repaired. I don't mind performing the research necessary here at T-T or at caveats at MarketingTools however the vast lack of information
is a diservice to business partners.

We are surgeons and they act like poor doctors who increase the cost of malpractice insurance.

my .02

 

[tlpeter]

I agree on all off that
What helped in my support times is that when i raised bugs on the Avaya site is not putting it on IPO but on CM.

Then ten minutes later i had an Avaya engineer on the line and told him it was an IPO bug and he then reassigned it to the right group.
This was much quicker then waiting for 48 hours and them email again because you had no response at all.




BAZINGA!

I'm not insane, my mother had me tested!

 

[CarGoSki]

I hear ya. I think that I will hold them to the fire on these issues. I have sent those issues to our management who was requested by Avaya to collect our input.

 

[SCNIPOffice]

Just to add another perspective, here, but it's incredibly frustrating to have a product where you can find and reproduce an issue and have no way of communicating that issue to the vendor without going through a business partner who doesn't seem to follow up (or is having difficulty working with Avaya).

Honestly though, that may be indicative of the business partner we're working with. I've had to learn this system myself as their technicians have been largely useless past the initial install.