VG248 integrate with third party voice mail system get busy

[lwai]

Hi,

We have a CCM 3.3(5) and we have a VG248 directly connected SMDI with a third party VoiceMail system.

Frequently, when users call voicemail pilot number, they hear busy tone but there have voice mail ports in idle status,the call cannot be forward o the next available port.

Why is this happening and is there a way of fixing that ? We had replace and upgrade the IOS of the VG248, but the issue cannot be fixed. Reboot the Pub. and Sub. server will solve the issue temp.

It will happen again within several hours or a couple of days.

The status of the pilot and the voice mail ports are registered to the cluster as the issue happened.

The virtual interface of the VG248 is assigned to the pilot and it forward all to the first port of the VG248. We use 12 ports of the VG248 to connect the mail system.

[Sandy Lee]

Hi,

We had a similar issue, make sure all your 12 ports are configured correctly regarding the CFB's. If you make one mistake in your chain of CFBs from the first port until your 12th port, that may be your problem.

Try calling each VG248 directly and see if it answers you correctly.

Regards.

[lwai]

Hi Sandy,

I will double check the setting.

If the issue happen, user restart the CM service in both Pub. and Sub. servers will temp. settle the issue. But it may happen again within a couple of days.

As the issue happen, user press the message button will get busy tone. But if the calls comes from PSTN via voice gateway, the incoming calls can ring the DN.

It is very tricky for me.

No solution from Cisco TAC and TAC suspect the issue comes from VG248. I had changed the VG248 and IOS, the issue cannot be solved.

Any input will be much appreciated!!

[lwai]

Hi,

Replace Pub. server and restore the data, all phone registered to this new server.

The issue still cannot be solved!

As user press the voice mail button, no pilot DN display and get busy tone. External user can ring the pilot.

Voice mail profile was created once, no luck; the same issue happen again.

Reboot the server will solve the issue temp.

TAC cannot provide any action plan in this issue.

Do you have any idea on this tricky issue?

Michael.