Don't show status on DAHDI Extensions

RekGRpthRekGRpth
in Support
I have trouble with status of extensions on DAHDI.
I set up much extensions in elastix as DAHDI devices, such as "DAHDI/i9/19", but corresponding buttons don't show status, when I make call to or from extensions.
However status of DAHDI trunks work well, that is, I see on trunks channels and phone numbers.

Comments

  • nicolasnicolas
    Look at how the autoconfiguration is setting the device names ( run /usr/local/fop2/autoconfig-buttons-freepbx.sh ), and compare those names with active channel names when you are on a call ( asterisk -rx "core show channels" ). If the device names are different, you won' t see status, you have to use in fop2 the same device name as an active channel. If the autoconfiguration fails to guess the number, you will have to create some manual configuration fro your dahdi extensions.
  • RekGRpthRekGRpth
    autoconfiguration sets such device names:

    [DAHDI/i9/55]
    type=extension
    extension=55
    ...
    bun, when I call from 55 to 591600, the command asterisk -rx "core show channels" shows
    ...
    DAHDI/i9/55-40a3 s@macro-dialout-trun Ring Dial(DAHDI/g2/591600,300,T)
    ...
    and number -40a3 changes from call to call
  • nicolasnicolas
    The session id is normal and it is removed by fop2, so the device names are the same. If they are advertised as such in AMI, then it must work... (edited) but perhaps the double slash is troublesome. Try to capture events from AMI using fop2_server in debug level 1 when you make a call with that extension and send the capture to me so I can replay it locally

    service fop2 stop
    cd /usr/local/fop2
    script capture.log
    ./fop2_server -X 1

    (do your call)

    ctrl-C
    exit

    (send me the capture.log file via private email/post)
  • RekGRpthRekGRpth
    I sent log to you, are you received it?
  • nicolasnicolas
    Yes, I did. I have to check/test still.
  • RekGRpthRekGRpth
    I found, why status doesn't showed:

    when I call from SIP phone, registered in FOP2 as SIP/155 in log this string appears: 
    GET CHANNEL input (SIP/155-00006e9a) - output (SIP/155)
    and status of button SIP/155 is shown

    but when I call from phone, registered in FOP2 as DAHDI/i9/55 in log this: 
    GET CHANNEL input (DAHDI/i9/55-71ca) - output (DAHDI/I9)
    although must be some, like this 
    GET CHANNEL input (DAHDI/i9/55-71ca) - output (DAHDI/i9/55)
  • RekGRpthRekGRpth
    The problem was solved by changing "DAHDI/i9" on "SIP" via proxy between FOP2 server and asterisk :shock:
  • nicolasnicolas
    well, a working but maybe ugly solution. I will work on a fix for the next fop2 release so you can avoid using that proxy.
Sign In or Register to comment.

© Asternic Corp 2024