[Freeswitch-users] span not defined error

Moises Silva moises.silva at gmail.com
Mon Jun 21 10:09:42 PDT 2010


Check the sangoma_prid log, from FS point of view there is nothing wrong.
Make sure you have defined g2 properly.

The sangoma_prid log is /var/log/sangoma_mgd.log


Moises Silva
Senior Software Engineer
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3
Canada
t. 1 905 474 1990 x 128 | e. moy at sangoma.com


On Mon, Jun 21, 2010 at 9:51 AM, Neil Patel <neilp at cs.stanford.edu> wrote:

> Hi Moises,
>
> I recently added a second PRI line to my A102 and followed your
> instructions below (modified /etc/wanpipe/smg_pri.conf; openzap.conf as
> shown below) and can successfully dial out with g1, but not the recently
> added second line set on g2. Below is the error we get:
>
> freeswitch at otalo> originate openzap/smg_prid/a/<num>@g2 &echo
> 2010-06-21 19:15:59.591930 [WARNING] ozmod_sangoma_boost.c:344 TX EVENT:
> CALL_START:(80) [w1g1] CSid=3 Seq=4 Cn=[N/A] Cd=[9586550654] Ci=[N/A]
> Rdnis=[]
> 2010-06-21 19:15:59.624992 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT
> (N): CALL_START_ACK:(81) [w2g1] Rc=0 CSid=3 Seq=6
> 2010-06-21 19:15:59.625987 [NOTICE] switch_channel.c:675 New Channel
> OpenZAP/1:31/<num>@g2 [19ae26fb-f9e4-480a-9cc7-11fa91b8bb1c]
> 2010-06-21 19:15:59.724996 [WARNING] ozmod_sangoma_boost.c:1632 RX EVENT
> (N): CALL_STOPPED:(85) [w2g1] Rc=3 CSid=3 Seq=7
> 2010-06-21 19:15:59.724996 [NOTICE] mod_openzap.c:1935 Hangup
> OpenZAP/1:31/<num>@g2 [CS_CONSUME_MEDIA] [NO_ROUTE_DESTINATION]
>
> -ERR NO_ROUTE_DESTINATION
>
> Seems like a config issue, but not sure what I'm missing. Any ideas?
>
> Thanks in advance,
> Neil
>
> On Sun, May 16, 2010 at 10:50 AM, Moises Silva <moises.silva at gmail.com>wrote:
>
>> Hi Again Neil,
>>
>> I just noticed your dial string is incorrect. The correct syntax is:
>>
>> OpenZAP/<span>/<chan_code>/[number]
>>
>> The span and chan code are mandatory. The number is optional ( FXS
>> channels do not require a number, they just ring the FXO device connected to
>> them).
>>
>> The span is either a number ( span id, the id is a number assigned in the
>> order in which the span is defined in openzap.conf ) or a span name also as
>> specified in the [span wanpipe <span_name>] line in openzap.conf
>>
>> The chan code is either a number ( for spans that support individual
>> channel selection, boost is NOT one of them ), or a channel hunting mode,
>> there is currently 2 modes, "a" is top down and "A" is bottom up.
>>
>> So, this is a valid string for you case:
>>
>> OpenZAP/smg_prid/a/<number>
>>
>> In the specific case of boost in socket mode ( openzap only supports
>> socket mode ) the number may contain @gX where X is a group ( for hunting as
>> configured in /etc/wanpipe/smg_pri.conf). Boost signaling are a special case
>> because the hunting for channels is not done within FreeSWITCH but in
>> sangoma_prid binary ( in the new OpenZAP version called FreeTDM this has
>> changed depending on configuration).
>>
>> Bottom line, this should work:
>>
>> OpenZAP/smg_prid/a/1234 at g1
>>
>> If you have g1 configured in /etc/wanpipe/smg_pri.conf
>>
>> Moises Silva
>> Senior Software Engineer
>> Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R
>> 9T3 Canada
>> t. 1 905 474 1990 x 128 | e. moy at sangoma.com
>>
>>
>> On Sat, May 15, 2010 at 6:26 PM, Neil Patel <neilp at cs.stanford.edu>wrote:
>>
>>> Span was originally in the boost section when I got this error, so I
>>> thought I'd try it in analog and both. None work.
>>>
>>> -Neil
>>>
>>> On Sat, May 15, 2010 at 3:18 PM, Moises Silva <moises.silva at gmail.com>wrote:
>>>
>>>> Why do you have 2 spans in openzap.conf.xml with the same name, in both
>>>> the boost and analog sections?
>>>> Moises Silva
>>>> Senior Software Engineer
>>>> Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R
>>>> 9T3 Canada
>>>> t. 1 905 474 1990 x 128 | e. moy at sangoma.com
>>>>
>>>>
>>>> On Sat, May 15, 2010 at 3:52 PM, Neil Patel <neilp at cs.stanford.edu>wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I am trying to dial out over my PRI, and am getting this error:
>>>>>
>>>>> 2010-05-16 01:01:21.452392 [CRIT] zap_io.c:1139 SPAN NOT DEFINED!
>>>>> 2010-05-16 01:01:21.452392 [ERR] mod_openzap.c:1154 No channels
>>>>> available
>>>>> 2010-05-16 01:01:21.452392 [ERR] switch_ivr_originate.c:2249 Cannot
>>>>> create outgoing channel of type [OpenZAP] cause: [NORMAL_CIRCUIT_CONGESTION]
>>>>>
>>>>>
>>>>> This is my 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
>>>>>
>>>>>
>>>>> This is my 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 lua code I'm using to dial out:
>>>>>
>>>>> sessiondata = "OpenZAP/smg_prid/<num>"
>>>>> new_session = freeswitch.Session(sessiondata)
>>>>>
>>>>>
>>>>> What am I missing here?
>>>>> Thanks,
>>>>> Neil
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>> _______________________________________________
>> 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
>>
>>
>
> _______________________________________________
> 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/20100621/c2e5d74b/attachment-0001.html 


More information about the FreeSWITCH-users mailing list