VoIP Mailing List Archives

[gcd at i.ph]

hi everybody,

i installed FS 1.0.2 to an Atom mobo (Intel D945GCLF2). it's working using IP phones, softphones and digium FXS port. but there's a problem in dialing out to PSTN using digium tdm400 fxo - it works fine on the first attempt (after starting FS) but it fails on the subsequent attempts. i tested to call using the FXS port and IP phone. same problem.

before i place any call, i checked >oz dump 2 1 (show current state = DOWN, last state = DOWN)

in the first call, there's this message:
[WARNING] mod_openzap.c:1196 on_fxo_signal() Unhandled type for channel 2:1
but

then i hangup. checked >oz dump 21 (show current state=DOWN, last state=HANGUP)

in the 2nd (and subsequent) attempts, the fxo just goes off-hook but doesn't send the dtmf tones.

[anthony.minessale at g...]

Its not detecting a dial tone on the failure case.
Before dialing it waits until it picks up dialtone.
Try the svn trunk version to see if it works any better or verify there is a dialtone on the line.

[gcd at i.ph]

i monitored the line using another phone. there's indeed dialtone in all attempts.
i see TONE_DETECTED in the first call but i wonder there's a WARNING message immediately following [WARNING] mod_openzap.c:1196 on_fxo_signal() Unhandled type for channel 2:1.
the dialtone freq should be okay since it's detected in the first call.could the WARNING message gives us a hint of a possible problem other than the dialtone freq?

okay, i'll try the SVN version next.


On Mon, Jan 26, 2009 at 10:18 AM, Anthony Minessale <anthony.minessale@gmail.com (anthony.minessale@gmail.com)> wrote:

[msc at freeswitch.org]

I have a TDM400 clone and I will see if I can reproduce these
symptoms. BTW, are you in the Philippines? Is there any difference in
the dial tone there than in the US?
-MC

On Sun, Jan 25, 2009 at 11:05 PM, Nandy Dagondon <gcd@i.ph> wrote:

[gcd at i.ph]

that's great. yes, i'm in the philippines. there's a difference in dialtone - it's 425 Hz.
-nandy


On Mon, Jan 26, 2009 at 6:01 PM, Michael Collins <msc@freeswitch.org (msc@freeswitch.org)> wrote:

[anthony.minessale at g...]

The unhanded type message just means that mod_openzap does not do anything with the TONE_DETECTED event that was passed
up from the ozmod_analog.

On Mon, Jan 26, 2009 at 7:32 AM, Nandy Dagondon <gcd@i.ph (gcd@i.ph)> wrote:

[raul at etellicom.com]

You may want to define the conf/tones.conf file with the proper tone
definitions for your country, then specify that tone group (tonegroup=XX
where XX is the 2 letters code for your country). For example, this is
the definition for my country (Brazil) and I also have tonegroup=br in
my openzap configuration file:

[br]
generate-busy => v=-7;%(250,250,425)
generate-dial => v=-7;%(1000,0,425)
generate-ring => v=-7;%(1000,4000,425)
generate-callwaiting-sas => v=0;%(300,10000,425)
detect-busy => 425
detect-dial => 425
detect-ring => 425
detect-callwaiting-sas => 425

Regards,

Raul Fragoso

On Mon, 2009-01-26 at 21:32 +0800, Nandy Dagondon wrote:

[gcd at i.ph]

i tested the SVN trunk version. still the same behaviour.
-nandy

On Tue, Jan 27, 2009 at 12:33 AM, Anthony Minessale <anthony.minessale@gmail.com (anthony.minessale@gmail.com)> wrote:

[gcd at i.ph]

hi everybody,

i created [ph] tone definition per raul's suggestion and changed /etc/zaptel.conf entries to:
tonezone=ph
defaultzone=ph

but it didn't solve the problem.

i captured the console log during start-up and shutdown. i noticed openzap related errors during shutdown. here's the snippet of the log:

