Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Ghost calls or dropped calls from the Q

Ghost calls or dropped calls from the Q

Ghost calls or dropped calls from the Q

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.

RE: Ghost calls or dropped calls from the Q

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.

RE: Ghost calls or dropped calls from the Q

Just try the command:

<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!

Good luck...

Kind Regards,
Maarten Copini

-Please let me know if this was of any help-

RE: Ghost calls or dropped calls from the Q

                                 EVENTS REPORT

Event Event                      Event     Event      First       Last     Evnt
Type  Description                Data 1    Data 2     Occur       Occur     Cnt

81    No digits collected        14/5     87       01/13/16:30 01/24/08:23  15
81    No digits collected        29/4     263      01/13/16:33 01/25/10:24  255
115   ASAI transfer converse     10/1     2BE      01/13/17:23 01/25/09:55  255
81    No digits collected        29/14    151      01/14/07:13 01/25/10:10  255
62    Adjunct route canceled     44/14    261      01/14/09:05 01/25/10:24  255
60    Adjunct route failed       44/15    261      01/14/09:05 01/25/10:24  255
60    Adjunct route failed       45/4     233      01/14/09:10 01/25/10:21  255
62    Adjunct route canceled     45/6     CC       01/14/09:37 01/25/10:02  175
60    Adjunct route failed       45/5     CC       01/14/09:37 01/25/10:02  217
60    Adjunct route failed       45/3     255      01/14/09:50 01/25/09:51  174
81    No digits collected        34/5     1EC      01/14/10:50 01/24/18:43  19
81    No digits collected        34/6     1EC      01/14/10:50 01/24/18:43  19
81    No digits collected        34/7     1EC      01/14/10:50 01/24/18:43  19
81    No digits collected        27/12    173      01/14/10:55 01/24/07:22  5

RE: Ghost calls or dropped calls from the Q

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

-Please let me know if this was of any help-

RE: Ghost calls or dropped calls from the Q

Thank for the help

RE: Ghost calls or dropped calls from the Q

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.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close