My CSR people are telling me they are getting a lot of "ghost/dropped calls" or dead air when they take the call. We have a VRU and I have checked the links between the as400 and the VRU. Traffic is far to midland on the T.
Hi
I had the same problem.
In my case the reason of that "dead calls" was in immediate vector-announcement answer. Some International protocols need to have pre-answer ring-back mode or something like that.
I insert wait time 2 sec hearing ring before announcement and the "dead calls" gone away.
<i>display events</i> for the vectors that seem to have problems. The results / event-data displayed can be looked up in the manuals. Otherwise: put 'em up here.
Also the command will show you times and dates problems occured. Give it a try!
Error 81 is: no digits collected. The vector advanced to the next step because users did not enter digits that were in-table x or that were recognized in a goto step x if digits = y. Try to insert an extra step like: goto step x if digits not-in table y or if digits < y.
Error 115 is: ASAI attempted to transfer an active call at a converse step and advenced to the next vector step. This I cannot figure out without seeing your vector.
Error 60 and 62 tell you that an adjunct routing step failed because there was another routing step in the vector (such as queue-to.
All this can, btw, easily be looked up in the Definity Rel.x libraries.
Hope this is of any help to you, 'caus I cannot help you any further without knowing your system and having a look at your call flows...
Plz let me know and good luck.
Kind Regards,
Maarten Copini
I had a problem something like this. During the day, the receptionist would get about 20 calls at a time to where there was no one on the line. The attendant display showed that these calls were coming from our Long Distance trunk group with the letters "ic" to the right in the display. Using CentreVu I pulled a Call Records report for the times the problem occurred. The Call Records showed me which DS1 card the calls were coming from, showed 0 secs, no DNIS, no data, etc. I did a status on the trunk group and found that we had that T-1 down. Once the T-1 was back up, we had no more problems.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.