STARTUP
---------------
2009-02-01 15:58:10 [NOTICE] zap_io.c:2517 zap_global_init() Modules configured: 1
2009-02-01 15:58:10 [INFO] zap_io.c:2341 zap_load_module() Loading IO from /opt/freeswitch/mod/ozmod_zt.so
2009-02-01 15:58:10 [INFO] zap_io.c:2127 load_config() auto-loaded 'zt'
2009-02-01 15:58:10 [INFO] ozmod_zt.c:186 zt_open_range() configuring device /dev/zap/channel channel 1 as OpenZAP device 1:1 fd:39
2009-02-01 15:58:10 [INFO] ozmod_zt.c:186 zt_open_range() configuring device /dev/zap/channel channel 2 as OpenZAP device 2:1 fd:40
2009-02-01 15:58:10 [INFO] zap_io.c:2265 load_config() Configured 2 channel(s)
2009-02-01 15:58:10 [INFO] zap_io.c:2358 zap_load_module() Loading SIG from /opt/freeswitch/mod/ozmod_analog.so
2009-02-01 15:58:10 [INFO] zap_io.c:2474 zap_configure_span() auto-loaded 'analog'
2009-02-01 15:58:10 [CONSOLE] switch_loadable_module.c:857 switch_loadable_module_load_file() Successfully Loaded [mod_openzap]

--- DIDN'T MAKE ANY CALL ---

SHUTDOWN
------------------
2009-02-01 15:59:07 [NOTICE] switch_loadable_module.c:536 switch_loadable_module_unprocess() Deleting API Function 'oz'
2009-02-01 15:59:07 [CONSOLE] switch_loadable_module.c:1231 do_shutdown() Stopping: mod_openzap
2009-02-01 15:59:07 [INFO] zap_io.c:256 zap_channel_destroy() Closing channel zt:1:1 fd:39
2009-02-01 15:59:07 [INFO] zap_io.c:256 zap_channel_destroy() Closing channel zt:2:1 fd:40
2009-02-01 15:59:08 [ERR] ozmod_analog.c:899 zap_analog_run() Failure Polling event! [no matching descriptor]
2009-02-01 15:59:08 [ERR] ozmod_analog.c:899 zap_analog_run() Failure Polling event! [no matching descriptor]
2009-02-01 15:59:08 [INFO] zap_io.c:2456 zap_unload_modules() Unloading /opt/freeswitch/mod/ozmod_analog.so
2009-02-01 15:59:08 [INFO] zap_io.c:2441 zap_unload_modules() Unloading IO zt
2009-02-01 15:59:08 [INFO] zap_io.c:2456 zap_unload_modules() Unloading /opt/freeswitch/mod/ozmod_zt.so

i also notice the same ERR flag during shutdown after making test calls.

any suggestion what to do next?

tks for your assistance.

rgds,
-nandy

On Tue, Jan 27, 2009 at 8:39 AM, Nandy Dagondon <gcd@i.ph (gcd@i.ph)> wrote:

[gcd at i.ph]

hi,

i found a major one. this time i deliberately set the dialtone freq to US std on my PH definition. i expect FS wont dial at all. but to my surprise, the problem is gone!! i checked the log. it indicates successful detection of DIALTONE.

going on further. i noticed FXO wont hangup on busy tone.

one possibility is the volume settings. the default is -7. how many dBm is this? and what is the dB equivalent per increment?

tks n rgds,
nandy

On Sun, Feb 1, 2009 at 4:30 PM, Nandy Dagondon <gcd@i.ph (gcd@i.ph)> wrote:

[anthony.minessale at g...]

the value is dB already -7dB

but for the detection section you do not specify anything but the list of frequencies needed to detect.

detect-ring => 440,480

this means it needs to detect a 440+480 to know there is a dialtone, the generate value has nothing to do with it.

openzap does not currently do busy detection to detect a hangup, but up in freeswitch you can use the tone_detect app to do this.


On Sun, Feb 1, 2009 at 3:17 AM, Nandy Dagondon <gcd@i.ph (gcd@i.ph)> wrote: