* You are viewing the archive for September 3rd, 2010

How to tell if there is a transfer from CDR?

Is there any way to know if a call was transferred from reading the
CDR? Any relation in fields like UNIQUEID? Something that can be
scripted to make a special report?

UK-specific hardware recommendations (FXOand FXS)

Roger Burton West wrote:

> I want to hook one of them to the PSTN. Given that I am in
> the UK, what is a reasonably easily-available device to
> provide an FXO interface from a Linux box, with a minimum of
> faffing around with drivers? Just one line is needed, though
> in theory two might eventually be useful. My usual white-box
> hardware suppliers don’t seem to play in this field.

I’ve had good experiences with an OpenVox A400P, once you’ve done the “Dahdi
dance”, it settles down to be very reliable. Reasonable price, too. I bought
mine from Voipon, although I’m sure a bit of shopping around will find other
vendors.

Cheers,
Ade.

Faxes

We have asterisk connected to the PSTN VIA TE410P (ANSI SS7 to T1 PRI)
cards.

I am having trouble completing faxes. Carrier send calls to me using SIP.
Any recommendation to have some success with Fax.

We trying using T.38 pass through and using G711U codec.

Asterisk Version 1.6.1.1

Thanks,

Dave

DAHDI-linux & DAHDI-tools 2.4.0 Release Announcement

The Asterisk Development Team is pleased to announce the release of
DAHDI-Linux and DAHDI-Tools version 2.4.0.

DAHDI-Linux 2.4.0, DAHDI-Tools 2.4.0, and DAHDI-Linux-Complete are
available for immediate download at:
http://downloads.asterisk.org/pub/telephony/dahdi-linux
http://downloads.asterisk.org/pub/telephony/dahdi-tools
http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete

In addition to several bug fixes, the most significant changes from the
2.3.0 release are:

General DAHDI Changes:

* Added DAHDI_MAINT_ALARM_SIM maintenance mode for drivers that
support alarm simulation (wct4xxp). This is only used by
dahdi_maint and doesn’t change the ABI.

* Span callbacks are moved out of the dahdi_span structure potentially
saving memory when a single driver implements multiple spans.

Updated Drivers:

* wctdm24xxp, wcte12xp: Fix bug when moving to memory mapped registers
where the interrupt handler was run twice for every interrupt.

* wctdm24xxp, wcte12xp: Processing moved back to interrupt handler.
(Closes issue #17289 Reported by alecdavis)

* wctdm24xxp, wcte12xp: Update VPMADT032 firmware to 1.25. Contains
improvements to prevent loss of convergence when signal levels go
over a certain threshold and for handling line condition changes.

* wctdm24xxp: Fix race conditions/improvements in FXS line feed register
handling.
(Closes issues #17724 and #17764. Reported and patched by alecdavis)

* wctdm24xxp: Added “companding” module parameter to replace
“alawoverride”. When BRI modules are installed on a Hx8 board alaw is
the default companding so change the semantics to just allow the
companding to be forced as opposed to overriding a default. The
default is “auto” which means alaw if there are BRI modules, otherwise
ulaw.

* wctdm24xxp: Set ‘spantype’ for digital spans so that they can be
displayed with dahdi_scan.

* wcte12xp: dahdi_cfg does not need to be called twice when using RBS
signalling.

* wcte12xp: Loopback module parameter removed since ‘dahdi_maint’ can
now put the spans in digital loopback.

* wct4xxp: Add ‘latency’, ‘max_latency’, and ‘ms_per_irq’ module
parameters to set expected latency conditions when using Gen5
firmware.

* wct4xxp: Added support for network loopback modes via dahdi_maint.

* wct4xxp: Which span is providing card timing is now exported via
sysfs.

* wcb4xxp: Fixed pulse mask for improved TBR3 compliance.

* wcb4xxp: Added pci-ids for Junghanns PCI-E cards.

* wcb4xxp: Added ‘companding’ module parameter.

* wcb4xxp: Fixed bug when using automatic timing sync.

* wcb4xxp: Which span is providing card timing is now exported via
sysfs.

* wctdm: Added configurable debounce to support old rotary phones.
(Closes issue #16339. Reported by alecdavis patch by tilghman.)

* xpp:
FXS: support VMWI config from Asterisk >= 1.6.1
PRI:
- PRI Astribanks always sync AB (and independent)
- don’t send “duplicates” in E1 as in D4
- Reduce noise at E1 startup.
- T1 CAS fixes.
PIC 4 rev. 7381: fix T1 returning signaling register in non-CAS

Changes to dahdi-tools:

* dahdi_maint: Added support for simulating alarm conditions.

* dahdi_scan: Report more detailed alarm information.

* xpp_fxloader:
- Load firmware in the background
- Support 1163 twinstar devices
- A delay loop for older kernels (e.g. 2.6.18)

* astribank_is_starting does not depend on libusb.

* Allow using CONNECTOR/LABEL in genconf_parameters for pri_termtype

For a full list of changes in these releases, please see the ChangeLogs at
http://svn.asterisk.org/svn/dahdi/linux/tags/2.4.0/ChangeLog and
http://svn.asterisk.org/svn/dahdi/tools/tags/2.4.0/ChangeLog

Issues found in these releases can be reported at http://issues.asterisk.org

Thank you for your continued support of Asterisk!

How to use MYSQL(Set timeout x)

I use Asterisk 1.6.2.11 and this is my dialplan:

[test]
exten => 9999,1,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,Answer()
exten => 9999,n,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,PlayBack(hello-world)
exten => 9999,n,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,MYSQL(Set timeout 2)
exten => 9999,n,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,MYSQL(Connect connid localhost user pass asterisk)
exten => 9999,n,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,MYSQL(Query resultid ${connid} SELECT SLEEP(10))
exten => 9999,n,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,MYSQL(Fetch fetchid ${resultid} RESULT)
exten => 9999,n,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,MYSQL(Clear ${resultid})
exten => 9999,n,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,MYSQL(Disconnect ${connid})
exten => 9999,n,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,NoOp(Result: ${RESULT})
exten => 9999,n,NoOp(${STRFTIME(${EPOCH},,%Y-%m-%d %H:%M:%S)})
exten => 9999,n,Hangup()

When i call to 9999 this is the CLI output:

Connected to Asterisk 1.6.2.11 currently running on Asterisk (pid = 2092)
Verbosity is at least 2147483647
Asterisk*CLI>
== Using SIP RTP CoS mark 5