Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. don't show status DAHDI after upgrade to Asterisk 1.8

don't show status DAHDI after upgrade to Asterisk 1.8

Scheduled Pinned Locked Moved Support
25 Posts 4 Posters 247 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E
    E
    Eugene
    wrote on last edited by
    #16

    ....If it works of some calls, it should work for others as long as you have DAHDI/ix as channel names. In any case send me the debug output as before for the other type of calls, look at the device names there.

    ОК, I will send it soon. There is no indications while DAHDI/iN/YYY rings to SIP extension. The indication is appears when call is timed out and transfered to voicemail system.
    ** *EDIT: The indication is appears when I pickup the phone too, but not while phone ringing. **

    And to make it clear to other users, this happens with CUSTOM DAHDI TRUNKS for ISDN, not for regular DAHDI usage... right?

    I think it's not a CUSTOM DAHDI TRUNKS for ISDN, it's STANDARD DAHDI TRUNKS for ISDN (DIGIUM Wildcard TE122). But new version of DAHDI and LibPRI used in Asterisk 1.8 was changed for best q931 support. Therefore, such a system of naming ISDN channels is standard for all installations of Asterisk 1.8

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #17

      I talked about Custom because in the logs there is a mention of a custom trunk in freepbx. Be sure to have the "all" permission in both read/write in /etc/asterisk/manager.conf. Some asterisk versions filter out events event if you have the individual permission set (I think it is a bug in trixbox only, but maybe it is more extended than that). Another issue that I see is the dial extension with the g0/ prefix. Not that is horrible, but that behavior is new, and I think is not good, as you dial a number, the g0 is used by the dial command only.

      1 Reply Last reply
      0
      • E
        E
        Eugene
        wrote on last edited by
        #18

        .... Be sure to have the "all" permission in both read/write in /etc/asterisk/manager.conf...

        read = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
        write = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
        

        ...Another issue that I see is the dial extension with the g0/ prefix. Not that is horrible, but that behavior is new, and I think is not good, as you dial a number, the g0 is used by the dial command only...

        This issue does not affect the display of channel status button. Вut I don't see channel status while DAHDI-->SIP is ringing.
        **DAHDI/i1/100 ringing to SIP/6030 screenshot
        [url=http://www.flickr.com/photos/56594160@N02/5227634625/:ex7qglin]*http://farm6.static.flickr.com/5124/5227634625_0854707b1a_z.jpg*[/url:ex7qglin]

        And now call is answered**
        [url=http://www.flickr.com/photos/56594160@N02/5227632049/:ex7qglin]*http://farm6.static.flickr.com/5288/5227632049_e8f514956e_z.jpg*[/url:ex7qglin]

        1 Reply Last reply
        0
        • N
          N
          nicolas
          wrote on last edited by
          #19

          Hi Eugene,

          Trunk buttons only are displayed when they are bridged. That is normal behavior in fop2.

          1 Reply Last reply
          0
          • E
            E
            Eugene
            wrote on last edited by
            #20

            OK! It's not a bug, it's a feature.

            Thank you, Nicolas!

            1 Reply Last reply
            0
            • R
              R
              RekGRpth
              wrote on last edited by
              #21

              Sorry for upping this theme, but I have trouble with status of extensions on DAHDI.

              I set up much extensions in elastix as DAHDI devices, such as "DAHDI/i9/10" etc, but corresponding buttons don't show their status, when I make call to or from extensions. However status of DAHDI trunks works well, that is, I see channels and phone numbers on trunks.

              1 Reply Last reply
              0
              • N
                N
                nicolas
                wrote on last edited by
                #22

                Check how are your device names are being set by the fop2admin module ( /usr/local/fop2/autoconfig-buttons-freepbx.sh ), and check those names with the active channels for your extensions when you have ongoing calls ( asterisk -rx "core show channels"). If they do not match, you won't see activity.

                1 Reply Last reply
                0
                • R
                  R
                  rcanavan
                  wrote on last edited by
                  #23

                  I have upgraded from Asterisk 1.6 to Asterisk 1.8 and found that the DAHDI channels do not show anymore as well. I have upgraded to FOP2 2.25 with the admin 1.2.10. When running autoconfig-buttons-freepbx.sh I get the DAHDI channels coming back without the i.

                  Is there a setting I am missing in getting this back working?

                  1 Reply Last reply
                  0
                  • R
                    R
                    rcanavan
                    wrote on last edited by
                    #24

                    FYI - I removed the FOP2admin module and reinstalled ( 1.2.10 ).

                    I added the line in php.ini max_input_vars = 2500 so that I could post the buttons form properly as the newer version of PHP only permits up to 1000 by default.

                    I ran the autoconfig-buttons-freepbx.sh and the DAHDI lines do not appear to be showing up correctly still.

                    1 Reply Last reply
                    0
                    • R
                      R
                      rcanavan
                      wrote on last edited by
                      #25

                      Found this post: View Post 1208

                      I am now showing the channels, but it is not showing up properly.

                      Eg. I have a trunk which uses channels 1-47 ( private PRI ) and a trunk that uses channels 49-71 ( PRI from telco ).

                      All channels appear to be coming in via the 1-47 trunk on the FOP2 panel now.

                      EDIT: Upon further review it seems that Asterisk is not reporting the proper DAHDI channel in use. I make a call out which goes out via DAHDI channel 49, however it is reporting it under DAHDI/i3.

                      I can only figure that Asterisk is grouping the trunks via an interface number.

                      Due to this, I changed in FOP2 buttons to use 1-2 for the first two trunk lines ( two links spanned on one group ) and 3 for the last.

                      This does not appear to work ( one of the trunk buttons light up but does not associate properly to the correct trunk ).

                      EDIT: To single out the line in FOP2admin - Buttons, you need to set it to 3-3, otherwise it will generate the lines as if going from 1 to 3. This appears to have resolved the issue.

                      1 Reply Last reply
                      0

                      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                      With your input, this post could be even better 💗

                      Register Login
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      Powered by NodeBB Contributors
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • World
                      • Users
                      • Groups