On Fri, Dec 30, 2011 at 8:10 PM, Kaushal Shriyan
> I get this warning "[Dec 30 19:59:20] WARNING: app_dial.c:1353
> wait_for_answer: Unable to write frametype: 2" on Asterisk *CLI>
> Any clue ?
> Please let me know if anyone needs any additional information or details
> of configuration files.
Hi, Checking in again for my earlier post to this Mailing List. Regards, Kaushal
I am looking for a good Outbound Dialer and to be practical with possibility to do modification on it, the outbound dialer should send the calls to the agent when the agent is logged in as long the agent is belong to the queue (or let us say the skill group of this campaign).
Any one can guide me?
If I can build this using the AMI, so I appreciate if anyone did it before me so I can use his help.
I am playing around with Asterisk 184.108.40.206 from Digium repository. This is
all there is to my logger.conf file: *[general]*
*full => notice,warning,error,debug,verbose,dtmf,fax*
However, when I do, "core set verbose 0" at CLI, Asterisk ceases to write
to /var/log/asterisk/full file for some reason. When I type "core set
verbose 9" at CLI then it starts writing to /var/log/asterisk/full. Is this
the correct behaviour or am I missing a config setting? Of course I want the /var/log/asterisk/full file to always…
I get this warning "[Dec 30 19:59:20] WARNING: app_dial.c:1353
wait_for_answer: Unable to write frametype: 2" on Asterisk *CLI> Any clue ? Please let me know if anyone needs any additional information or details of
configuration files. Regards, Kaushal
I need to recompile asterisk to install some apps.
Does anyone has a good tutorial on how to do this ? I've asterisk
1.4.13 installed should I upgrade to 1.6 ? will I benifit from video
improvements if I upgrade ? Will I loose asterisk settings if I recompile ?
If you have previously recompiled asterisk please let me know your
Any information about this will be very welcome.
The Asterisk Development Team has announced the release of Asterisk 220.127.116.11.
This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 18.104.22.168 resolves a regression introduced in Asterisk
22.214.171.124 reported by the community, and would have not been possible without your
participation. Thank you! The following is the issue resolved in this release: * Handle AST_CONTROL_UPDATE_RTP_PEER frames in local bridge loop Failing to handle AST_CONTROL_UPDATE_RTP_PEER frames in the local bridge loop
causes the loop to exit prematurely. This causes a variety of negative side
effects, which may include having…
My question in short: what is the best practise for a small company (30-50
users) with one operator that answers each call? I am a developer and now working on the implementation of Asterisk in our
company. With the definitive guide next to me, the scripting of extensions
and configuring trunks isn't that hard from what I have read until now.
What worries me is what the best way would be to get our operator to work
nicely / efficiently. On one location we have a receptionist who takes the
calls to our…
I've been trying to fix NOTIFY replies (specifically keep-alives) in 1.4.42
(I can't upgrade to 1.8.x at the moment for various reasons). I've noticed for user agents that have a VIA header with a different
port than the port the NOTIFY was sent from,
the NOTIFY reply will always be sent back to that port, which is incorrect.
(Sonicwalls and other routers love to do this, even with "Symmetric NAT" on).
The reason for this is that the NOTIFY reply does not attempt to
lookup the SIP peer and check
I know this is more a Digium hardware than an Asterisk issue. Already
posted a question at Digium, however also like to see whether anyone in the
Asterisk community has encountered the following situation: I installed a Digium B410P BRI PCI card on my new asterisk server,
following the steps specified in the manual. I can see the PCI card is
available using the lspci command: ...
04:00.0 Ethernet controller : Intel Corporation 82574L Gigabit
Network Connection [8086:10d3]
05:00.0 Ethernet controller : Intel Corporation 82574L Gigabit
Network Connection [8086:10d3]
> 1. I checked the log and I don't see any registration attempt, so I *assume*
> they simply send an invite, and so they are in the external/outside context
> of my dialplan. So they are trying to reach extensions which don't exist.
> If they succesfully registered they would be on the internal context, and
> their calls would have succeeded. (Or am I missing something?). I actually
> see nothing in the log but the notice (and nothing on the CLI but the
> notice)...so I assume it is…