OGUser

Member

Last active 7 years ago

  1. 7 years ago
    Fri Apr 7 21:33:12 2017
    OGUser started the conversation DAHDI Trunk issues.

    I have FOP2 2.31.07 installed on FreePBX 13. Everything seems to be working great except for the Trunk display. I have 2 PRIs connected to the box. One has DAHDI channels 1-23 and the other 25-36. I assigned those ranges to the buttons in the FOP2 manager and restarted FOP2. The problem is that FOP2 doesn't seem to recognize the channels correctly. All outgoing calls go through the PRI with channels 25-36, and incoming can be from either. But FOP2 will only show calls on whichever PRI I assign channels 1-23 on.
    This shows an incoming call on channel 36 viewed from Asterisk:
    35 from-digital en default Yes
    36 xxxxxxx from-digital en default Yes

    This is the results from running autoconfig-buttons.sh:
    [DAHDI/g0]
    type=trunk
    label=DAHDI/g0 TB PRI
    email=splitme-25-36
    channel=DAHDI/25
    channel=DAHDI/i25
    channel=ZAP/25
    channel=DAHDI/26
    channel=DAHDI/i26
    channel=ZAP/26
    channel=DAHDI/27
    channel=DAHDI/i27
    channel=ZAP/27
    channel=DAHDI/28
    channel=DAHDI/i28
    channel=ZAP/28
    channel=DAHDI/29
    channel=DAHDI/i29
    channel=ZAP/29
    channel=DAHDI/30
    channel=DAHDI/i30
    channel=ZAP/30
    channel=DAHDI/31
    channel=DAHDI/i31
    channel=ZAP/31
    channel=DAHDI/32
    channel=DAHDI/i32
    channel=ZAP/32
    channel=DAHDI/33
    channel=DAHDI/i33
    channel=ZAP/33
    channel=DAHDI/34
    channel=DAHDI/i34
    channel=ZAP/34
    channel=DAHDI/35
    channel=DAHDI/i35
    channel=ZAP/35
    channel=DAHDI/36
    channel=DAHDI/i36
    channel=ZAP/36
    autoanswerheader=__SIPADDHEADER51=Call-Info: answer-after=0.001

    And I attached a file with the screenshot of the FOP2 display.
    Any ideas?

    Found the answer. For those in a similar situation, when I ran a "core show channels", it showed one PRI using DAHDI/i1 and the other using DAHDI/i2. I went to FOP2 Manager and entered a 1 and a 2 in the appropriate trunk Zap/DAHDI channel box.

  2. 15 years ago
    Mon Jul 6 23:33:10 2009
    OGUser posted in getmembers errors.

    32 bit.

  3. Mon Jul 6 20:01:34 2009
    OGUser started the conversation getmembers errors.

    Thank you for an excellent product. I purchased a license immediately after testing it.
    After entering all my extensions however, I seem to have a problem with the FOP2 server shutting down with:
    Can't call method "getMembers" on an undefined value at script/fop2_server.pl line 2830.
    As a little background, I am running the FOP server on a standalone Centos 5 box, and it is monitoring 5 Trixboxes. We have a SIP phone wired to the paging systems at the sites. The error seems to occur when someone dials the paging extension. I ran the server with the -X 15 options and these are the last few entries:
    10.1.16.21 <- Event: ExtensionStatus
    10.1.16.21 <- Privilege: call,all
    10.1.16.21 <- Exten: 6954
    10.1.16.21 <- Context: ext-local
    10.1.16.21 <- Status: 1
    10.1.16.21 <- Server: 2

    10.1.16.21 <- Event: Newstate
    10.1.16.21 <- Privilege: call,all
    10.1.16.21 <- Channel: SIP/6954-09bd3048
    10.1.16.21 <- State: Up
    10.1.16.21 <- CallerID: 6478
    10.1.16.21 <- CallerIDName: device
    10.1.16.21 <- Uniqueid: 1246908058.18153
    10.1.16.21 <- Server: 2

    10.1.16.21 <- Event: Newchannel
    10.1.16.21 <- Privilege: call,all
    10.1.16.21 <- Channel: Zap/pseudo-169205266
    10.1.16.21 <- State: Rsrvd
    10.1.16.21 <- CallerIDNum: <unknown>
    10.1.16.21 <- CallerIDName: <unknown>
    10.1.16.21 <- Uniqueid: 1246908058.18154
    10.1.16.21 <- Server: 2

    10.1.16.21 <- Event: MeetmeJoin
    10.1.16.21 <- Privilege: call,all
    10.1.16.21 <- Channel: SIP/6954-09bd3048
    10.1.16.21 <- Uniqueid: 1246908058.18153
    10.1.16.21 <- Meetme: 223673073d
    10.1.16.21 <- Usernum: 1
    10.1.16.21 <- Server: 2
    Can't call method "getMembers" on an undefined value at script/fop2_server.pl line 2830.

    Do you need any more information?