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!

Call Auto-release doesn't happen for CO trunk

Status
Not open for further replies.

uma0579

Technical User
Feb 13, 2011
5
0
0
IN
Hello Friends,

Please help for the issue where calls are not getting auto-release even when caller hangs up at his end but the call still shows active on our end (agent end). for Each and every call agents need to press the release button on the phone to release the call. Normally when caller disconnect his call it should also get disconnected at agent end but it is not happening and agent needs to press the release button to disconnect. What could be the possible cause for this?


TRUNK GROUP

Group Number: 56 Group Type: co CDR Reports: y
Group Name: SJO Local IN/OUT COR: 91 TN: 70 TAC: 8056
Direction: two-way Outgoing Display? n
Dial Access? n Busy Threshold: 255 Night Service:
Queue Length: 0 Country: 1 Incoming Destination: 472-1000
Comm Type: voice Auth Code? n Digit Absorption List:
Prefix-1? y Trunk Flash? n Toll Restricted? y

Trunk Type: loop-start
Group Type: co Trunk Type: loop-start

TRUNK PARAMETERS

Outgoing Dial Type: tone Cut-Through? n
Trunk Termination: rc Disconnect Timing(msec): 500

Auto Guard? n Call Still Held? n Sig Bit Inversion: none
Analog Loss Group: 6 Digital Loss Group: 11
Trunk Gain: high

Disconnect Supervision - In? y Out? n Cyclical Hunt? n
Answer Supervision Timeout: 10 Receive Answer Supervision? n
Administer Timers? y
TRUNK FEATURES
ACA Assignment? n Measured: both
Maintenance Tests? y
Data Restriction? n

Abandoned Call Search? n
Suppress # Outpulsing? n

Charge Conversion: 1
Decimal Point: none
Currency Symbol:
Charge Type: units Receive Analog Incoming Call ID: disabled
Per Call CPN Blocking Code:
Per Call CPN Unblocking Code:

Outgoing ANI: Ds1 Echo Cancellation? n
DMINISTRABLE TIMERS
Send Incoming/Outgoing Disconnect Timers to TN465 Ports? n
Incoming Disconnect(msec): 500 Outgoing Disconnect(msec): 500
Outgoing Dial Guard(msec): 1600
Incoming Glare Guard(msec): 1500 Outgoing Glare Guard(msec): 1500


Ringing Monitor(msec): 5200 Incoming Seizure(msec): 500
Outgoing End of Dial(sec): 10 Outgoing Seizure Response(sec): 5
Programmed Dial Pause(msec): 1500
Flash Length(msec): 540


END TO END SIGNALING
Tone(msec): 350 Pause(msec): 150

OUTPULSING INFORMATION
PPS: 10 Make(msec): 40 Break(msec): 60 PPM? n
ATMS THRESHOLDS
TTL Type: 105-w-rl Far End Test No:
TTL Vendor: TTL Contact:
Trunk Vendor: Trunk Contact:
Trunk Length:
MARGINAL UNACCEPTABLE
Min Max Min Max
1004 Hz Loss: -2 21 -2 21

-Dev +Dev -Dev +Dev
404 Hz Loss: 9 9 9 9
2804 Hz Loss: 9 9 9 9

Maximum C Message Noise: 55 55
Maximum C Notched Noise: 74 74
Minimum SRL-HI: 0 0
Minimum SRL-LO: 0 0
Minimum ERL: 0 0

Allow ATMS Busyout, Error Logging and Alarming? n
TRUNK GROUP
Administered Members (min/max): 1/22
GROUP MEMBER ASSIGNMENTS Total Administered Members: 21

Port Code Sfx Name Night Mode Type Ans Delay
1: 23A1101 TN797 293-1000
2: 23A1102 TN797 271-2022
3: 23A1103 TN797 271-2022
4: 23A1104 TN797 271-2022
5: 23A1105 TN797 271-2022
6: 23A1106 TN797 271-2022
7: 23A1107 TN797 271-2022
8: 23A1108 TN797 271-2022
9: 23A1201 TN797 271-2022
10: 23A1202 TN797
11: 23A1203 TN797
12: 23A1204 TN797
13: 23A1205 TN797
14: 23A1206 TN797
15: 23A1207 TN797
16: 23A1208 TN797
17: 23B1201 TN797
18: 23B1202 TN797
19:
20: 23B1204 TN797
21: 23B1205 TN797
22: 23B1206 TN797

Even though Customer hangs up, call doesn't release at our end itself. After customer hangs up we can hear disconnection tone almost for 1 minute and then it goes on slient but that call still shows active on phone and trunk. We have to manually press the release button on Avaya phone or put the handset back on Phone cradle to release the call.


Is it in anyway related with physical pair connectivity? I have asked the carrier of that CO trunk to provide trunk settings that they have on their system, but instead of that they carried out testing on that trunk isolating the PBX and as per them issue is at our end. I am pasting below the message content that my colleague sent me after he did testing with carrier technician.

"The technician came today, I made sure I was with him at all times. We made a test on all lines and the problem comes from the box to the inside of the building. For example: We disconnected a line and left it alone from the street up to the box, then we called the number, answered and hanged up. The line didn’t remain open, but when we connected the internal pair ( the our part) we started getting the error. Calls didn’t get disconnected, even though the caller hangs up, the call still remained open. This is not only something the technician told me, he gave me his handset testing phone and I performed the test and it happened the same.

So just wondering if it is in anyway related with physical patching, i think it is more related with trunk configuration


Thanks & Regards
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top