Hi Mike, Thanks for your help. Manually loading mod_openzap fails. It looks like there is something wrong with my udev rules not changing permission of the /dev/wanpipe files. freeswitch@internal> load mod_openzap -ERR [module load file routine returned an error] 2010-02-26 12:24:26.807413 [DEBUG] zap_config.c:56 Configuration file is /opt/teoswitch/conf/modules.conf. freeswitch@internal> 2010-02-26 12:24:26.807413 [NOTICE] zap_io.c:2778 Modules configured: 1 2010-02-26 12:24:26.807413 [DEBUG] zap_config.c:56 Configuration file is /opt/teoswitch/conf/openzap.conf. 2010-02-26 12:24:26.807413 [DEBUG] zap_io.c:2362 found config for span 2010-02-26 12:24:26.807413 [INFO] zap_io.c:2579 Loading IO from /opt/teoswitch/mod/ozmod_wanpipe.so [wanpipe] 2010-02-26 12:24:26.807413 [DEBUG] zap_config.c:56 Configuration file is /opt/teoswitch/conf/wanpipe.conf. 2010-02-26 12:24:26.807413 [INFO] zap_io.c:2379 auto-loaded 'wanpipe' 2010-02-26 12:24:26.807413 [DEBUG] zap_io.c:2400 created span 1 (smg_prid) of type wanpipe 2010-02-26 12:24:26.807413 [DEBUG] zap_io.c:2413 span 1 [name]=[smg_prid] 2010-02-26 12:24:26.807413 [DEBUG] zap_io.c:2413 span 1 [trunk_type]=[t1] 2010-02-26 12:24:26.817864 [DEBUG] zap_io.c:2417 setting trunk type to 'T1' 2010-02-26 12:24:26.817864 [DEBUG] zap_io.c:2413 span 1 [b-channel]=[1:1-23] 2010-02-26 12:24:26.817864 [ERR] ozmod_wanpipe.c:233 Failed to open wanpipe device span 1 channel 1 2010-02-26 12:24:26.817864 [ERR] ozmod_wanpipe.c:233 Failed to open wanpipe device span 1 channel 2 2010-02-26 12:24:26.817864 [ERR] ozmod_wanpipe.c:233 Failed to open wanpipe device span 1 channel 3 2010-02-26 12:24:26.817864 [ERR] ozmod_wanpipe.c:233 Failed to open wanpipe device span 1 channel 4 2010-02-26 12:24:26.817864 [ERR] ozmod_wanpipe.c:233 Failed to open wanpipe device span 1 channel 5 2010-02-26 12:24:26.817864 [ERR] ozmod_wanpipe.c:233 Failed to open wanpipe device span 1 channel 6 2010-02-26 12:24:26.817864 [ERR] ozmod_wanpipe.c:233 Failed to open wanpipe device span 1 channel 7 Here is what /dev/wan* looks like after udev changes: [root@roberth-c53 bin]# ls -l /dev/wan* crw------- 1 root root 242, 0 Feb 26 11:24 /dev/wanec crw------- 1 root root 241, 2080 Feb 26 11:24 /dev/wanpipe crw------- 1 root root 241, 1 Feb 26 11:24 /dev/wanpipe1_if1 crw------- 1 root root 241, 10 Feb 26 11:24 /dev/wanpipe1_if10 crw------- 1 root root 241, 11 Feb 26 11:24 /dev/wanpipe1_if11 crw------- 1 root root 241, 12 Feb 26 11:24 /dev/wanpipe1_if12 CUT A FEW LINES crw------- 1 root root 241, 34 Feb 26 11:24 /dev/wanpipe2_if2 crw------- 1 root root 241, 35 Feb 26 11:24 /dev/wanpipe2_if3 crw------- 1 root root 241, 36 Feb 26 11:24 /dev/wanpipe2_if4 crw------- 1 root root 241, 2112 Feb 26 11:24 /dev/wanpipe_ctrl crw------- 1 root root 241, 2144 Feb 26 11:24 /dev/wanpipe_logger crw------- 1 root root 241, 2368 Feb 26 11:24 /dev/wanpipe_timer0 I made and installed the wanpipe driver as root, is that part of the problem? Thanks again, Robert _____ From: Michael Collins [mailto:msc@freeswitch.org] Sent: Friday, February 26, 2010 11:28 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Cannot make calls through PRI via wanpiperunning as daemon On Thu, Feb 25, 2010 at 5:16 PM, Robert Hadley <robert.hadley@teotech.com> wrote: When running Freeswitch as service called teoswitch as user teoswitch I cannot make calls through the Sangoma PRI or analog cards using wanpipe driver. I have added a file called 30-wanpipe.rules to /etc/udev/rules.d and rebooted the server. cat 30-wanpipe.rules # /etc/udev/rules.d/30-wanpipe.rules SUBSYSTEM=="wptdm", OWNER="teoswitch", GROUP="teoswitch", MODE="0660" SUBSYSTEM=="wanpipe", OWNER="teoswitch", GROUP="teoswitch", MODE="0660" I also tried adding: SUBSYSTEM=="wanec", OWNER="teoswitch", GROUP="teoswitch", MODE="0660" Freeswitch log: Dialplan: sofia/internal/5410@192.168.72.45:5060 parsing [default->SangomaPRI] continue=false Dialplan: sofia/internal/5410@192.168.72.45:5060 Regex (PASS) [SangomaPRI] destination_number(93491045) =~ /^9(\d+)$/ break=on-false Dialplan: sofia/internal/5410@192.168.72.45:5060 Action set(effective_caller_id_number=425740${caller_id_number}) Dialplan: sofia/internal/5410@192.168.72.45:5060 Action bridge(openzap/smg_prid/a/3491045@g1) 2010-02-25 16:51:11.328635 [DEBUG] switch_core_state_machine.c:122 (sofia/internal/5410@192.168.72.45:5060) State Change CS_ROUTING -> CS_EXECUTE 2010-02-25 16:51:11.328635 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/5410@192.168.72.45:5060 [BREAK] 2010-02-25 16:51:11.328635 [DEBUG] switch_core_state_machine.c:341 (sofia/internal/5410@192.168.72.45:5060) State ROUTING going to sleep 2010-02-25 16:51:11.328635 [DEBUG] switch_core_state_machine.c:314 (sofia/internal/5410@192.168.72.45:5060) Running State Change CS_EXECUTE 2010-02-25 16:51:11.328635 [DEBUG] switch_core_state_machine.c:348 (sofia/internal/5410@192.168.72.45:5060) State EXECUTE 2010-02-25 16:51:11.328635 [DEBUG] mod_sofia.c:181 sofia/internal/5410@192.168.72.45:5060 SOFIA EXECUTE 2010-02-25 16:51:11.328635 [DEBUG] switch_core_state_machine.c:159 sofia/internal/5410@192.168.72.45:5060 Standard EXECUTE EXECUTE sofia/internal/5410@192.168.72.45:5060 set(effective_caller_id_number=4257405410) 2010-02-25 16:51:11.328635 [DEBUG] mod_dptools.c:811 sofia/internal/5410@192.168.72.45:5060 SET [effective_caller_id_number]=[4257405410] EXECUTE sofia/internal/5410@192.168.72.45:5060 bridge(openzap/smg_prid/a/3491045@g1) 2010-02-25 16:51:11.339637 [ERR] switch_core_session.c:357 Could not locate channel type openzap 2010-02-25 16:51:11.339637 [ERR] switch_ivr_originate.c:2411 Cannot create outgoing channel of type [openzap] cause: [CHAN_NOT_IMPLEMENTED] 2010-02-25 16:51:11.339637 [DEBUG] switch_ivr_originate.c:3209 Originate Resulted in Error Cause: 66 [CHAN_NOT_IMPLEMENTED] 2010-02-25 16:51:11.339637 [INFO] mod_dptools.c:2346 Originate Failed. Cause: CHAN_NOT_IMPLEMENTED CHAN_NOT_IMPLEMENTED implies that OpenZAP did not load. Capture the output of "load mod_openzap" and look for the reason that it is failing to load. -MC