Mike Jerris asked me to move this conversation to
the -dev mailing list. That's why this
questions is here.
On September 19 2008 at 0:54
Michael Jerris wrote:
> my guess would be that it just fails to
load. what does the debug say?
>
> Mike
>
>
>> On Sep 18, 2008, at 1:19 PM, Evgeniy Zolotov
wrote:
>>
>> Thanks, Mike. But what dialect works when
we make
>>
>> <param name="dialect" value="ABC"
/>
>>
>> or
>>
>>
<param name="dialect" value="XYZ" />
( Previous part of conversation look at -user list: subjects "
mod_openzap and PRI " and
"mod_openzap ")
That's our debugging info:
....
freeswitch@opos9.altron.lan> console loglevel
9
freeswitch@opos9.altron.lan> load
mod_openzap
2008-09-19 13:11:14 [DEBUG] zap_io.c:1957 load_config() found
config for span
2008-09-19 13:11:14 [DEBUG] zap_io.c:1984 load_config()
created span 1 of type zt
2008-09-19 13:11:14 [DEBUG] zap_io.c:1997
load_config() span 1 [name]=[OpenZAP]
2008-09-19 13:11:14 [DEBUG]
zap_io.c:1997 load_config() span 1 [number]=[1]
2008-09-19 13:11:14 [DEBUG]
zap_io.c:1997 load_config() span 1 [trunk_type]=[E1]
2008-09-19 13:11:14
[DEBUG] zap_io.c:2001 load_config() setting trunk type to 'E1'
freeswitch@opos9.altron.lan> 2008-09-19
13:11:14 [DEBUG] zap_io.c:1997 load_config() span 1
[b-channel]=[1-15]
...
2008-09-19 13:11:14 [DEBUG] zap_isdn.c:1089 zap_isdn_configure_span()
opening d-channel #0 1:16
2008-09-19 13:11:14 [DEBUG] zap_isdn.c:1089
zap_isdn_configure_span() opening d-channel #0 2:16
2008-09-19 13:11:14
[DEBUG] zap_isdn.c:1089 zap_isdn_configure_span() opening d-channel #0
3:16
2008-09-19 13:11:14 [DEBUG] zap_isdn.c:1089 zap_isdn_configure_span()
opening d-channel #0 4:16
2008-09-19 13:11:14 [CONSOLE]
switch_loadable_module.c:778 switch_loadable_module_load_file() Successfully
Loaded [mod_openzap]
2008-09-19 13:11:14 [NOTICE]
switch_loadable_module.c:139 switch_loadable_module_process() Adding Endpoint
'openzap'
2008-09-19 13:11:14 [NOTICE] switch_loadable_module.c:237
switch_loadable_module_process() Adding Application 'disable_ec'
2008-09-19
13:11:14 [NOTICE] switch_loadable_module.c:257 switch_loadable_module_process()
Adding API Function 'oz'
API CALL [load(mod_openzap)]
output:
+OK
2008-09-19 13:11:14 [DEBUG] zap_isdn.c:865 zap_isdn_run() ISDN
thread starting.
2008-09-19 13:11:14 [DEBUG] zap_isdn.c:865 zap_isdn_run()
ISDN thread starting.
2008-09-19 13:11:14 [DEBUG] zap_isdn.c:865
zap_isdn_run() ISDN thread starting.
2008-09-19 13:11:14 [DEBUG]
zap_isdn.c:865 zap_isdn_run() ISDN thread starting.
- full content of
/usr/local/freeswitch/conf/autoload_configs/openzap.conf.xml is performed
below:
<configuration name="openzap.conf" description="OpenZAP
Configuration">
<settings>
<param
name="debug" value="1"/>
</settings>
<pri_spans>
<span id="1"> <!-- to PSTN
-->
<param name="mode" value="user"
/>
<param name="dialect" value="XYZ"
/>
<param name="dialplan"
value="XML"/>
<param name="context"
value="public"/>
</span>
<span id="2"> <!-- to PSTN -->
<param name="mode" value="user" />
<param name="dialect" value="li_ewsd" />
<param name="dialplan"
value="XML"/>
<param name="context"
value="public"/>
</span>
<span id="3"> <!-- to PSTN -->
<param name="mode" value="user" />
<param name="dialect" value="li_ewsd"
/>
<param name="dialplan"
value="XML"/>
<param name="context"
value="public"/>
</span>
<span id="4"> <!-- to PSTN -->
<param name="mode" value="user" />
<!--param name="dialect" value="national"
/-->
<param name="dialect"
value="li_ewsd"
/>
<param name="dialplan"
value="XML"/>
<param name="context"
value="public"/>
</span>
</pri_spans>
</configuration>
"span" 1 is deliberately configured with wrong
dialect.
In which way we are able to determine what dialect is used for
"span" 2 and "span" 3 -
our own "li_ewsd" or any else?
Thanks for your's previous answers, but we still need info on
this question.
Regards, Evgeniy