I am having a problem with my outside lines disconnecting after the number is dialed. The call just disappears and there is no ring. I have tested all lines and they all ring and answer fine incoming. Sprint is our local telco provider, and I had a similar problem on our old Definity system. The CO is really close to our office. I have adjusted the "disconnect clear" down to 100ms and I still have the problem. By the way, these are loop start lines w/caller id. Anyone had a similar problem.
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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
IP Office 406 disconnect problem
- Thread starter kmerck
- Start date
Is this 100% of the time or on occasion? If on occasion do you have offhook station selected for the users to enable headset support? If you do this will cause a busy number to clear without presenting a busy tone. This is "working as designed". Apparently Avaya believes that users with headsets are to busy to hit drop on a busy call so they will simply drop the call for them.
Kyle Holladay
Certified: ACACN, ACSCI, ACSCM, TIA-CTP
"If it worked the way it should you wouldn't need me
Kyle Holladay
Certified: ACACN, ACSCI, ACSCM, TIA-CTP
"If it worked the way it should you wouldn't need me
- Thread starter
- #3
intrigrant
Systems Engineer
Maybe you DTMF signal is on the edge of allowed, try to increase the duration/pause times.
You can adjust these on the Analog tab of the trunk settings.
You can adjust these on the Analog tab of the trunk settings.
What is the call cause code from Monitor?
Look for:
CMExtnTX: (plus some stuff)
followed by
Cause=xx, Normal Call Clearing (where xx = a number)
Kyle Holladay
Certified: ACACN, ACSCI, ACSCM, TIA-CTP
"If it worked the way it should you wouldn't need me
Look for:
CMExtnTX: (plus some stuff)
followed by
Cause=xx, Normal Call Clearing (where xx = a number)
Kyle Holladay
Certified: ACACN, ACSCI, ACSCM, TIA-CTP
"If it worked the way it should you wouldn't need me
intrigrant
Systems Engineer
I thought that the Cause codes only is shown for ISDN lines?
From the Sysmon docs:
Cause Codes (ISDN)
When a call is ended, a cause code may be shown in the Monitor trace. This cause code is not
necessarily an error as cause codes are shown at the end of normal calls. Cause codes 0 to 102 are
standard ISDN cause codes. Causes codes 103 upwards are IP Office specific codes.
There is a special filter for ATM on the sysmonitor were you can monitor only the Analog Trunk Modules.
From the Sysmon docs:
Cause Codes (ISDN)
When a call is ended, a cause code may be shown in the Monitor trace. This cause code is not
necessarily an error as cause codes are shown at the end of normal calls. Cause codes 0 to 102 are
standard ISDN cause codes. Causes codes 103 upwards are IP Office specific codes.
There is a special filter for ATM on the sysmonitor were you can monitor only the Analog Trunk Modules.
- Status
