Commit Graph

14 Commits

Author SHA1 Message Date
Andreas Eversberg 034d3a9140 Data-Over-Voice
An experimental feature to send and receive an identification over
voice channel.

If a party answers, the ID is transmitted some seconds afterwards.
The calling party listens 30 seconds after receiving an answer message
for the ID.

Add to your extension's settings file:

dov_ident  <id string without white spaces>
dov_log    /path/to/log/file
dov_type   pwm|pcm
dov_level  0|level

'pwm' survives analog transcoding.
'pcm' is fast and will almost not be recognised.
'level' can be used to alter default signal amplitude (100..30000).
2015-12-15 14:27:23 +01:00
Andreas Eversberg e233557e40 Experimental crypto feature: Support for libvootp 2015-12-15 07:59:12 +01:00
Andreas Eversberg 705f2dac84 Fixed early audio with chan_lcr (Asterisk)
If progress message is received, go into proceeding state.

Send audio, if proceeding/alerting state, so RTP stream is sent in both
directions. This is essential when using NAT.
2012-12-16 10:11:47 +01:00
Andreas Eversberg d3b4611440 Fix: Allow recording of audio for SIP/remote/GSM interfaces too 2012-12-16 10:11:47 +01:00
Andreas Eversberg bdd274c5e8 Fix: Don't forward MESSAGE_TRAFFIC to endpoint instance
Thanx to Atul for catching this bug
2012-12-16 10:11:46 +01:00
Andreas Eversberg b971fdeb62 Store caller/dialing info for calls via remote interfaces (chan_lcr) 2012-12-16 10:11:46 +01:00
Andreas Eversberg c33007184d Fix: Send tones/patterns/announcements for remote connections 2012-12-16 10:11:46 +01:00
Andreas Eversberg 68ccf0448d Add screening of caller ID for remote (asterisk) connections 2012-12-16 10:11:46 +01:00
Andreas Eversberg 7f0d14c706 Cleanup: Make interface name be part of Port class 2012-12-16 10:11:46 +01:00
Andreas Eversberg 240562640f Maintain states for remote socket connections 2012-12-16 10:10:33 +01:00
Andreas Eversberg f6aea744f8 Removed complete bchannel handling from chan_lcr
The remote application interface does not allow any bchannel to be
exported or imported. Audio traffic via socket interface is used instead.

The joinremote instance became obsolete and is removed.

The remote action (routing) became obsolete, use interface.conf instead.

The handling of loopback device became obsolete and was removed

The chan_lcr does not rely on mISDN anymore, that means:
- can be used with GSM and without mISDN at all.
- chan_lcr can be used as internal extension of LCR (e.g. SIP phone)
  (chan_lcr can be handled as any other interface)
- no loopback device to be used anymore.
2012-12-16 10:10:32 +01:00
Andreas Eversberg 74a7fe54a8 Adding simple bridge application to forward calls without PBX app.
Call received on an interface can directly be forwarded to a given
destination interface, instead of routing the call through PBX
application. This way calls can be forwarded without going through
route.conf.

Currently only SIP and GSM destinations are supported. Also there
are no tones generated, if one side provides no tones, but the
other wants to receive them.

The keyword "bridge <output interface>" in interface.conf is used.
Without that keyword, incomming calls are handled as usual.
2012-01-16 09:14:22 +01:00
Andreas Eversberg 9f505bd729 Additionally adding output of bchannel "ref" at some debug output. 2011-08-11 15:23:23 +02:00
Andreas Eversberg 3a8f58ec89 Adding interface support for remote app (chan_lcr).
chan_lcr can be handled as an interface. This way it is possible to (e.g.):
- make a SIP phone become an LCR extension with all LCR features.
- make conference calls. (untested)
- perform parallel ringing. (ISDN phone and SIP phones can ring in
  parallel.)
- do voice recoding.

It is still also possible to link chan_lcr directly without interface
(as before).

Documentation/howto for that will follow.
2010-12-13 09:22:49 +01:00