Ring Groups and Hangup

Discussion in 'General' started by tknman0700, Jan 4, 2010.

  1. tknman0700

    Joined:
    Oct 30, 2009
    Messages:
    49
    Likes Received:
    0
    I have a situation where I have ring groups that are being called from an IVR - simple but the problem is the hangup is not detected. I am running a Sangoma A200 and cannot seem to get it to detect that the hangup has occured until about 5 seconds after the caller hungup. The problem with this is the phones keep ringing and those behind the phones think the system is cutting off the call... HELP. I have tried callprogress=yes but nothing seems to help. I am also having a situation where calls are being dropped mid call... I am unsure how to debug these.

    Here is my chan_dahdi.conf

    ;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
    ;autogenrated on 2009-11-23
    ;Dahdi Channels Configurations
    ;For detailed Dahdi options, view /etc/asterisk/chan_dahdi.conf.bak

    [trunkgroups]

    [channels]
    context=default
    usecallerid=yes
    hidecallerid=no
    callwaiting=yes
    usecallingpres=yes
    callwaitingcallerid=yes
    threewaycalling=yes
    transfer=yes
    canpark=yes
    cancallforward=yes
    callreturn=yes
    echocancel=yes
    echocancelwhenbridged=yes
    relaxdtmf=yes
    rxgain=5.0
    txgain=2.0
    group=1
    callgroup=1
    pickupgroup=1
    immediate=no
    hanguponpolarityswitch=yes
    busydetect=yes
    busycount=3
    callprogress=no

    ;Sangoma AFT-A200 [slot:1 bus:2 span:1] <wanpipe1>
    context=from-zaptel
    group=0
    signalling = fxs_ks
    channel => 1

    context=from-zaptel
    group=0
    signalling = fxs_ks
    channel => 2

    context=from-zaptel
    group=0
    signalling = fxs_ks
    channel => 3

    context=from-zaptel
    group=0
    signalling = fxs_ks
    channel => 4

    context=from-zaptel
    group=0
    signalling = fxs_ks
    channel => 5

    context=from-zaptel
    group=0
    signalling = fxs_ks
    channel => 6

    context=from-zaptel
    group=0
    signalling = fxs_ks
    channel => 7

    context=from-zaptel
    group=0
    signalling = fxs_ks
    channel => 8
     
  2. jgutierrez

    Joined:
    Feb 28, 2008
    Messages:
    5,737
    Likes Received:
    0
    Another solution could be that you enable reversal polarity on your analog lines, and then configure it on chan_dahdi.conf
     
  3. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    could well be causing the hangups, 3 is way to few, try playing three notes on a piano regularly and see. Further busydetect=yes should ONLY be used if your line provider doesn't provide any other method.

    as jguttierez alluded, you need to find out from your telco if they provide "far end disconnect supervision" on your lines, if they do you need to use the same method in chan_dahdi.conf.

    (google "far end disconnect supervision" for more details as to the how's and the where's involved around the world.)
     
  4. tknman0700

    Joined:
    Oct 30, 2009
    Messages:
    49
    Likes Received:
    0
    I contacted them and they are supposed to be getting back with me (telco - its Qwest).

    I changed two settings..

    hanguponpolarityswitch=yes
    busydetect=no
    busycount=6
    callprogress=no

    Perhaps this will help with the hangups in mid call but it didnt help (or make worse) the hangup detection on teh remote end. I did some reading there are some good posts online about it but it seems a very difficult thing to detect.

    Here is a good post:
    http://www.asteriskguru.com/tutorials/r ... email.html

    Not sure I know what to do next..

    I am confused on this comment
    "if they do you need to use the same method in chan_dahdi.conf"

    I know only of the hanguponpolarityreversal option... are there others I could test?
    Thanks for your time.
     
  5. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    Qwest usually use what I think they call CPC (Calling Party Control) (it has other names), that was also in answer to you ultimate question, you should check they are so provisioning your lines that way (and while you're at it try an get the length of the CPC signal they send, as if that is non-standard (unlikely) it can be tuned if necessary), CPC is a brief interruption in loop current rather than a "battery reversal" and is normally taken care of by using "kewlstart" signaling (fxs_ks, which is what you have in chan_dahdi.conf which elides your penultimate question :) ) so maybe hanguponpolarityswitch=no makes more sense.

    regards
    dicko

    p.s. if the illuminated dial on your old trimphone blinks on hangup, it's a fair indication you have CPC on your lines.
     

Share This Page