Cisco VG30D - random crashes / reboots

[brinkworth]

Hi,

We've just installed a new Cisco VG30D DPNSS/Qsig convertor between our Call Manager (v8.5) and a Siemens ISDX. The VG30 is up and running ok and passing calls normally, but it seems to be crashing and rebooting at random times (several times a day)

There only seems to be 2 or 3 calls active at any time, but there's no pattern to the crashes. We've looked at the Call Manager logs, Tiger call logger, ISDX etc, but can't see anything obvious.

Looking in the VG30 system log it says it's crashed  with the following error codes

Recovered from SCN fatal error:-

Error Code: Q3GF  Source: Q3P1

Additional Info: 00

Recovered from SCN fatal error:-

Error Code: DPB7  Source: DPO1

Additional Info: 00

Recovered from SCN fatal error:-
Error Code: Q3GF  Source: Q3P1
Additional Info: 00

We've swapped the hardware for another VG30, but it crashes as well, with the same codes.

Does anyone know what these codes mean, or can anyone suggest how to stop the crashes?

Please help, as it's driving us mad !

Thanks,

Mike

[nick.tyler]

we are having the same problem, but not as sever, tend to find we get a reboot once a day from one of our 4 vg30's. from googling it may be a problem with trunk clock syncronisation, our supplier is lookign into the problem, will post anything of any use if they solve it.

Nick

[brinkworth]

Hi Nick,

We raised a TAC case with Cisco and after trying numerous different things, Cisco gave us a config to load on the VG30. This seems to have fixed the problem, but we're not really sure why this fixed it. We tried switching on and off several different features on the VG30 (at Cisco's suggestion/request), but it didn't make much difference, until we got the Cisco's config.

We found that the VG30 was crashing in this scenario. When you made a call from Call Manager to an analogue extension, that was diverted to a different analogue extn, (on the same switch) the call was set up ok, but when that call cleared down, the VG30. crashed. It seems like that the VG30 didn't like the fact that the original called number was not the same as the actual final called destination (because of the divert) when the call was being cleared down.

We used our call logger to look at the calls in progress just before the time of the VG30 crashes and noticed the diverted calls were clearing down just before the crashes.

Hope that helps...

Mike

[reidg]

HI Nick, came across this post the other night and i was wondering whether you reached any resolution, we've been having the same problem for months with a pair vg30d, raised a tac case but got nowhere with it and as happens its became one of those annoying things we just accept as too busy to chase down.  Did you get a TAC reference, i'd be interested to know as i'm going to raise our issue again and would be useful to point them in the direction of the two cases here as well?

regards

Grant

[brinkworth]

Hi Grant,

Our TAC case ref was SR 623440343. Since loading the config sent to us by Cisco, the VG30 still hasn't crashed at all.

Hope that helps...

Mike.