outbound calling error: multiple PRIs with Sangoma + FS
Hi All, I am having a problem getting outbound calls to connect on one of my two PRI lines connected to FS via a Sangoma A102 card. Here are my config files: Bottom of /etc/wanpipe/smg_pri.conf: *;AFT-A102 on port 1 signalling=pri_cpe switchtype=euroisdn group=1 spans=1 ;AFT-A102 on port 2 signalling=pri_cpe switchtype=euroisdn group=2 spans=2 * openzap.conf: *[span wanpipe smg_prid] name => smg_prid trunk_type =>e1 b-channel => 1:1-15 b-channel => 1:17-31 trunk_type =>e1 b-channel => 2:1-15 b-channel => 2:17-31* autoload_configs/openzap.conf.xml: *<configuration name="openzap.conf" description="OpenZAP Configuration">* * <settings>* * <param name="debug" value="0"/>* * * * </settings>* * <boost_spans>* * <span id="smg_prid">* * <param name="dialplan" value="XML"/>* * <param name="context" value="default"/>* * </span>* * </boost_spans>* * * * <analog_spans>* * <span id="smg_prid">* * <param name="dialplan" value="XML"/>* * <param name="context" value="default"/>* * * * </span>* * </analog_spans>* *</configuration>* ...and here is the output from FS CLI. Note that the PRI line connected to port 2 (g2) works great; it is g1 that is producing the NO_ROUTE_DESTINATION error: *freeswitch@otalo> originate openzap/smg_prid/a/958655XXXX@g1 &echo* 2010-10-07 18:08:25.273814 [WARNING] ozmod_sangoma_boost.c:344 TX EVENT: CALL_START:(80) [w1g1] CSid=5 Seq=41 Cn=[N/A] Cd=[958655XXXX] Ci=[N/A] Rdnis=[] 2010-10-07 18:08:25.306941 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT (N): CALL_START_ACK:(81) [w1g1] Rc=0 CSid=5 Seq=34 2010-10-07 18:08:25.307953 [NOTICE] switch_channel.c:675 New Channel OpenZAP/1:1/958655XXXX@g1 [c4305297-3a6e-4bd8-a25c-71e96da6b77d] 2010-10-07 18:08:25.411216 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT (N): CALL_STOPPED:(85) [w1g1] Rc=3 CSid=5 Seq=35 2010-10-07 18:08:25.411216 [NOTICE] mod_openzap.c:1935 Hangup OpenZAP/1:1/958655XXXX@g1 [CS_CONSUME_MEDIA] [NO_ROUTE_DESTINATION] -ERR NO_ROUTE_DESTINATION 2010-10-07 18:08:25.412218 [NOTICE] switch_core_session.c:1188 Session 16 (OpenZAP/1:1/958655XXXX@g1) Ended 2010-10-07 18:08:25.412218 [NOTICE] switch_core_session.c:1190 Close Channel OpenZAP/1:1/958655XXXX@g1 [CS_DESTROY] 2010-10-07 18:08:25.441373 [WARNING] sangoma_boost_client.c:221 TX EVENT (N): CALL_STOPPED_ACK:(86) [w1g1] Rc=0 CSid=0 Seq=42 *freeswitch@otalo> originate openzap/smg_prid/a/958655XXXX@g2 &echo* 2010-10-07 18:08:30.199197 [WARNING] ozmod_sangoma_boost.c:344 TX EVENT: CALL_START:(80) [w1g1] CSid=6 Seq=43 Cn=[N/A] Cd=[958655XXXX] Ci=[N/A] Rdnis=[] 2010-10-07 18:08:30.263078 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT (N): CALL_START_ACK:(81) [w2g1] Rc=0 CSid=6 Seq=36 2010-10-07 18:08:30.264081 [NOTICE] switch_channel.c:675 New Channel OpenZAP/1:31/958655XXXX@g2 [fe1dad03-1086-4d56-bc55-62563e170a78] 2010-10-07 18:08:30.493273 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT: CALL PROGRESS:(50) [w2g1] CSid=6 Seq=37 Cn=[N/A] Cd=[N/A] Ci=[N/A] Rdnis=[] 2010-10-07 18:08:30.493273 [NOTICE] mod_openzap.c:1962 Pre-Answer OpenZAP/1:31/958655XXXX@g2! +OK fe1dad03-1086-4d56-bc55-62563e170a78 I don't notice much going on in /var/log/sangoma_mgd.log or /var/log/messages, but then again I'm not sure what to look for. Any guidance would be greatly appreciated! Neil
On Thu, Oct 7, 2010 at 6:52 AM, Neil Patel <neilp@cs.stanford.edu> wrote:
...and here is the output from FS CLI. Note that the PRI line connected to port 2 (g2) works great; it is g1 that is producing the NO_ROUTE_DESTINATION error:
freeswitch@otalo> originate openzap/smg_prid/a/958655XXXX@g1 &echo 2010-10-07 18:08:25.273814 [WARNING] ozmod_sangoma_boost.c:344 TX EVENT: CALL_START:(80) [w1g1] CSid=5 Seq=41 Cn=[N/A] Cd=[958655XXXX] Ci=[N/A] Rdnis=[] 2010-10-07 18:08:25.306941 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT (N): CALL_START_ACK:(81) [w1g1] Rc=0 CSid=5 Seq=34 2010-10-07 18:08:25.307953 [NOTICE] switch_channel.c:675 New Channel OpenZAP/1:1/958655XXXX@g1 [c4305297-3a6e-4bd8-a25c-71e96da6b77d] 2010-10-07 18:08:25.411216 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT (N): CALL_STOPPED:(85) [w1g1] Rc=3 CSid=5 Seq=35 2010-10-07 18:08:25.411216 [NOTICE] mod_openzap.c:1935 Hangup OpenZAP/1:1/958655XXXX@g1 [CS_CONSUME_MEDIA] [NO_ROUTE_DESTINATION]
-ERR NO_ROUTE_DESTINATION
2010-10-07 18:08:25.412218 [NOTICE] switch_core_session.c:1188 Session 16 (OpenZAP/1:1/958655XXXX@g1) Ended 2010-10-07 18:08:25.412218 [NOTICE] switch_core_session.c:1190 Close Channel OpenZAP/1:1/958655XXXX@g1 [CS_DESTROY] 2010-10-07 18:08:25.441373 [WARNING] sangoma_boost_client.c:221 TX EVENT (N): CALL_STOPPED_ACK:(86) [w1g1] Rc=0 CSid=0 Seq=42 freeswitch@otalo> originate openzap/smg_prid/a/958655XXXX@g2 &echo 2010-10-07 18:08:30.199197 [WARNING] ozmod_sangoma_boost.c:344 TX EVENT: CALL_START:(80) [w1g1] CSid=6 Seq=43 Cn=[N/A] Cd=[958655XXXX] Ci=[N/A] Rdnis=[] 2010-10-07 18:08:30.263078 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT (N): CALL_START_ACK:(81) [w2g1] Rc=0 CSid=6 Seq=36 2010-10-07 18:08:30.264081 [NOTICE] switch_channel.c:675 New Channel OpenZAP/1:31/958655XXXX@g2 [fe1dad03-1086-4d56-bc55-62563e170a78] 2010-10-07 18:08:30.493273 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT: CALL PROGRESS:(50) [w2g1] CSid=6 Seq=37 Cn=[N/A] Cd=[N/A] Ci=[N/A] Rdnis=[] 2010-10-07 18:08:30.493273 [NOTICE] mod_openzap.c:1962 Pre-Answer OpenZAP/1:31/958655XXXX@g2!
+OK fe1dad03-1086-4d56-bc55-62563e170a78
I don't notice much going on in /var/log/sangoma_mgd.log or /var/log/messages, but then again I'm not sure what to look for. Any guidance would be greatly appreciated! Neil
Hi Neil, Any reason you are using deprecated software? FreeTDM replaced openzap and libsng_isdn replaced boost. See: http://wiki.freeswitch.org/wiki/FreeTDM http://wiki.sangoma.com/FreeTDM-Sangoma-ISDN-Library Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com
Hi Moises, Thanks for the heads-up about freetdm. I have installed the freetdm module on a freshly updated FS instance, and have also updated my wanpipe drivers to the latest. Here is my freetdm.conf: [span wanpipe wp1] trunk_type => e1 group=>grp1 b-channel => 1:1-15 b-channel => 1:17-31 d-channel => 1:16 [span wanpipe wp2] trunk_type => e1 group=>grp2 b-channel => 2:1-15 b-channel => 2:17-31 d-channel => 2:16 Here's my freetdm.conf.xml: <configuration name="freetdm.conf" description="FreeTDM Configuration"> <settings> <param name="debug" value="0"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <pri_spans> <span name="wp1"> <!-- Log Levels: none, alert, crit, err, warning, notice, info, debug --> <param name="q921loglevel" value="alert"/> <param name="q931loglevel" value="alert"/> <param name="mode" value="user"/> <param name="dialect" value="5ess"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> <span name="wp2"> <param name="q921loglevel" value="alert"/> <param name="q931loglevel" value="alert"/> <param name="mode" value="user"/> <param name="dialect" value="5ess"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> <!-- one entry here per openzap span --> <analog_spans> <span id="1"> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> <param name="tonegroup" value="us"/> <param name="digit-timeout" value="2000"/> <param name="max-digits" value="11"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> <param name="enable-callerid" value="true"/> <!-- regex to stop dialing when it matches --> <!--<param name="dial-regex" value="5555"/>--> <!-- regex to stop dialing when it does not match --> <!--<param name="fail-dial-regex" value="^5"/>--> </span> </analog_spans> </configuration> And pasted below is the errors I am getting when I fire up FS. Note especially the bolded parts: 2010-10-09 18:28:58.364527 [INFO] ftdm_io.c:4288 Loading IO from /usr/local/freeswitch/mod/ftmod_wanpipe.so [wanpipe] 2010-10-09 18:28:58.364647 [INFO] ftdm_io.c:604 Auto-loaded I/O module 'wanpipe' 2010-10-09 18:28:58.364845 [INFO] ftmod_wanpipe.c:363 [s1c1][1:1] configured wanpipe device s1c1 as FreeTDM channel 1:1 fd:43 DTMF: hardware 2010-10-09 18:28:58.364921 [INFO] ftmod_wanpipe.c:363 [s1c2][1:2] configured wanpipe device s1c2 as FreeTDM channel 1:2 fd:46 DTMF: hardware 2010-10-09 18:28:58.364991 [INFO] ftmod_wanpipe.c:363 [s1c3][1:3] configured wanpipe device s1c3 as FreeTDM channel 1:3 fd:49 DTMF: hardware 2010-10-09 18:28:58.365055 [INFO] ftmod_wanpipe.c:363 [s1c4][1:4] configured wanpipe device s1c4 as FreeTDM channel 1:4 fd:52 DTMF: hardware 2010-10-09 18:28:58.365123 [INFO] ftmod_wanpipe.c:363 [s1c5][1:5] configured wanpipe device s1c5 as FreeTDM channel 1:5 fd:55 DTMF: hardware 2010-10-09 18:28:58.365198 [INFO] ftmod_wanpipe.c:363 [s1c6][1:6] configured wanpipe device s1c6 as FreeTDM channel 1:6 fd:58 DTMF: hardware 2010-10-09 18:28:58.365268 [INFO] ftmod_wanpipe.c:363 [s1c7][1:7] configured wanpipe device s1c7 as FreeTDM channel 1:7 fd:61 DTMF: hardware 2010-10-09 18:28:58.365336 [INFO] ftmod_wanpipe.c:363 [s1c8][1:8] configured wanpipe device s1c8 as FreeTDM channel 1:8 fd:64 DTMF: hardware 2010-10-09 18:28:58.365400 [INFO] ftmod_wanpipe.c:363 [s1c9][1:9] configured wanpipe device s1c9 as FreeTDM channel 1:9 fd:67 DTMF: hardware 2010-10-09 18:28:58.365463 [INFO] ftmod_wanpipe.c:363 [s1c10][1:10] configured wanpipe device s1c10 as FreeTDM channel 1:10 fd:70 DTMF: hardware 2010-10-09 18:28:58.365620 [INFO] ftmod_wanpipe.c:363 [s1c11][1:11] configured wanpipe device s1c11 as FreeTDM channel 1:11 fd:41 DTMF: hardware 2010-10-09 18:28:58.365685 [INFO] ftmod_wanpipe.c:363 [s1c12][1:12] configured wanpipe device s1c12 as FreeTDM channel 1:12 fd:75 DTMF: hardware 2010-10-09 18:28:58.365791 [INFO] ftmod_wanpipe.c:363 [s1c13][1:13] configured wanpipe device s1c13 as FreeTDM channel 1:13 fd:78 DTMF: hardware 2010-10-09 18:28:58.365861 [INFO] ftmod_wanpipe.c:363 [s1c14][1:14] configured wanpipe device s1c14 as FreeTDM channel 1:14 fd:81 DTMF: hardware 2010-10-09 18:28:58.365926 [INFO] ftmod_wanpipe.c:363 [s1c15][1:15] configured wanpipe device s1c15 as FreeTDM channel 1:15 fd:84 DTMF: hardware 2010-10-09 18:28:58.366117 [INFO] ftmod_wanpipe.c:363 [s1c16][1:17] configured wanpipe device s1c17 as FreeTDM channel 1:16 fd:87 DTMF: hardware 2010-10-09 18:28:58.366184 [INFO] ftmod_wanpipe.c:363 [s1c17][1:18] configured wanpipe device s1c18 as FreeTDM channel 1:17 fd:90 DTMF: hardware 2010-10-09 18:28:58.366250 [INFO] ftmod_wanpipe.c:363 [s1c18][1:19] configured wanpipe device s1c19 as FreeTDM channel 1:18 fd:93 DTMF: hardware 2010-10-09 18:28:58.366325 [INFO] ftmod_wanpipe.c:363 [s1c19][1:20] configured wanpipe device s1c20 as FreeTDM channel 1:19 fd:96 DTMF: hardware 2010-10-09 18:28:58.366441 [INFO] ftmod_wanpipe.c:363 [s1c20][1:21] configured wanpipe device s1c21 as FreeTDM channel 1:20 fd:99 DTMF: hardware 2010-10-09 18:28:58.366505 [INFO] ftmod_wanpipe.c:363 [s1c21][1:22] configured wanpipe device s1c22 as FreeTDM channel 1:21 fd:102 DTMF: hardware 2010-10-09 18:28:58.366571 [INFO] ftmod_wanpipe.c:363 [s1c22][1:23] configured wanpipe device s1c23 as FreeTDM channel 1:22 fd:105 DTMF: hardware 2010-10-09 18:28:58.366645 [INFO] ftmod_wanpipe.c:363 [s1c23][1:24] configured wanpipe device s1c24 as FreeTDM channel 1:23 fd:108 DTMF: hardware 2010-10-09 18:28:58.366707 [INFO] ftmod_wanpipe.c:363 [s1c24][1:25] configured wanpipe device s1c25 as FreeTDM channel 1:24 fd:111 DTMF: hardware 2010-10-09 18:28:58.366775 [INFO] ftmod_wanpipe.c:363 [s1c25][1:26] configured wanpipe device s1c26 as FreeTDM channel 1:25 fd:114 DTMF: hardware 2010-10-09 18:28:58.366898 [INFO] ftmod_wanpipe.c:363 [s1c26][1:27] configured wanpipe device s1c27 as FreeTDM channel 1:26 fd:40 DTMF: hardware 2010-10-09 18:28:58.366962 [INFO] ftmod_wanpipe.c:363 [s1c27][1:28] configured wanpipe device s1c28 as FreeTDM channel 1:27 fd:119 DTMF: hardware 2010-10-09 18:28:58.367027 [INFO] ftmod_wanpipe.c:363 [s1c28][1:29] configured wanpipe device s1c29 as FreeTDM channel 1:28 fd:122 DTMF: hardware 2010-10-09 18:28:58.367091 [INFO] ftmod_wanpipe.c:363 [s1c29][1:30] configured wanpipe device s1c30 as FreeTDM channel 1:29 fd:125 DTMF: hardware 2010-10-09 18:28:58.367168 [INFO] ftmod_wanpipe.c:363 [s1c30][1:31] configured wanpipe device s1c31 as FreeTDM channel 1:30 fd:128 DTMF: hardware *2010-10-09 18:28:58.367265 [ERR] ftmod_wanpipe.c:238 Failed to open wanpipe device span 1 channel 16 2010-10-09 18:28:58.367305 [ERR] ftdm_io.c:3949 1:Failed to configure span2010-10-09 18:28:58.367470 [INFO] *ftmod_wanpipe.c:363 [s2c1][2:1] configured wanpipe device s2c1 as FreeTDM channel 2:1 fd:131 DTMF: hardware 2010-10-09 18:28:58.367556 [INFO] ftmod_wanpipe.c:363 [s2c2][2:2] configured wanpipe device s2c2 as FreeTDM channel 2:2 fd:134 DTMF: hardware 2010-10-09 18:28:58.367639 [INFO] ftmod_wanpipe.c:363 [s2c3][2:3] configured wanpipe device s2c3 as FreeTDM channel 2:3 fd:137 DTMF: hardware 2010-10-09 18:28:58.367708 [INFO] ftmod_wanpipe.c:363 [s2c4][2:4] configured wanpipe device s2c4 as FreeTDM channel 2:4 fd:140 DTMF: hardware 2010-10-09 18:28:58.367778 [INFO] ftmod_wanpipe.c:363 [s2c5][2:5] configured wanpipe device s2c5 as FreeTDM channel 2:5 fd:143 DTMF: hardware 2010-10-09 18:28:58.367850 [INFO] ftmod_wanpipe.c:363 [s2c6][2:6] configured wanpipe device s2c6 as FreeTDM channel 2:6 fd:146 DTMF: hardware 2010-10-09 18:28:58.367917 [INFO] ftmod_wanpipe.c:363 [s2c7][2:7] configured wanpipe device s2c7 as FreeTDM channel 2:7 fd:149 DTMF: hardware 2010-10-09 18:28:58.367994 [INFO] ftmod_wanpipe.c:363 [s2c8][2:8] configured wanpipe device s2c8 as FreeTDM channel 2:8 fd:152 DTMF: hardware 2010-10-09 18:28:58.368059 [INFO] ftmod_wanpipe.c:363 [s2c9][2:9] configured wanpipe device s2c9 as FreeTDM channel 2:9 fd:155 DTMF: hardware 2010-10-09 18:28:58.368128 [INFO] ftmod_wanpipe.c:363 [s2c10][2:10] configured wanpipe device s2c10 as FreeTDM channel 2:10 fd:158 DTMF: hardware 2010-10-09 18:28:58.368201 [INFO] ftmod_wanpipe.c:363 [s2c11][2:11] configured wanpipe device s2c11 as FreeTDM channel 2:11 fd:161 DTMF: hardware 2010-10-09 18:28:58.368269 [INFO] ftmod_wanpipe.c:363 [s2c12][2:12] configured wanpipe device s2c12 as FreeTDM channel 2:12 fd:164 DTMF: hardware 2010-10-09 18:28:58.368345 [INFO] ftmod_wanpipe.c:363 [s2c13][2:13] configured wanpipe device s2c13 as FreeTDM channel 2:13 fd:167 DTMF: hardware 2010-10-09 18:28:58.368411 [INFO] ftmod_wanpipe.c:363 [s2c14][2:14] configured wanpipe device s2c14 as FreeTDM channel 2:14 fd:170 DTMF: hardware 2010-10-09 18:28:58.368478 [INFO] ftmod_wanpipe.c:363 [s2c15][2:15] configured wanpipe device s2c15 as FreeTDM channel 2:15 fd:173 DTMF: hardware 2010-10-09 18:28:58.368589 [INFO] ftmod_wanpipe.c:363 [s2c16][2:17] configured wanpipe device s2c17 as FreeTDM channel 2:16 fd:176 DTMF: hardware 2010-10-09 18:28:58.368677 [INFO] ftmod_wanpipe.c:363 [s2c17][2:18] configured wanpipe device s2c18 as FreeTDM channel 2:17 fd:179 DTMF: hardware 2010-10-09 18:28:58.368744 [INFO] ftmod_wanpipe.c:363 [s2c18][2:19] configured wanpipe device s2c19 as FreeTDM channel 2:18 fd:182 DTMF: hardware 2010-10-09 18:28:58.368818 [INFO] ftmod_wanpipe.c:363 [s2c19][2:20] configured wanpipe device s2c20 as FreeTDM channel 2:19 fd:185 DTMF: hardware 2010-10-09 18:28:58.368884 [INFO] ftmod_wanpipe.c:363 [s2c20][2:21] configured wanpipe device s2c21 as FreeTDM channel 2:20 fd:188 DTMF: hardware 2010-10-09 18:28:58.368951 [INFO] ftmod_wanpipe.c:363 [s2c21][2:22] configured wanpipe device s2c22 as FreeTDM channel 2:21 fd:191 DTMF: hardware 2010-10-09 18:28:58.369018 [INFO] ftmod_wanpipe.c:363 [s2c22][2:23] configured wanpipe device s2c23 as FreeTDM channel 2:22 fd:194 DTMF: hardware 2010-10-09 18:28:58.369084 [INFO] ftmod_wanpipe.c:363 [s2c23][2:24] configured wanpipe device s2c24 as FreeTDM channel 2:23 fd:197 DTMF: hardware 2010-10-09 18:28:58.369150 [INFO] ftmod_wanpipe.c:363 [s2c24][2:25] configured wanpipe device s2c25 as FreeTDM channel 2:24 fd:200 DTMF: hardware 2010-10-09 18:28:58.369213 [INFO] ftmod_wanpipe.c:363 [s2c25][2:26] configured wanpipe device s2c26 as FreeTDM channel 2:25 fd:203 DTMF: hardware 2010-10-09 18:28:58.369278 [INFO] ftmod_wanpipe.c:363 [s2c26][2:27] configured wanpipe device s2c27 as FreeTDM channel 2:26 fd:206 DTMF: hardware 2010-10-09 18:28:58.369341 [INFO] ftmod_wanpipe.c:363 [s2c27][2:28] configured wanpipe device s2c28 as FreeTDM channel 2:27 fd:209 DTMF: hardware 2010-10-09 18:28:58.369406 [INFO] ftmod_wanpipe.c:363 [s2c28][2:29] configured wanpipe device s2c29 as FreeTDM channel 2:28 fd:212 DTMF: hardware 2010-10-09 18:28:58.369476 [INFO] ftmod_wanpipe.c:363 [s2c29][2:30] configured wanpipe device s2c30 as FreeTDM channel 2:29 fd:215 DTMF: hardware 2010-10-09 18:28:58.369548 [INFO] ftmod_wanpipe.c:363 [s2c30][2:31] configured wanpipe device s2c31 as FreeTDM channel 2:30 fd:218 DTMF: hardware *2010-10-09 18:28:58.369640 [ERR] ftmod_wanpipe.c:238 Failed to open wanpipe device span 2 channel 16 2010-10-09 18:28:58.369687 [ERR] ftdm_io.c:3949 2:Failed to configure span2*010-10-09 18:28:58.369718 [INFO] ftdm_io.c:4213 Configured 60 channel(s) 2010-10-09 18:28:58.452329 [INFO] ftdm_io.c:4288 Loading IO from /usr/local/freeswitch/mod/ftmod_sangoma_isdn.so [sangoma_isdn] 2010-10-09 18:28:58.452369 [INFO] ftmod_sangoma_isdn.c:851 Loading ftmod_sangoma_isdn... 2010-10-09 18:28:58.452688 [INFO] ftmod_sangoma_isdn_stack_rcv.c:877 sng_isdn-> =========================================== = Sangoma FreeTDM ISDN Library = = Version:1.0.0 = =========================================== 2010-10-09 18:28:58.480173 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully registered Stack Manager 2010-10-09 18:28:58.480421 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully started a task for Stack Manager 2010-10-09 18:28:58.480476 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully attached Stack Manager to it's task 2010-10-09 18:28:58.480529 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully registered Call Control 2010-10-09 18:28:58.480611 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully started a task for Call Control 2010-10-09 18:28:58.480657 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully attached Call Control to it's task 2010-10-09 18:28:58.486424 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully registered Q.930/Q.931 2010-10-09 18:28:58.486535 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully started a task for Q.930/Q.931 2010-10-09 18:28:58.486607 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully attached Q.930/Q.931 to it's task 2010-10-09 18:28:58.486658 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully registered LAPD 2010-10-09 18:28:58.486720 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully started a task for LAPD 2010-10-09 18:28:58.486772 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully attached LAPD to it's task 2010-10-09 18:28:58.486823 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully registered Physical Layer 2010-10-09 18:28:58.486881 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully started a task for Physical Layer 2010-10-09 18:28:58.486930 [INFO] ftmod_sangoma_isdn_stack_rcv.c:874 sng_isdn->Successfully attached Physical Layer to it's task 2010-10-09 18:28:58.486986 [INFO] ftdm_io.c:4300 Loading SIG from /usr/local/freeswitch/mod/ftmod_sangoma_isdn.so 2010-10-09 18:28:58.487035 [INFO] ftdm_io.c:4523 auto-loaded 'sangoma_isdn' 2010-10-09 18:28:58.487076 [INFO] ftmod_sangoma_isdn.c:791 Configuring ftmod_sangoma_isdn span = wp1 2010-10-09 18:28:58.487311 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter q921loglevel 2010-10-09 18:28:58.487369 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter q931loglevel 2010-10-09 18:28:58.487425 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter mode 2010-10-09 18:28:58.487480 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter dialect *2010-10-09 18:28:58.487517 [ERR] ftmod_sangoma_isdn_cfg.c:267 wp1: switchtype not specified2010-10-09 18:28:58.487537 [ERR] ftmod_sangoma_isdn.c:807 Failed to parse configuration* 2010-10-09 18:28:58.487578 [ERR] mod_freetdm.c:2478 Error configuring Sangoma ISDN FreeTDM span 1 2010-10-09 18:28:58.487628 [INFO] ftmod_sangoma_isdn.c:791 Configuring ftmod_sangoma_isdn span = wp2 2010-10-09 18:28:58.487869 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter q921loglevel 2010-10-09 18:28:58.487927 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter q931loglevel 2010-10-09 18:28:58.487984 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter mode 2010-10-09 18:28:58.488039 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter dialect *2010-10-09 18:28:58.488076 [ERR] ftmod_sangoma_isdn_cfg.c:267 wp2: switchtype not specified2010-10-09 18:28:58.488096 [ERR] ftmod_sangoma_isdn.c:807 Failed to parse configuration 2010-10-09 18:28:58.488135 [ERR] mod_freetdm.c:2478 Error configuring Sangoma ISDN FreeTDM span 2* Your help is greatly appreciated, Neil On Fri, Oct 8, 2010 at 1:21 AM, Moises Silva <moises.silva@gmail.com> wrote:
On Thu, Oct 7, 2010 at 6:52 AM, Neil Patel <neilp@cs.stanford.edu> wrote:
...and here is the output from FS CLI. Note that the PRI line connected to port 2 (g2) works great; it is g1 that is producing the NO_ROUTE_DESTINATION error:
freeswitch@otalo> originate openzap/smg_prid/a/958655XXXX@g1 &echo 2010-10-07 18:08:25.273814 [WARNING] ozmod_sangoma_boost.c:344 TX EVENT: CALL_START:(80) [w1g1] CSid=5 Seq=41 Cn=[N/A] Cd=[958655XXXX] Ci=[N/A] Rdnis=[] 2010-10-07 18:08:25.306941 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT (N): CALL_START_ACK:(81) [w1g1] Rc=0 CSid=5 Seq=34 2010-10-07 18:08:25.307953 [NOTICE] switch_channel.c:675 New Channel OpenZAP/1:1/958655XXXX@g1 [c4305297-3a6e-4bd8-a25c-71e96da6b77d] 2010-10-07 18:08:25.411216 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT (N): CALL_STOPPED:(85) [w1g1] Rc=3 CSid=5 Seq=35 2010-10-07 18:08:25.411216 [NOTICE] mod_openzap.c:1935 Hangup OpenZAP/1:1/958655XXXX@g1 [CS_CONSUME_MEDIA] [NO_ROUTE_DESTINATION]
-ERR NO_ROUTE_DESTINATION
2010-10-07 18:08:25.412218 [NOTICE] switch_core_session.c:1188 Session 16 (OpenZAP/1:1/958655XXXX@g1) Ended 2010-10-07 18:08:25.412218 [NOTICE] switch_core_session.c:1190 Close Channel OpenZAP/1:1/958655XXXX@g1 [CS_DESTROY] 2010-10-07 18:08:25.441373 [WARNING] sangoma_boost_client.c:221 TX EVENT (N): CALL_STOPPED_ACK:(86) [w1g1] Rc=0 CSid=0 Seq=42 freeswitch@otalo> originate openzap/smg_prid/a/958655XXXX@g2 &echo 2010-10-07 18:08:30.199197 [WARNING] ozmod_sangoma_boost.c:344 TX EVENT: CALL_START:(80) [w1g1] CSid=6 Seq=43 Cn=[N/A] Cd=[958655XXXX] Ci=[N/A] Rdnis=[] 2010-10-07 18:08:30.263078 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT (N): CALL_START_ACK:(81) [w2g1] Rc=0 CSid=6 Seq=36 2010-10-07 18:08:30.264081 [NOTICE] switch_channel.c:675 New Channel OpenZAP/1:31/958655XXXX@g2 [fe1dad03-1086-4d56-bc55-62563e170a78] 2010-10-07 18:08:30.493273 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT: CALL PROGRESS:(50) [w2g1] CSid=6 Seq=37 Cn=[N/A] Cd=[N/A] Ci=[N/A] Rdnis=[] 2010-10-07 18:08:30.493273 [NOTICE] mod_openzap.c:1962 Pre-Answer OpenZAP/1:31/958655XXXX@g2!
+OK fe1dad03-1086-4d56-bc55-62563e170a78
I don't notice much going on in /var/log/sangoma_mgd.log or /var/log/messages, but then again I'm not sure what to look for. Any guidance would be greatly appreciated! Neil
Hi Neil,
Any reason you are using deprecated software? FreeTDM replaced openzap and libsng_isdn replaced boost.
See:
http://wiki.freeswitch.org/wiki/FreeTDM http://wiki.sangoma.com/FreeTDM-Sangoma-ISDN-Library
Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Neil Patel typed:
<param name="q921loglevel" value="alert"/> <param name="q931loglevel" value="alert"/> <param name="mode" value="user"/> <param name="dialect" value="5ess"/>
...
2010-10-09 18:28:58.487311 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter q921loglevel 2010-10-09 18:28:58.487369 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter q931loglevel 2010-10-09 18:28:58.487425 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter mode 2010-10-09 18:28:58.487480 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter dialect
http://wiki.sangoma.com/wanpipe-api-freetdm http://wiki.sangoma.com/Freeswitch-FreeTDM-Sangoma-ISDN-Library mose
I've already followed these steps... Wanpipe is compiled for FreeTDM and installed, and I have configured FS as above, based on Sangoma's instructions. -Neil On Sat, Oct 9, 2010 at 7:01 AM, Russell Mosemann <Russell.Mosemann@cune.org>wrote:
Neil Patel typed:
<param name="q921loglevel" value="alert"/> <param name="q931loglevel" value="alert"/> <param name="mode" value="user"/> <param name="dialect" value="5ess"/>
...
2010-10-09 18:28:58.487311 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter q921loglevel 2010-10-09 18:28:58.487369 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter q931loglevel 2010-10-09 18:28:58.487425 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter mode 2010-10-09 18:28:58.487480 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter dialect
http://wiki.sangoma.com/wanpipe-api-freetdm http://wiki.sangoma.com/Freeswitch-FreeTDM-Sangoma-ISDN-Library
mose
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Neil Patel <neilp@cs.stanford.edu> said:
I've already followed these steps... Wanpipe is compiled for FreeTDM and installed, and I have configured FS as above, based on Sangoma's instructions.
If that were true, we wouldn't see q921loglevel as a parameter below, and FS wouldn't be complaining about it. Maybe another look at the URLs I included would be helpful to see the valid parameters you can use for configuration.
On Sat, Oct 9, 2010 at 7:01 AM, Russell Mosemann <Russell.Mosemann@cune.org>wrote:
Neil Patel typed:
<param name="q921loglevel" value="alert"/>
2010-10-09 18:28:58.487311 [WARNING] ftmod_sangoma_isdn_cfg.c:262 Ignoring unknown parameter q921loglevel
http://wiki.sangoma.com/wanpipe-api-freetdm http://wiki.sangoma.com/Freeswitch-FreeTDM-Sangoma-ISDN-Library
-- Russell Mosemann ________________________________________________________ Concordia University, Nebraska See http://www.cune.edu/ for the latest news and events!
participants (4)
-
Moises Silva
-
Neil Patel
-
Russell Mosemann
-
Russell.Mosemann＠cune.org