Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Very odd calls calls hitting Script

Status
Not open for further replies.

Sympology

MIS
Jan 6, 2004
5,508
GB
Just had an issue where 222 calls hit a service desk in a 30 minute period. Each call only lasted 1 or 2 seconds. This desk tends to receive about 30 an hour. I've looked at the call by call and can't work out the CLI is, normally it's 901234567 etc. I'm guessing it could be a withheld number, but any ideas what these calls could be? (*'s block out script name for business reasons).
Running on Symposium obsolete (4.0) on O/S obsolete (NT4) SUS 10

Call ID: 119,800,025
12:43:21 Give Ringback NULL
12:43:21 Task Flow Handed Off NULL TF: 1 TF: 10090
12:43:21 Local Call Arrived NULL RTE: 48 TRK: 9 CDN: 4905 DNIS: CLID: 1548
12:43:21 Application Interflowed NULL L_APP: Master_Script L_APP: ****_****_Helpdesk
12:43:21 Handed Over to Master Application NULL CDN: 4905 L_APP: Master_Script NORM
12:43:22 Local Call Abandoned NULL


Only the truly stupid believe they know everything.
Stu.. 2004
 
Think we may of found it, looks like a line fault, but very odd, it seems as though it's hitting a line then jumping to another, so comes in as another call.
We've moved it onto a different ISDN line and seems to have gotten us out of the doo doo for now.

Thanks anyway.

Stu..

Only the truly stupid believe they know everything.
Stu.. 2004
 
Try to filter on the CLID and route it to your phone set then. This way to can hear whether or not it's a modem.
Otherwise you can have it routed based upon it's CLID to a disconnect script.
 
Unfortunatly there was no CLID on the number, it was just coming up with the trunk number. We're now doing the Vendor / Maintainer not our fault it yours...no it's not it's yours....
Oh hum..

Stu..

Only the truly stupid believe they know everything.
Stu.. 2004
 
Stu,

I'm a little confused. Did I misread your original post? I think I see:
TRUNK:9
ROUTE:48
CDN:4905
CLID:1548

Did something not carry over correctly?
 
Yeah, seems odd, but the CLID appears for all calls coming in on this trunk. Think it auto assigns this number to a withheld number. An odd one I know, but see it on the ISDN's as well. I'm not really up on the advanced side of Meridian programming, but I believe it something that it sticks in...may be wrong.

Only the truly stupid believe they know everything.
Stu.. 2004
 
Sounds like you don't have all the features on your trunks turned on. When the trunks don't pass CLID from the carrier level it reports the trunking information on your switch as the CLID.

My question would be what are you doing in your Master Script to associate your call to the script *****_helpdesk and what is that application doing in the first line of code.
 
Maybe I see a clue. What type are your incoming trunks-PRI? If so are you familiar with the LD96 prompts MSGI/MSGO? If not we probably need to take a different approach.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top