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

IP Office stops communicating with 2

Status
Not open for further replies.

EricMcS

IS-IT--Management
Apr 9, 2015
31
CA
I have an Avaya IP Office V2 which has been intermittently no longer communicating with VM server. This system has been rock solid for years, but this just started happening about 6 months ago.

About every 2 months, I will get a report that calls are playing a carrier message about the line being down. Doesn't affect direct dials - until the most recent event, it was anything that went to the VMPro (IVR, or direct-dial VM.) Today, it was even more weird - it was only 1 VM Route... All other IVR/VM was working, but if we called our main number which uses a short code to go to a VM routine it would fail - this also happened for any other route that went to the same shortcode.

This is the error code we got:
13:51:28 2782699010mS CMTARGET: 0a0100f00000e8e4 5.7.1 15576 Q931 Trunk:5 CHAN=13: SYS SC: *6003 5 sc=type=VoicemailCollect code=*6003, num="2011_AutoRoute" callinfop->sending_complete=1 secondary_dialtone=
13:51:28 2782699010mS CMTARGET: 0a0100f00000e8e4 5.7.1 15576 Q931 Trunk:5 CHAN=13: ADD VM TARGET
13:51:28 2782699010mS CMTARGET: Voicemail Pro not operational
13:51:28 2782699011mS CMTARGET: 0a0100f00000e8e4 5.7.1 15576 Q931 Trunk:5 CHAN=13: ADD VM TARGET: FAILED availability=0
13:51:28 2782699011mS CMTARGET: 0a0100f00000e8e4 5.7.1 15576 Q931 Trunk:5 CHAN=13: NO INITIAL TARGETS: ??

As I said, in the past we would get this error on all attempts to transfer to a VM Path, today, it was only one function - all the others were fine.


 
What version IPO?

VM server is windows or linux?
 
Physical IP Office v11.0.4.4.0 Build 6.
VM Server is Windows-based.

It's been a few months and I think I've finally isolated the issue - it appears to be related to the web-based management system.

I've been using the Java-based for years without issue. But, around January of this year, I found that although sluggish, it was faster at doing a couple of tasks so I started using it. About a month later, we had our first crash. And every 2-3 weeks thereafter. Around 2 weeks after I posted my message, I stopped using it and I haven't had a crash since (about 7-8 weeks.)

I will wait and see.
 
Happy to say that it's been about 12 weeks since we stopped using the web-based management tool and have not had a crash since... Before hand, we would have had 4-6 in that time. Must me a flaw in the web-tool, too bad - it was much nicer to use than the Java fat client.
 
Thanks EricMcS for taking the time to post this. Pink for you.

Joe
FHandw, ACSS, ACIS
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top