cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
442
Views
0
Helpful
5
Replies

Strange VG248 port problem

6rmisior
Level 1
Level 1

Hello,

Our institution uses a large number of vg248 gateways.

Every so often I'm having a strange problem, where a single port on the vg is unable to make calls but it can receive incoming calls.

If you pickup the receiver on the phone connected to that port there is no dial tone, if you call that phone's number the phone will ring and it works like it should (no noise or any thing during the conversation).

All other ports on that vg work fine.

The only way I can find to fix the port is by rebooting the VG, after the reboot VG works like it should, and it can take a very long time before the problem happens again on the same VG. And if it dose happen again on the same VG it will be on a different port.

I'm wondering if anyone ever had a similar problem.

Here is more info about our standard VG:

Software version : 1.3(1)

DSP firmware version : 3.6(25C)

Loader version : 1.0(1)

We use CCM 4.0(1)sr2a

Thanks,

Robert

5 Replies 5

m.batts
Level 4
Level 4

Hi,

I'm getting the same problem.Did you manage to fix it?

Thanks

Mark

I am experiencing the same issue with VG 1.3 and CCM 4.1. Has anyone seen any further updates?

Same issue here too, CCM 4.1.2 with VG248 1.3 software.

TMH

I have found on my VG248's that rather than restarting the whole box, if you enable and disable the port this tends to fix it.It has only happen 3 times but this has worked twice.

I think the problem is due to a bug in the Vg248 code as quite alot of people have seen this issue on all times of callmanager.

Mark

I have tried this on the last couple of times this has happened to no avail. Only way to fix the issue has been to reboot the VG248. Of note I started to suspect that this issue might have something to do with call waiting as I have seen issues with an ATA where a user flashes to a second line and has an "open line". Flashing back gets you dialtone. In this case it doesn't appear to be a call waiting issue as I had hoped...looks like it is a bug.