[Freeswitch-users] Sangoma prid and multiple PRIs with FreeSWITCH

Michael Collins msc at freeswitch.org
Wed May 5 12:33:49 PDT 2010


I believe we started a boost section on the openzap wiki page. If not, would
you mind adding these config examples? It would be very helpful for the next
poor soul coming along trying to work on this.

Thanks,
MC

On Wed, May 5, 2010 at 11:40 AM, Bryan Vyhmeister <freeswitch at bsdjournal.net
> wrote:

> 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.
>
> ;AFT-A102 on port 1
> signalling=pri_cpe
> switchtype=national
> group=1
> spans=1
>
> ;AFT-A102 on port 2
> signalling=pri_cpe
> switchtype=national
> group=2
> spans=2
>
> In openzap.conf.xml you only need one span:
>
> <configuration name="openzap.conf" description="OpenZAP Configuration">
>   <settings>
>     <param name="debug" value="0"/>
>   </settings>
>   <boost_spans>
> <span id="1">
>         <param name="node" value="cpe"/>
>         <param name="switch" value="ni2"/>
> <param name="dialplan" value="XML"/>
>  <param name="context" value="public"/>
> </span>
>   </boost_spans>
>    <analog_spans>
>   </analog_spans>
>  </configuration>
>
> And the same in openzap.conf however you need to define the channels of
> both physical PRI circuits.
>
> [span wanpipe 1]
> name => 1
> trunk_type =>t1
> b-channel => 1:1-23
> b-channel => 2:1-23
>
> When you dial, instead of using openzap/1 or openzap/2 you have to use
> groups. This would be the first PRI dial string:
>
> <action application="bridge" data="openzap/1/a/$1 at g1"/>
>
> This would be the second PRI dial string:
>
> <action application="bridge" data="openzap/1/a/$1 at g2"/>
>
> 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!
>
> Bryan
>
>
> On Wed, May 5, 2010 at 11:01 AM, Bryan Vyhmeister <
> freeswitch at bsdjournal.net> wrote:
>
>> 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:
>>
>> 2010-05-05 09:42:02.573743 [CRIT] ozmod_sangoma_boost.c:257 SPAN is not
>> online.
>> 2010-05-05 09:42:02.573743 [ERR] switch_ivr_originate.c:2480 Cannot create
>> outgoing channel of type [openzap] cause: [NORMAL_CIRCUIT_CONGESTION]
>>
>> When I start FreeSWITCH up I get this error on the console right after all
>> the channels are activated.
>>
>> 2010-05-05 07:25:59.414444 [ERR] ozmod_sangoma_boost.c:1534 Error: Opening
>> MCON Socket [-1] Address already in use
>>
>> The configs are below:
>>
>> openzap.conf
>> [span wanpipe 1]
>> name => 1
>> trunk_type =>t1
>> b-channel => 1:1-23
>> [span wanpipe 2]
>> name => 2
>> trunk_type =>t1
>> b-channel => 2:1-23
>>
>> openzap.conf.xml
>> <configuration name="openzap.conf" description="OpenZAP Configuration">
>>   <settings>
>>     <param name="debug" value="0"/>
>>   </settings>
>>   <boost_spans>
>> <span id="1">
>>         <param name="node" value="cpe"/>
>>         <param name="switch" value="ni2"/>
>> <param name="dialplan" value="XML"/>
>>  <param name="context" value="public"/>
>> </span>
>>  <span id="2">
>>         <param name="node" value="cpe"/>
>>         <param name="switch" value="ni2"/>
>>  <param name="dialplan" value="XML"/>
>> <param name="context" value="public"/>
>>   </boost_spans>
>>   <analog_spans>
>>   </analog_spans>
>> </configuration>
>>
>> I'm dialing with this dial string.
>>
>>         <action application="bridge"
>> data="{origination_caller_id_number=${outbound_caller_id_number}}openzap/2/a/$1"/>
>>
>> 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.
>>
>> My question is how can I get two PRI's working with Sangoma's smg_prid?
>> Thank you.
>>
>> Bryan
>>
>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20100505/e9da8e01/attachment-0001.html 


More information about the FreeSWITCH-users mailing list