I am needing help and our vendor doesnt seem to know what to do. We are running CallPilot on Server Release 03.03.06 with CallPilot Manager 05.00.41.57. The last few days I have noticed that when I dial our CP Access DN # of 71700 the call connects but callpilot does not answer. I just get dead air. I went into the Maintenance Admin tab and noticed that 10 out of the 20 DS3OX channels had red x's on them. I then went into channel monitor and they all looked fine. As a quick fix I rebooted the server and everything came back up fine. The problem then occurred again the next day, but when I went into maintenance admin all the channels looked fine. I rebooted the server again and the problem went away. I then come in this morning and am getting complaints that our customers are saying that when they call no one answers. We have 16 remote branch sites that all have their main lines forwarded back here to an SDN for an Auto Attendant. I am getting internal complaints that the phones are ringing but when they answer no one is there. I am getting more complaints from our limited VoIP user's than on the legacy phones. I had opened a ticket with our vendor because I was seeing strange messages come across a telnet session on our signaling server. This is what it is saying
17/04/2009 08:36:33 LOG0006 NPM: npmSendFSResponse : received g729 in FS transmit, compare to g729AnnexA
17/04/2009 08:36:33 LOG0006 NPM: npmSendFSResponse : received g729 in FS receive , compare to g729AnnexA
17/04/2009 08:37:11 LOG0003 VTRK: igcc: cc_i_disc: state = U10 ; cause = 0x10 ; size = 0xC ; channel = 2
17/04/2009 08:39:01 LOG0003 VTRK: igcc: cc_i_disc: state = U10 ; cause = 0x10 ; size = 0xC ; channel = 1
17/04/2009 08:42:39 LOG0006 NPM: npmSendFSResponse : received g729 in FS transmit, compare to g729AnnexA
17/04/2009 08:42:39 LOG0006 NPM: npmSendFSResponse : received g729 in FS receive , compare to g729AnnexA
17/04/2009 08:44:02 LOG0003 VTRK: igcc: cc_i_disc: state = U10 ; cause = 0x10 ; size = 0xC ; channel = 16
17/04/2009 08:45:34 LOG0003 VTRK: igcc: saveNpmDiscData: npmData->cause = 0x10
?17/04/2009 08:51:38 LOG0003 VTRK: igcc: cc_i_disc: state = U10 ; cause = 0x10 ; size = 0xC ; channel = 16
17/04/2009 08:52:18 LOG0004 tRUDPSS: Forwarding for connect Id = 414780544, error of type = 6 (connection lost).
17/04/2009 08:52:18 LOG0003 tRUDPSS: ITS2008 Terminal connection status: 10.179.34.242 lost (20)
We have 3 media gateway cards and our vendor noticed that one of the three was on version 4.0 while the other 2 were on version 4.5. The fixed this problem but also said that we needed to update our DEPS and patches. Over the last 6 months I have updated and updated and updated until I am blue in the face and the problem always comes back. I did notice yesterday that whoever did the last update left the zip files installed on the C:/ on the server. This caused C:/ memory to drop to 500MB. I deleted the temp files and currently are C:/ is back up to right around a gig. Does anyone know what these errors are or maybe what the hell is going on? I am getting so fed up with Nortel either pushing new equipment or lengthy patches to fix our problem. Personally I believe it is a an issue with the server and it probably needs to be replaced.. but our vendor doesnt seem to think so.
17/04/2009 08:36:33 LOG0006 NPM: npmSendFSResponse : received g729 in FS transmit, compare to g729AnnexA
17/04/2009 08:36:33 LOG0006 NPM: npmSendFSResponse : received g729 in FS receive , compare to g729AnnexA
17/04/2009 08:37:11 LOG0003 VTRK: igcc: cc_i_disc: state = U10 ; cause = 0x10 ; size = 0xC ; channel = 2
17/04/2009 08:39:01 LOG0003 VTRK: igcc: cc_i_disc: state = U10 ; cause = 0x10 ; size = 0xC ; channel = 1
17/04/2009 08:42:39 LOG0006 NPM: npmSendFSResponse : received g729 in FS transmit, compare to g729AnnexA
17/04/2009 08:42:39 LOG0006 NPM: npmSendFSResponse : received g729 in FS receive , compare to g729AnnexA
17/04/2009 08:44:02 LOG0003 VTRK: igcc: cc_i_disc: state = U10 ; cause = 0x10 ; size = 0xC ; channel = 16
17/04/2009 08:45:34 LOG0003 VTRK: igcc: saveNpmDiscData: npmData->cause = 0x10
?17/04/2009 08:51:38 LOG0003 VTRK: igcc: cc_i_disc: state = U10 ; cause = 0x10 ; size = 0xC ; channel = 16
17/04/2009 08:52:18 LOG0004 tRUDPSS: Forwarding for connect Id = 414780544, error of type = 6 (connection lost).
17/04/2009 08:52:18 LOG0003 tRUDPSS: ITS2008 Terminal connection status: 10.179.34.242 lost (20)
We have 3 media gateway cards and our vendor noticed that one of the three was on version 4.0 while the other 2 were on version 4.5. The fixed this problem but also said that we needed to update our DEPS and patches. Over the last 6 months I have updated and updated and updated until I am blue in the face and the problem always comes back. I did notice yesterday that whoever did the last update left the zip files installed on the C:/ on the server. This caused C:/ memory to drop to 500MB. I deleted the temp files and currently are C:/ is back up to right around a gig. Does anyone know what these errors are or maybe what the hell is going on? I am getting so fed up with Nortel either pushing new equipment or lengthy patches to fix our problem. Personally I believe it is a an issue with the server and it probably needs to be replaced.. but our vendor doesnt seem to think so.
