Hi, sorry if i'm posting in the wrong place or if im unable to give much technical information as i mainy work on Cisco Kit and was kind of dropped in at the deep end with this one. - but here goes.
Last year - April 2015 ( yes it's been on going for some time)
We had our CS1k upgraded from V4.5 to V7.6, following the upgrade we had intermittent issues with one way transmission on internal , external , inbound & outbound calls.
We have approx 2600 analoge telephones at our site and 500 IP phones. this issue affects analogue to analogue, IP to IP and analogue to IP.
following a lot of investigation by our support company and avaya the problem was narrowed down to a fault with "junctor 3" on our system. a patch was written to route all calls (except for one test phone which would always produce this issue) away from there and the problem was resolved.
fast forward to February this year and our switch "INI'd" itself for no reason in the middle of the day. we had our maintainer look through the system logs and could find nothing to indicate as to why this happened. following this INI the one way transmission started up again. following some more diagnostics our maintainer suggested that we reseat the Controller cards for each of our IPE Shelves (NT8D01DC)
following this reseat the one way transmission issues once again dissapeared.
however our maintainer noticed that the Patch that was written by Avaya no longer re-created the issue when calls were placed using the test phone, and suggested we remove the patch, advising that should the issue come back we can just put the patch back into service.
as you can probably guess the patch was removed and a day and a half later our transmission woes returned. reapplying the patch has made no difference.
or maintainer once again has advised a reseat of the shelf controller cards which is hopefully scheduled for some time this week, but i am worried that there is an underlying issue causing these problems that they are unable to identify , and am just hoping that someone else has had this issue with the same version as us and successfully found a way through it.
once again apologies if this isnt very technical but i'll try and get any information if its requested.