Messages

1

Running WombatDialer / Re: problems making calls

« on: June 14, 2013, 12:45:51 »

Thanks for your answer.
I will take a look at that link and try the set up you suggest.

And about the local example, we don't use a 9 or any other number to get external line. There are dialing patterns configured to be able to make external calls directly.

(We do need a 0 to get out of our centrex service provided by the telco, but that 0 is added automatically on our dial rules (for that reason, when I define the Dahdi trunk I use "0${num}" .) )

Thanks again.

2

Running WombatDialer / problems making calls

« on: June 13, 2013, 15:07:12 »

Hi folks.

I have been testing Wombat Dialer and I like it very much. I am trying to use it at the company where I work to make automated calls to our customers.

I am still testing Wombat, and although it mostly works, I have encountered a problem I still could not solve.

I use Elastix and I have installed Wombat in a different computer.

On the Elastix box, I added to manager_custom.conf the following lines:


[wombat]
secret= womBat
deny=0.0.0.0/0.0.0.0
permit=192.168.0.0/255.255.255.0
read = system,call,log,verbose,command,agent,user,originate
write = system,call,log,verbose,command,agent,user,originate

Then, in the Wombat interface I define trunks in two ways, but with both I am getting problems.

First I defined a local trunk: Local/${num}@from-internal

With this trunk I am able to make campaigns and call to extensions in my network.
But when I try to call an outside number, apparently there is a problem with the authentication, because although I define the dial account in the campaign, I can see in the logs that Asterisk is playing the "code incorrect" audio message when Wombat tries to make the call.

I also tried defining a trunk with this string: DAHDI/8/0${num} 
(that is my 8th line, and I use the 0 to be able to get external line)

With that setting, I could make just one call. The other numbers got the REJECTED status in the Wombat logs.

If I check the Asterisk logs, I have these lines:

(...)
[Jun 12 18:10:04] VERBOSE[901] func_timeout.c: Channel will hangup at 2013-06-12 18:12:04.980 ART.
[Jun 12 18:10:05] VERBOSE[901] sig_analog.c:     -- Hanging up on 'DAHDI/8-1'
[Jun 12 18:10:05] VERBOSE[901] chan_dahdi.c:     -- Hungup 'DAHDI/8-1'
[Jun 12 18:10:05] NOTICE[902] channel.c: Unable to request channel DAHDI/8/04439809
[Jun 12 18:10:06] NOTICE[903] channel.c: Unable to request channel DAHDI/8/0154296362
[Jun 12 18:10:06] NOTICE[904] channel.c: Unable to request channel DAHDI/8/04402773
[Jun 12 18:10:06] NOTICE[905] channel.c: Unable to request channel DAHDI/8/04423508
[Jun 12 18:10:06] NOTICE[906] channel.c: Unable to request channel DAHDI/8/04592705
(...)

Any ideas about how to solve these problems?

Thank you very much in advance.
Greetings from Argentina.