Manya More
    [Stream]
    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?

    Call are coming on one of our CO trunks for which at pbx we have setting for disconnet supervision as flllows:

    Disconnect Supervision - In? y Out? n Cyclical Hunt? n
    Answer Supervision Timeout: 10 Receive Answer Supervision? n
    Administer Timers? y
    Manya More
    [Stream]
    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 BAD PORT
    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
    Saud Hussain
    [Americom Technology]
    are you able to resolve this problem????
    Manya More
    [Stream]
    not yet, :-(
    Fernando Duran
    [Ikusi]
    Is the CO trunk in service-onhook, or is still offhook?
    Manya More
    [Stream]
    I didn't get your question. If you are asking about trunk status, It is in Service.
    Fernando Duran
    [Ikusi]
    My question was about the trunk been still on the call, even if customer already hung up. Like if the trunk is not been released because Avaya equipment is not detecting disconnection.
    Manya More
    [Stream]
    Yes, 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. If we forget to release that call manually It remains active.
    Ferdinand Villanueva
    [Gulfsat Communications]
    Please check in your system-parameter feature if wait answer supervision timer is enabled. It supposed to be in page 10.

    regards,
    Manya More
    [Stream]
    It is already disabled.

    Wait Answer Supervision Timer? n
    Ferdinand Villanueva
    [Gulfsat Communications]
    It is already disabled.

    Wait Answer Supervision Timer? n

    You have to enable it.

    regards,
    Manya More
    [Stream]
    just want to make sure that if I enable it , is it going to affect any ISDN trunks because we have all other ISDN trunks.


    Regards,
    Manya More
    [Stream]
    No, not working, I also tried enabling it but same issue.


    Regards
    Manya More
    [Stream]
    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

    Please advise..
    Fernando Duran
    [Ikusi]
    Hi Umesh. This problem is related to the system not recognizing the disconnect dial tone. I have a document done when i used to work at Avaya Mexico for this to be fixed, but is in spanish, and i dont have the time to translate it to english. If you're interested, send me your email address on a private message and i can send it to you. Check if you can get the translated document from the guy who asked it on this thread. http://www.avayausers.com/showthread.php?t=21981
    Manya More
    [Stream]
    Please send it to [email][login to unmask email]/email]
    Manya More
    [Stream]
    Thank you Ferstrange. I have received that document. But is it required any particular privilege to change the system-parameters country option. I can see the settings for country options but when i try to change that it doesn't show country option after I enter command change system paramers


    Please choose from one of the following:

    cdr coverage-forwarding crisis-alert

    Or press CANCEL to cancel the command




    "c" is an ambiguous entry
    Command: change system-parameters c



    I have super-user login privilege on pbx.
    Fernando Duran
    [Ikusi]
    To change country options should be enough with dadmin or craft, or something similar. Also, once measured the time for the disconnect or busy tone, you will have change the system ocm-call-classification, so if your user is not giving you access to those options, then i guess you will have to get someone on Avaya to help you.
    Raul Rea
    [Dolphin Telecomunicacione]

    Hello Fernando Duran. Could you please send me a copy of the document regarding 

    call auto-release not happening? [login to unmask email]   I'm in Mexico and we are having same issue. Regards!


    All Times America/New_York


    Copyright © 2014.'The International Avaya User Group. All Rights Reserved

    All material, files, logos and tradarks within this site are properties of their respective organizations.


    Terms of Service - Privacy Policy - Contact