Inbound calling to our 800 number Dead air.

[Future00]

Heya

We're having an issue with when people call our 800 number they are randomly getting just dead air. I'll try to explain this as much as I can. It never rings or anything. Its only happening on Route 10 which is loop 18 and 19, 48 channels all from the same carrier. We have other 800 numbers with other carriers that are fine.

I checked the trunks one by one using the maintenance mode on my phone and calling out on each one and found no issues there. What i mean by that is going into ld 36 from the phone and putting in the trunk tn and then dialing a number to see if it connects successfuly. All good.

The dead air happens probably 10 out of 12 times calling the number. When you get dead air and I do a stat on the loop I can see the LCKO. When the person hangs up after realizing the dead air is going no where the LCKO becomes idle again.

I talked with the carrier there trying to say its not an issue with them. They said there sending the dnis back and it seems our system isnt doing anything with it from there. Basically there blaming something with out pbx. Its an Opt 81c Succession 3.

What else I can look for to see what is happening?

The DNIS the 800 numbers is going to is 6100. Is there anything I can do to check the DNIS also? No system changes have made any where. This all started happening 2 days ago for no reason.

Thanks

Ryan

MCP/MCDST/MCSA 2003

 

[johnpoole]

sounds like a change on the far end.. this, i assume is a t, not a pri... is the dnis in a idc or on a set or ?

john poole
bellsouth business
columbia,sc

 

[Future00]

There T's both pointing to the same DNIS.

Not sure what you mean on the DNIS type? If you mean when i do a prt dnb on 6100 it is a phantom tn?

How do I check that?

Ryan

MCP/MCDST/MCSA 2003

 

[Reusser]

Not sure what applications this DNIS number goes to but you need to simplify this as much as possible.

1st - Print IDC table see if DNIS is assigned to anything else

2nd - assign DNIS to a phone and call - when you get silence does set ring

3rd - check all trunks for CLS DIP - if set to DIP will hear silence if telco sending dtmf

4th - find a pattern through repeated tests and traces - same trunks same T1, same intergroup, etc

5th - if you found nothing on switch or found something but switch ok - work with telco. Have them trace as you are tracing. Use Telco that you get the 800 service from if they need to get local telco involved let then initiate that call.

 

[serge9]

to find out if your dn is in the IDC Table

Ld 49
PRT IDC


Serge9

 

[Future00]

prt idc isnt working for me in ld 49...

>ld 49
DGT000
MEM AVAIL: (U/P): 12625338 USED U P: 2503400 206685 TOT: 15335423
DISK SPACE NEEDED: 338 KBYTES
2MB BACKUP DISKETTE(S) NEEDED: 1 (PROJECTED LD43 - BKO)
REQ prt
TYPE idc
CUST 0
SCH3627
CUST
SCH0274

?

Ryan

MCP/MCDST/MCSA 2003

 

[serge9]

Sch3627 indicate that The Customer does not have IDC option enabled

so, your Dn is not in IDC table,You do not have an IDC table

serge9

 

[Future00]

What could be the problem were having? REMI is the carrier that supplies the 2 T's that are having issues. We have Quest and AT&T for other T's with 800 numbers and everything is perfectly fine with them. To me that eliminates that its my PBX. I think its REMI and my 24 hour monitoring support service people say its REMI also. Remi says its the PBX so its an endless battle so far and the complaints are stacking up from people not being able to call in without trying 20 times to get through on those bad 800 numbers...

Ryan

MCP/MCDST/MCSA 2003

 

[davebopp]

We've seen similar problems here. Usually happens after some sort of switch shutdown (our switch likes to crash).

We notify local provider (Verizon) who insists problem is on our end. When we persist they agree to do "intrusive testing" which always clears the problem. We're then just fine for a while.

 

[Future00]

I got our service people and provider on the phone now. There saying the trunk is going off hook and waiting for digits but it never gets them and that is causing the lockouts. There both clueless where to go now. Anyone have any ideas?

Thanks

Ryan

MCP/MCDST/MCSA 2003

 

[Future00]

Sorta figured it out. The DNIS the carrier is to send is 6100. For some odd reason it would randomly drop the 1 and only send 600. So we changed the DNIS to 6111 and then it started randomly dropping 1 or 2 1's. When the dead air would happen when it would only send 600 if we hit say 2 then it would dial ext. 6002. We still dont know why it is dropping the ones so we changed the DNIS to 6620 and eliminated the 1's and is all working good again. The carrier refuses to admit its there problem... Oh well its working.

Ryan

MCP/MCDST/MCSA 2003