I just spoke with Sangoma tech support. I am posting a workaround solution here in case someone else runs into the same problem. As long as both spans use the same switch type, FreeSWITCH can see both as the same span. In /etc/wanpipe/smg_pri.conf, you need to define a separate group for each span.<div>
<br></div><div><div>;AFT-A102 on port 1</div><div>signalling=pri_cpe</div><div>switchtype=national</div><div>group=1</div><div>spans=1</div><div><br></div><div>;AFT-A102 on port 2</div><div>signalling=pri_cpe</div><div>switchtype=national</div>
<div>group=2</div><div>spans=2</div><div><br></div><div>In openzap.conf.xml you only need one span:</div><div><br></div><div><div><configuration name="openzap.conf" description="OpenZAP Configuration"></div>
<div> <settings></div><div> <param name="debug" value="0"/></div><div> </settings></div><div> <boost_spans></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><span id="1"></div>
<div> <param name="node" value="cpe"/></div><div> <param name="switch" value="ni2"/></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><param name="dialplan" value="XML"/></div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span><param name="context" value="public"/></div><div><span class="Apple-tab-span" style="white-space:pre"> </span></span></div>
<div> </boost_spans></div><div> <analog_spans></div><div> </analog_spans></div><div> </configuration></div><div><br></div><div>And the same in openzap.conf however you need to define the channels of both physical PRI circuits.</div>
<div><br></div><div><div>[span wanpipe 1]</div><div>name => 1</div><div>trunk_type =>t1</div><div>b-channel => 1:1-23</div><div>b-channel => 2:1-23</div><div><br></div><div>When you dial, instead of using openzap/1 or openzap/2 you have to use groups. This would be the first PRI dial string:</div>
<div><br></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><action application="bridge" data="openzap/1/a/$1@g1"/></span></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">This would be the second PRI dial string:</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><span class="Apple-style-span" style="font-size: 13px; "><action application="bridge" data="openzap/1/a/$1@g2"/></span></span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">This works as expected. Apparently there will be a new way of interacting with smg_prid coming out at some point that will address these issues and allow multiple spans and switch types in the openzap configs. Thanks to Sangoma for the great hardware and drivers and the FreeSWITCH project for a fantastic product!</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Bryan</span></font></div>
<div><br></div></div></div><br><div class="gmail_quote">On Wed, May 5, 2010 at 11:01 AM, Bryan Vyhmeister <span dir="ltr"><<a href="mailto:freeswitch@bsdjournal.net">freeswitch@bsdjournal.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I setup a FreeSWITCH pbx with a Sangoma A102D card, the latest FreeSWITCH as of yesterday, and Wanpipe 3.5.11. I have found that I cannot use both PRI ports with Sangoma's smg_prid. The first one always works great but the second one never works. I get the following error:<div>
<br></div><div><div>2010-05-05 09:42:02.573743 [CRIT] ozmod_sangoma_boost.c:257 SPAN is not online.</div><div>2010-05-05 09:42:02.573743 [ERR] switch_ivr_originate.c:2480 Cannot create outgoing channel of type [openzap] cause: [NORMAL_CIRCUIT_CONGESTION]</div>
<div><br></div><div>When I start FreeSWITCH up I get this error on the console right after all the channels are activated.</div><div><br></div><div><div>2010-05-05 07:25:59.414444 [ERR] ozmod_sangoma_boost.c:1534 Error: Opening MCON Socket [-1] Address already in use</div>
<div><br></div><div>The configs are below:</div><div><br></div><div>openzap.conf</div><div><div>[span wanpipe 1]</div><div>name => 1</div><div>trunk_type =>t1</div><div>b-channel => 1:1-23</div><div>[span wanpipe 2]</div>
<div>name => 2</div><div>trunk_type =>t1</div><div>b-channel => 2:1-23</div><div><br></div><div>openzap.conf.xml</div><div><div><configuration name="openzap.conf" description="OpenZAP Configuration"></div>
<div> <settings></div><div> <param name="debug" value="0"/></div><div> </settings></div><div> <boost_spans></div><div><span style="white-space:pre"> </span><span id="1"></div>
<div> <param name="node" value="cpe"/></div><div> <param name="switch" value="ni2"/></div><div><span style="white-space:pre"> </span><param name="dialplan" value="XML"/></div>
<div><span style="white-space:pre"> </span><param name="context" value="public"/></div><div><span style="white-space:pre"> </span></span></div>
<div><span style="white-space:pre"> </span><span id="2"></div><div> <param name="node" value="cpe"/></div><div> <param name="switch" value="ni2"/></div>
<div><span style="white-space:pre"> </span><param name="dialplan" value="XML"/></div><div><span style="white-space:pre"> </span><param name="context" value="public"/></div>
<div> </boost_spans></div><div> <analog_spans></div><div> </analog_spans></div><div></configuration></div><div><br></div><div>I'm dialing with this dial string.</div><div><br></div><div><div>
<action application="bridge" data="{origination_caller_id_number=${outbound_caller_id_number}}openzap/2/a/$1"/></div><div><br></div><div>I am certain the rest of this config works fine because the other PRI works great. I have also attempted to use FreeSWITCH without Sangoma's smg_prid by specifying a d-channel in openzap.conf. That seems to work but calls tend to drop frequently. I would rather just use Sangoma's smg_prid. I also attempted a hybrid config where FreeSWITCH worked without smg_prid on the first PRI and the second PRI was handled by smg_prid. That config worked except for the dropped calls that happen with using FreeSWITCH to manage the d-channel.</div>
<div><br></div><div>My question is how can I get two PRI's working with Sangoma's smg_prid? Thank you.</div><div><br></div><font color="#888888"><div>Bryan</div>
</font></div></div></div></div></div>
</blockquote></div><br></div>