Agent Greeting card not working :( 1

[JonEB]

Morning all,

We have a problem with our MC32 release 3 card not working. It worked yesterday all day then suddenly stopped giving out greetings this morning. It's done this before and we had the card replaced, but surely we can't have 2 faulty MC32 cards??? It's status shows as idle also, so it's not taking itself out of service, it just fails to give greetings. We can browse to the cards IP and everything looks fine. Is there any known issues with this card and AACC 6.2?

 

[SL1M1]

Is this a MIRAN Card MC8 (0-7 ports)
It maywell be a licence issue RAN/MUS if that's a Broadcast option, what's your PBX Release
You could try a card reboot

Cheers!!

 

[JonEB]

It's one of these:

http://i.ebayimg.com/t/Nortel-Merid...A=/$(KGrHqF,!g0E7ShTkF5UBO5P(0KUog~~60_12.JPG

We're on release 7 and I've rebooted the card several times and it will work for a period of time, then stop giving the greetings. The card has been replaced like for like, before this we had the exact same issue with a release 2 card... totally stuck for ideas and so are our BT Engineers...

 

[telebub]

We had the same issues after upgrading an AGC from release 2 to release 3.03 on a Media Card. We took it to Avaya and they had to rewrite the code to fix a memory leak. It took MONTHS to find the problem and fix it. When we turned on debug (AGDebugOn) we could sit and monitor the output and see the memory decrease. Once the memory got too low, the card would stop working. A reboot would get it back in service for a couple weeks until the memory ran out again. Below is an example of the memory decreasing and below that is an example of stable memory after implementing the replacement code.

Decreasing memory over a few days
Active:0, maxMem:8708592 0x282c76c (tDisplay): 14/11/11 07:34:39 (Nov 14, 2011)

Active:2, maxMem:4532192 0x282c76c (tDisplay): 15/11/11 16:35:51 (Nov 15, 2011)

Active:6, maxMem:3120420 0x282f028 (tDisplay): 16/11/11 10:03:33 (Nov 16, 2011)

Active:2, maxMem:1555668 0x282f028 (tDisplay): 17/11/11 11:19:40 (Nov 17, 2011)


Stable memory over a few days after the fix
Active:1, maxMem:34311116 0x282c304 (tDisplay): 10/01/12 08:17:18 (Jan 10, 2012)

Active:0, maxMem:34311116 0x282c304 (tDisplay): 11/01/12 07:58:22 (Jan 11, 2012)

Active:0, maxMem:34311116 0x282ebc0 (tDisplay): 12/01/12 08:10:53 (Jan 12, 2012)

 

[JonEB]

We have about 80 agents using greetings, and it seems to last at best about half a day. Never thought of a memory leak though, so I will turn the debug on and monitor it for a couple of hours before it inevitably fails again

 

[JonEB]

Just a further update to this... we had engineers in today to have another look at the card and we cannot seem to generate any memory usage logs. AGDebugOn didn't seem to be a recognised command, so is this just specific to 3.03 release, as ours is a 3.01

From what you have said though, those are the exact same symptoms we're getting and it would make perfect sense for the problem to be the one you describe with the memory leak.

 

[telebub]

Ok, I just confirmed the debug command on ours. AGDebugOn and AGDebugOff worked. It might only work on 3.03, not sure.

 

[JonEB]

telebub, we have had the card updated to version 3.03 and same issue again, lasted 2 weeks before it fell over. Using the mcShellPrintLastLog it's saying that there is a lack of memory. What command did you use above to see the mem usage?

 

[telebub]

AGDebugOn and AGDebugOff.

We started out with 3.03 and experienced the memory leak. After fighting it for about 7 months, Avaya Design wrote a new load of 3.03 that we have in service today. I think they might have incorporated the debug commands into the new load so they could see the results. I'm not sure those debug commands work in a standard load of 3.03 or 3.02. You'll just have to try.