IP500 5.X Conference Center Issue.

[djuplift]

We are running a IP500 recently updated to 5.0.15
We are running Conference Center updated to 3.2.22.

When attempting to join a conference using the conference center action in voicemail pro we are told the conference is not accessible then the call is routed to the error destination.

So I dial the customers conference number, I get into the call flow, I am prompted for my conference ID, I put in the ID press # and then I am told the conference is not accessible and routed off to reception.

I have tried updating the software, restarting both the services for VM pro and Conference Center and the PBX with no luck..

Any help would be appreciated.

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
Juniper - JNCIA-FWV
Convergence+

 

[oneboywonder]

I have the same setup on a customers site which works fine.

Can you run a monitor trace to check system resources or error messages.
Also check the system status to see if the resource is matched to the License.

 

[djuplift]

License is good, I have a trace of the issue are you wanting to see it?

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
Juniper - JNCIA-FWV
Convergence+

 

[djuplift]

Here is the debug view on the failure:

OSThreadFunc entered[TThreadCheckConfIDIsValid, 0445AAB0]
24/02 08:46:52.149 vmprov5s (09,3) 1038,13a0: Session: 00000a1b - Delegate <CLI:3193659723> - There was a problem validating conference information for delegate ID <255880>, (No responce from conf server), going to failure route
24/02 08:46:52.149 vmprov5s (09,4) 1038,13a0: Session: 00000a1b - Executing request to run node Conference.Gen Failure.0
24/02 08:46:52.149 vmprov5s (09,4) 1038,13a0: Session: 00000a1b - Executing node Conference.Gen Failure.0
24/02 08:46:52.149 vmprov5s (09,4) 1038,13a0: Session: 00000a1b - Executing request to run node Conference.Gen Failure.1
24/02 08:46:52.149 vmprov5s (09,4) 1038,13a0: Session: 00000a1b - Executing node Conference.Gen Failure.1
24/02 08:46:52.149 vmprov5s (23,5) 1038,13a0: Succeeded in loading sound bite C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Wavs\en\CONF_23.WAV [uLaw]
24/02 08:46:52.149 vmprov5s (0a,5) 1038,13a0: OSThreadFunc exited[TThreadCheckConfIDIsValid, 0445AAB0]
24/02 08:46:52.149 DbgOut (01,5) 4152,5024: DllMain(hinstDLL=0x10000000, fdwReason=DLL_THREAD_DETACH)


ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
Juniper - JNCIA-FWV
Convergence+

 

[djuplift]

It appears the conference server is not responding to Voicemail.

Any ideas?

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
Juniper - JNCIA-FWV
Convergence+

 

[hairlessupportmonkey]

rebooted the voicemail server?

 

[djuplift]

No but I have restarted the Voicemail Services same thing basically.

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
Juniper - JNCIA-FWV
Convergence+

 

[hairlessupportmonkey]

Give both the server and IPO a reboot if possible.

 

[oneboywonder]

debug shows that the VM cannot connect to the conference center software.

have you restarted both VMpro services?

I would reboot the VM machine as hairless has said and re-run the debug whilst running the test again.

 

[djuplift]

I got it fixed rebooting the voicemail services followed by the conference service seems to have cleared it up..

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
Juniper - JNCIA-FWV
Convergence+