FXO can call out but not receve after Update t0 12.7.6-1904-1


(Greg Theron) #1

Hi all
I have a FreePBX Distro Server and Sangoma A400 with 6 FXO and 2 FXS.
it was working fine all calls where being received and sent fine until I did the latest Update.
PBX Firmware: 12.7.6-1904-1.sng7
PBX Service Pack:1.0.0.0
I can Call internal and external.
I can not call from an outside number to the Analog line it just rings. the system will not answer.
I have confirmed that the line works with my buttset.
How do I see if the wanpipe driver can see the incoming call?

Thanks,
Greg


#2

If you can make outgoing calls to the PSTN then the card is working. You should check your inbound route. Open asterisk cli with asterisk -R -vvvvv and make a call to your PSTN number and look for the message “Starting simple switch on DAHDI”


(Greg Theron) #3

No Luck. It was working fine before the update to 1904. below is from asterisk when a POTS call is coming in.
Channel Location State Application(Data)
0 active channels
0 active calls
0 calls processed
Wanpipe is not transferring to Asterisk
What is the Command to see the wanpipe port status?


(Greg Theron) #4

active=yes
alarms=OK
description=wrtdm Board 1
name=WRTDM/0
manufacturer=Sangoma Technologies
devicetype=A400
location=SLOT=4, BUS=7
basechan=1
totchans=24
irq=0
type=analog
port=1,FXO
port=2,FXO
port=3,FXO
port=4,FXO
port=5,FXO
port=6,FXO
port=7,FXO
port=8,FXO
port=9,none
port=10,none
port=11,FXS
port=12,FXS
port=13,none
port=14,none
port=15,none
port=16,none
port=17,none
port=18,none
port=19,none
port=20,none
port=21,none
port=22,none
port=23,none
port=24,none


(Greg Theron) #5

When Pots is Rining it is getting the correct Voltage see below.
[root@L54-VoIP-020 ~]# wanpipemon -i w1g1 -c astats -m 2

    ------- Voltage Status  (FXO,port 1) -------

VOLTAGE : 128 Volts


(Greg Theron) #6

L54-VoIP-020CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked In Service Description
pseudo default default Yes
1 from-analog en default Yes
2 from-analog en default Yes
3 from-analog en default Yes
4 from-analog en default Yes
5 from-analog en default Yes
6 from-analog en default Yes
7 from-analog en default Yes
8 from-analog en default Yes
11 from-analog en default Yes
12 from-analog en default Yes
L54-VoIP-020
CLI> dahdi show status
Description Alarms IRQ bpviol CRC Fra Codi Options LBO
wrtdm Board 1 OK 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)


(Greg Theron) #7

[2019-08-27 08:27:40] ERROR[15616]: config_options.c:710 aco_process_config: Unable to load config file ‘resolver_unbound.conf’
[2019-08-27 08:27:40] WARNING[15616]: iax2/firmware.c:235 iax_firmware_reload: Error opening firmware directory ‘/var/lib/asterisk/firmware/iax’: No such file o r directory
[2019-08-27 08:27:40] NOTICE[15616]: iax2/provision.c:560 iax_provision_reload: No IAX provisioning configuration found, IAX provisioning disabled.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 10.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 1 with signaling Unknown signalling -1 ignored because it is alrea dy configured to be FXS Kewlstart.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 15.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 2 with signaling Unknown signalling -1 ignored because it is alrea dy configured to be FXS Kewlstart.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 20.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 3 with signaling Unknown signalling -1 ignored because it is alrea dy configured to be FXS Kewlstart.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 25.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 4 with signaling Unknown signalling -1 ignored because it is alrea dy configured to be FXS Kewlstart.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 30.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 5 with signaling Unknown signalling -1 ignored because it is alrea dy configured to be FXS Kewlstart.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:7290 handle_alarms: Detected alarm on channel 5: Red Alarm
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 35.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 6 with signaling Unknown signalling -1 ignored because it is alrea dy configured to be FXS Kewlstart.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 40.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 7 with signaling Unknown signalling -1 ignored because it is alrea dy configured to be FXS Kewlstart.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:7290 handle_alarms: Detected alarm on channel 7: Red Alarm
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 45.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 8 with signaling Unknown signalling -1 ignored because it is alrea dy configured to be FXS Kewlstart.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:7290 handle_alarms: Detected alarm on channel 8: Red Alarm
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 50.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 11 with signaling Unknown signalling -1 ignored because it is alre ady configured to be FXO Kewlstart.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:18931 process_dahdi: Ignoring any changes to ‘signalling’ (on reload) at line 55.
[2019-08-27 08:27:40] WARNING[15616]: chan_dahdi.c:12387 mkintf: Attempt to configure channel 12 with signaling Unknown signalling -1 ignored because it is alre ady configured to be FXO Kewlstart.
[2019-08-27 08:27:40] ERROR[15616]: res_pjsip_config_wizard.c:1091 object_type_loaded_observer: Unable to load config file ‘pjsip_wizard.conf’
[2019-08-27 08:27:40] NOTICE[15616]: confbridge/conf_config_parser.c:2295 verify_default_profiles: Adding default_menu menu to app_confbridge
[2019-08-27 08:27:40] WARNING[15616]: app_voicemail.c:14157 actual_load_config: maxsilence should be less than minsecs or you may get empty messages
[2019-08-27 08:27:40] NOTICE[15616]: app_queue.c:9260 reload_queue_rules: queuerules.conf has not changed since it was last loaded. Not taking any action.
L54-VoIP-020*CLI>


(Dave Burgess) #8

There’s almost nothing in here that helps. I don’t think this is a DAHDI problem. It looks like the DAHDI trunk is not getting connected to the card, so you should probably look more closely at the DAHDI interface in FreePBX.

Now, there is a problem in your config somewhere:

it looks like you have two sets of files that are trying to configure the interface. I’m going to guess that the FreePBX DAHDI configuration isn’t set up correctly, and that’s what’s killing your connections to the inbound trunk.


(Greg Theron) #9

fixed had to rollback DAHDi Config to 14.0.1.3


(system) closed #10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.