Author Topic: problems making calls  (Read 3898 times)

aarrieta

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
    • View Profile
    • Email
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.




QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: problems making calls
« Reply #1 on: June 14, 2013, 10:49:49 »
I believe that the second example makes sense: if you set up a trunk with a capacity of (say) 10, Wombat will try and send 10 calls at once. But as that is a physical line, its capacity is 1. :) My suggestion to use dahdi is to create a group of (say) 5 channels and set up the trunk to have a capacity of 5. See http://www.voip-info.org/wiki/view/Asterisk+config+chan_dahdi.conf

As per the Local example, most likely you'll be dialing Local/9${num}@from-internal to dial the number ${num} on the PSTN. May that be the case? (in general, calling directly a DAHDI or SIP interface is better as on default Local channels a lot of dialplan gets run and Wombat does not usually need it).




aarrieta

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
    • View Profile
    • Email
Re: problems making calls
« Reply #2 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.

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: problems making calls
« Reply #3 on: June 17, 2013, 09:59:14 »
It is weird that the Local channel does not work then. Do you have a CLI trace of what happens (make sure you send only one call - FreePBX logs get very hard to read quickly).