E-Cas Connectivity Problem 1

[charcarson]

Our company has two switches that dump data to our ECAS server. About a week ago, one of the switches stopped sending data. Looking at the ip-services and "stat cdr" don't show any problems.

Help with how to troubleshoot this would be appreciated.

 

[98Converter]

When you "stat cdr" the primary link is up? And it's not busied out? Can you view raw data on the ECAS? Maybe you need to restart the link...

Sounds like it should be gathering the data otherwise. But where is it dumping it to ~~~ hrmm.

 

[charcarson]

>When you "stat cdr" the primary link is up? And it's not >busied out? Can you view raw data on the ECAS? Maybe you
>need to restart the link...

Link is up. Data is not on the ECAS box. How do I restart the link?

>Sounds like it should be gathering the data otherwise. >But where is it dumping it to ~~~ hrmm.

Got me. Ping to the switch works. Ping from switch to Ecas works. A netstat -n on the Ecas system shows no TCP connection to the down switch. I do see a connection to the second switch.

 

[roche]

Try to busy out the cdr link and then release it
the commands are: busy cdr pri and release cdr pri

Also have you tried rebooting the ECAS box?

good luck
roche

 

[charcarson]

Unfortunately, we do not have those commands (there isn't anything for cdr when I do a busy help).

Rebooted the ECAS yesterday and today.

 

[charcarson]

We finally called Avaya and they busied out the cdr-link and reset it. This seems to have fixed the issue.

Earlier, we reset the c-lan card, which didn't help us.

Lastly, why I don't have those commands (the busy cdr ones) is because we didn't purchase it.

Avaya was adamant that the cdr was working because the primary link was up. While I don't how the primary link checks for connectivity, I can almost assure you (based on sniffing network traffic) that it isn't based on a response from the endpoint (before the busy and reset, the switch wasn't sending any traffic to the ecas system).

Thanks for the help.

 

[chicagophoneman]

Busy and release commands require Avaya Maintenance or a dadmin level password or higher.