if the problem is solved in that version. For the time being I have
removed cadence specification from any calls to Dial or Queue for FXS.
Cheers,
Panos
On Wed, May 23, 2012 at 7:31 PM, Shaun Ruffell sruff...@digium.com wrote:
On Wed, May 23, 2012 at 07:13:01PM +0300, Roeften wrote:
Hello
Hello everyone,
Just thought to let you know of a weird issue in Asterisk 1.8.? + Dahdi
2.6.? (and 2.5.?).
When you specify any cadence in an app (Dial, Queue) then caller id does
not work.
For instance with the default cadences (everything commented out in
chan_dahdi.conf) :
Dial(DAHDI/54)
Hello everyone,
I've just upgraded from 1.6.1.9 to 1.6.2.13.
I have noticed that (after the upgrade) abandoned calls within the Queue
produce no cdr at all.
I am using unanswered = no (the default) in cdr.conf.
The call shows, as expected, in the queue_log as ABANDON
The dialplan is:
Apologies, I've accidentally sent the email before finishing it.
As said, I've just upgraded from 1.6.1.9 to 1.6.2.13.
With unanswered = no (the default) in cdr.conf. and a dialplan:
*Ringing();
Answer();
Queue(hotelq,t,,,${QUEUE_TIMEOUT});
Background(vm-nobodyavail);
Voicemail(${HOTELVM});
Current issue with s4a is that you never see who is actually calling.
You always see only the skype user on the s4a server. Like in the old
days without CLIP/CLIR.
Hm, I can actually see who's calling (see SKYPE_CALL_PROPERTY(fullname) etc
variables).
From what I understand your sip client can handle g729 whereas for DAHDI you
need transcoding to a|ulaw.
I am using it with no problems (have g729 licenses as well though).
A bit off topic, I have found some extra configuration that is not really in
the docs (or I could not find them):
Hello everyone,
I am trying to find out whether AOC (any of the 3 types) is currently
supported by Asterisk and for which hardware combination.
Does anyone know if AOC info can be used in the CDR when the interface to
the outside world is ISDN BRI (not pri) and the internal counterpart
