Chan_capi

SoftIP Trial PPC

mohamadi.maryam66@gmail.com — Sat, 22 Oct 2011 07:49:34 GMT

Hi,

Can any one help me how to get PPC code of SoftIP in trial mode?I can not find any thing in site!

Use of chan_capi with Diva SS7

vladimir.startsev@eicon.com — Tue, 18 Aug 2009 21:16:40 GMT

Diva SS7 allows use of SS7 signaling with chan_capi. No changes to chan_capi or chan_capi configuration are necessary. Diva SS7 provides converion between SS7 protocol towards network and ETS 300 102-1 towards chan_capi. This allows use of existing chan_capi implementation and configuration without changes.

The solution allows simple implementation of gateways between SS7 and SIP, SS7 and local ISDN/PSTN networks.

Diva SS7 configuration (Diva demo system)

Diva chan_capi (capi.conf, modules.conf) configuration (Diva demo system)

chan_capi and chan_dialogicdiva 1.1.4 released now

vladimir.startsev@eicon.com — Tue, 18 Aug 2009 20:55:43 GMT

Based on chan_capi rev 737

chan_capi and chan_dialogicdiva 1.1.3 released now

vladimir.startsev@eicon.com — Tue, 04 Aug 2009 10:24:03 GMT

New stable version of chan_capi and chan_dialogicdiva are branched at version 1.1.3 and released now

Download

New command for conference management added to chan_capi

vladimir.startsev@eicon.com — Thu, 16 Jul 2009 14:59:52 GMT

(from README.media)

chat_command

Description:
Used to send command to conference.

Supported hardware:
Diva

Syntax:
capicommand(chat_command|options|roomname)
options - mandatory
r - Remove newest user from conference.
Command does not apply to calling member and be used by operators only.
l - Remove all listeners from conference.
Command does not apply to calling member and be used by operators only.
o - Remove all operators from conference.
Command does not apply to calling member and be used by operators only.
a - Remove all users from conference.
Command does not apply to calling member and be used by operators only.
roomname - optional, room caller assigned to is used if not present

Syntax example:
exten => s,n,capicommand(chat_command|r)
exten => s,n,capicommand(chat_command|lo|test)
exten => s,n,capicommand(chat_command|a|test)

Conference example:
/////////////////////////////////////////////////////////////////////
[isdn-in]
exten => _X.,1,Answer
exten => _X.,n,Authenticate(12345)
exten => _X.,n,Playback(vm-rec-name)
exten => _X.,n,Record(/tmp/name${UNIQUEID}.alaw,5,15) ; Record name
exten => _X.,n,capicommand(chat_play|c1||/tmp/name${UNIQUEID}.alaw|1-4) ; Play name to conference
exten => _X.,n,capicommand(resource|1-4) ; Create resource PLCI if call from IP
exten => _X.,n,capicommand(clamping|200) ; Activate suppression of DTMF codes
exten => _X.,n,capicommand(vc|chat_mute|1|yes) ; Voice command, key 1 - mute all members except operators
exten => _X.,n,capicommand(vc|chat_mute|2|no) ; Voice command, key 2 - unmute all members except operators
exten => _X.,n,capicommand(vc|chat_command|0|a|c1) ; Voice command, key 0 - disconnect all members
exten => _X.,n,capicommand(vc|noisesuppressor|3|yes) ; Voice command, key 3 - turn noise suppression on
exten => _X.,n,capicommand(vc|noisesuppressor|4|no) ; Voice command, key 4 - turn noise suppression off
exten => _X.,n,capicommand(chat|c1|mo|1-4) ; Add caller to conference as operator

Re: Question form support: Asterisk Konferenzen / Timingdevice

vladimir.startsev@eicon.com — Thu, 16 Jul 2009 13:33:05 GMT

In case Diva is used for conferencing then "chat" chan_capi command should be used instead of MeetMe.

Using "chat" conference is done on Diva hardware and not on host. Diva hardware will use internal clock (from TDM or from internal clock source) if necessary. "chat" can span conferences over multiple Diva boards.

Using "chat" this is possible interconnect E.1/T.1/S.0 and IP members and to span conferences over multiple Diva board. This allows not only to offload host but provide for all participants (inclusive IP participants) conference with active talker evaluation and media processing (noise suppression, dtmf detection, digital gain control, ...)

Use of "chat" chan_capi command together with "vc" chan_capi command allows interactive change (in real time) of apllied to media streams media processing.

Please read more about "chat", "chat_play", "chat_mute", "vc" and "resource" chan_capi commands in README.media

exten => 2001,1,Answer
exten => 2001,n,Authenticate(12345)
exten => 2001,n,Playback(vm-rec-name)
exten => 2001,n,Record(/tmp/name${UNIQUEID}.alaw,5,15)
exten => 2001,n,capicommand(chat_play|c1||/tmp/name${UNIQUEID}.alaw|1-4)
exten => 2001,n,capicommand(resource|1-4)
exten => 2001,n,capicommand(clamping|200)
exten => 2001,n,capicommand(vc|noisesuppressor|3|yes)    ; Voice command, key 3 - turn noise suppression on
exten => 2001,n,capicommand(vc|noisesuppressor|4|no)     ; Voice command, key 4 - turn noise suppression off
exten => 2001,n,capicommand(chat|c1|m|1-4)

exten => 2002,1,Answer
exten => 2002,n,Authenticate(21212)
exten => 2002,n,Playback(vm-rec-name)
exten => 2002,n,Record(/tmp/name${UNIQUEID}.alaw,5,15)
exten => 2002,n,capicommand(chat_play|c1||/tmp/name${UNIQUEID}.alaw|1-4)
exten => 2002,n,capicommand(resource|1-4)
exten => 2002,n,capicommand(clamping|200)
exten => 2002,n,capicommand(vc|chat_mute|1|yes)    ; Voice command, key 1 - change to half duplex mode
exten => 2002,n,capicommand(vc|chat_mute|2|no)     ; Voice command, key 2 - change to full duplex mode
exten => 2002,n,capicommand(vc|chat_command|0|a|c1)     ; Voice command, key 0 - disconnect all members
exten => 2002,n,capicommand(vc|noisesuppressor|3|yes)    ; Voice command, key 3 - turn noise suppression on
exten => 2002,n,capicommand(vc|noisesuppressor|4|no)     ; Voice command, key 4 - turn noise suppression off
exten => 2002,n,capicommand(chat|c1|mo|1-4)

Question form support: Asterisk Konferenzen / Timingdevice

vladimir.startsev@eicon.com — Thu, 16 Jul 2009 13:32:05 GMT

ein Kunde von Andreas fragt sich ob man ein Takt / Timingdevice für Konferenzen mit Diva Karten braucht, siehe Link unten:
http://www.das-asterisk-buch.de/2.1/konferenzraum-installation.html

(Customer ask about support for mentioned in the book timingdevive)

Download Chan_Dialogicdiva

falfaro — Fri, 15 May 2009 17:47:08 GMT

All of the software and drivers required to operate a Diva board with Asterisk can be downloaded as a single package from the Dialogic web site. Click here to download that package. The open source chan_dialogicdiva code that is compatible with the drivers is included in the package. It can be automatically installed along with the drivers.

Help for understanding and implementing the advanced features of Diva boards can are available in numerous locations on the Dialogic Website. A series of README files accompany chan_dialogicdiva that contain all the basic information needed to install and implent the Diva board. For more detailed information, a series of application notes for Dialogic® Diva® use with Asterisk are also available.

The open source chan_dialogicdiva code that is compatible with the drivers is included in the package

Chan_dialogicdiva allows to play messages to conferences

vladimir.startsev@eicon.com — Fri, 15 May 2009 16:07:37 GMT

Using 'chat_play' command this is possibe to play voice message to all members of conference while music on hold is played to caller

This feature is available for E.1/T.1/S0/PSTN and for IP conference members

Please read README.media for details

Update on chan_capi changes

vladimir.startsev@eicon.com — Fri, 15 May 2009 12:57:15 GMT

chan-capi-trunk 715

- fixed buffer length error with internal libcapi debug code.
- performance optimizations, use debug code when needed only.
- added commands for media features supported by Dialogic(R) Diva(R) Media Boards
- added variable CAPI_CIP for full access to all bearer capabilities.
- fixed CAPI 'chat' for using more than 8 controllers.
- fixed CAPI 'chat' for not exceeding maximal size of CAPI message
- add color fax
- add autodetection of fax file format for sendfax command (SFF, CFF JPEG, CFF T.43, TEXT)
- add extension for FAX paper formats and resolutions
- adjust NULL PLCI LI path
- add resource PLCI
- add echocancelpath configuration option
- fixed possible race condition while waiting for DISCONNECT_CONF
- add static half duplex conference
- add dynamic half duplex conference
- add clear channel fax
- add DTMF detection for NULL PLCI
- use direct access to vocoders without RTP framing
- play message to conference and music on hold to caller

Diva chan_capi allows use of clear channel fax over IP

vladimir.startsev@eicon.com — Sun, 03 May 2009 11:30:03 GMT

chan_capi 'sendfax' and 'receivefax' commands can be used to process clear channel fax over IP now.

This is achieved by use of Diva resource PLCI to attach DSP resources to connected by IP call and use Diva V.34 (33600Bps) Fax resources.

The 'resource' chan_capi command does not change the state of the call for connected by E.1/T.1/S0/PSTN calls. This allows to use same context
for processing all types of calls.

Please read details on 'receivefax' and 'sendfax' commands in README.Diva.fax and on 'resource' command in README.media

Example:

[handle_fax]
exten => s,1,capicommand(resource|1-4) ; Assign resource PLCI for IP, no action for E.1/T.1/S0/PSTN
exten => s,1,capicommand(receivefax|/tmp/${UNIQUEID}[|<stationid>|<headline>|<options>])
exten => s,2,Hangup()
exten => h,1,deadagi,fax.php ; Run sfftobmp and mail it

[handle_sendfax]
exten => s,1,capicommand(resource|1-4) ; Assign resource PLCI
exten => s,n,capicommand(sendfax|/tmp/sendfax001.sff|1234 1234 1234|Outgoing Fax)
exten => s,n,deadagi,faxlog.php ; Log result and schedule restart if necessary
exten => s,n,Hangup

Diva chan_capi provides managed conference

vladimir.startsev@eicon.com — Fri, 01 May 2009 14:36:34 GMT

Use 'chat_mute' to manage conferences

Diva chan_capi 'chat' command supports three types of conference members:
    Regular users
    Operators
    Listeners

Regular users can receive voise stream from conference and send voice stream to conference.
Outgoing (from user to conference) voice stream from regular users can be muted (deactivated)
and unmuted (activated) if necessary by 'chat_mute' command.

Operators can receive voise stream from conference and send voice stream to conference.
Outgoing (from user to conference) voice stream from operators can not be muted (deactivated)
by 'chat_mute' command.

Listeners can only receive voice stream from conference.
Outgoing (from user to conference) voice stream is muted (decativated) and can not be unmuted (activated)
by 'chat_mute' command.

'chat_mute' command allows to manage conference switching regular users between active (voice stream from
   user to conference is active and used in conference) and passive (voice stream from user to conference
   is deactivated and not used in conference) mode. 'chat_mute' command apply to regular users only.
   The state of operators and listeners is not changed by this commmand. Independent from changed by this
   command state of conference operators will remain active members and listeners will remain passive members
   of conference.

'chat_mute' command can be used by user which self is not a member of managed conference. Using
this feature one user can control multiple conferences. This allows to implement functionality of common
conference operator.

The 'chat_mute' command can be used for E.1/T.1/S0/PSTN and for IP conference members.

Please read more in README.media

Dialogic(R) Diva(R) SoftIP use cases

vladimir.startsev@eicon.com — Mon, 27 Apr 2009 09:47:40 GMT

How to use Dialogic(R) Diva(R) SoftIP for migration from ISDN/SS7/POTS environment to IP/SIP and to reuse available Dialogic(R) Diva(R) hardware in new IP environment

Use of Dialogic(R) Diva(R) softIP with chan_capi

vladimir.startsev@eicon.com — Mon, 20 Apr 2009 10:01:04 GMT

Use of Dialogic(R) Diva(R) softIP wit chan_capi allows to process T.38 V.34 fax connections and add additional features:

Accelaration by Diva hardware
- Clear channel V.34 fax
- Vocoders (G.729, G.723 32Kbit, GSM-FR, iLBC)
- Extended media processing
  - Noise suppression
  - Extended tone detection
  - Extended tone generation
  - AGC and digital gain control
Process IP calls in the same way as E.1/T.1/S0/PSTN calls
- Mapping between ISDN numbers and SIP addresses, REGISTRAR client support, outgoing proxy support
- SIP supplementary services are mapped to ISDN DSS1 supplementary services
Conferencing between originated by E.1/T.1/S0/PSTN and IP streams

Use of DSP resources for conferences with IP members

vladimir.startsev@eicon.com — Mon, 20 Apr 2009 08:43:23 GMT

The "chat" command allows to create conference with multeple rooms. This allows to create conference between E.1/T.1/S0/Analog and IP members in fully transparent to user way. "chat" command always detects the type of connection and uses appropriate resources.

The implementation of "chat" for IP endpoints uses Diva NULL PLCI. While this resource is available for every Diva hardware and allows to create high amount of IP endpoints running parallel to E.1/T.1/S0/Analog endpoints on the same Diva hardware it does not allows access to DSP resources for IP conference members.

This is the reason why new "resource" command is added to chan_capi. This command allows to assign DSP resource to IP conference member. This is no need fo user to check the type of connection and the type of Diva hardware is using this command. The "resource" command detects automatically the type of connection and type of hardware and perform requested actions only if necessary and possible.

The other more general way to use DSP resources for IP connections is to use Diva softIP. In this case IP traffic is processed by Diva protocol stack and presented as E.1/T.1 interface to chan_capi. This is not IP connection from the point of view of chan_capi and no additional commands are required.

Example (from README.media):

[isdn-in]
exten => _X.,1,Answer     ; Answer the line
exten => _X.,n,Goto(s,1)
exten => s,1,capicommand(resource|1-4)           ; Create DSP resource on CAPI controllers 1-4 for IP members, ignore command for E.1/T.1/S0/POTS members
exten => s,n,capicommand(clamping|100)         ; Activate suppression of DTMF tones
exten => s,n,capicommand(rxagc|yes)            ; Activate Rx AGC
exten => s,n,capicommand(noisesuppressor|yes)  ; Activate suppression of ambient noises
exten => s,n,capicommand(vc|incrxdgain|0|1.5)  ; Install voice command menu for volume control, '0' to increase volume
exten => s,n,capicommand(vc|incrxdgain|1|-1.5) ; Install voice command menu for volume control, '1' to decrease volume
exten => s,n,capicommand(vc|txdgain|2|-128) ; Install voice command menu for volume control, '2' to mute tx path
exten => s,n,capicommand(vc|txdgain|3|0) ; Install voice command menu for volume control, '3' to activate tx path
exten => s,n,capicommand(chat|test1|m|1-4)     ; Craete/enter conference toom 'test1', controller field is ignored if media processing resource is assigned by 'resource' command or for E.1/T.1/S0/POTS members

Supported hardware (from README.media):

Supported hardware:
  Assign DSP resources to connected by IP network conference member. This feature is available
  for equipped with DSP Diva hardware only.

  For Diva 2PRI PCI, Diva 4PRI PCI, Diva 1PRI PCIe HS, Diva 2PRI PCIe HS and Diva 4PRI PCIe HS no
  restrictions apply for this feature and this is possible to access N x 30 DSP resources
  (N - amount of interfaces, 1 - 1PRI, 2 - 2PRI, 4 - 4PRI) in addition to used for E.1/T.1
  DSP resources.

  For Diva PRI Rev.3 PCI and Diva PRI Rev.3 PCIe this is possible to reserve two DSPs for processing
  of E.1/T.1 without media processing features and share remainding DSPs between E.1/T.1 and IP
  for connections with media processing features.
  Using hardware with 30 DSPs and E.1 this is possible to create:
    From:  2 x E.1 without media processing + 28 x E.1 with media processing
    To:   30 x E.1 without media processing + 28 x IP with media processing
  Using hardware with 30 DSPs and T.1 this is possible to create:
    From: 23 x T.1 with media processing    +  7 x IP with media processing
    To:   23 x T.1 without media processing + 28 x IP with media processing

  For Diva BRI-2M Rev.2 PCI, Diva BRI-2M PCIe, Diva 4BRI Rev.2 PCI and for Diva 4BRI PCIe
  this is not possible to reserve DSPs for processing of ISDN connections and to share
  DSPs between ISDN and IP connection. In case DSP resources are assigned to connected
  by IP conference member then appropriate DSP resources receive not available
  for processing of ISDN connections. As result ISDN connections can not be processed.
  To resolve this problem please use Diva configuration to change the configuration
  of Diva board to resourceboardmode. In resourceboard mode ISDN interface is deactivated
  and all available DSP resources (two DSPs for Diva BRI-2M and eight DSPs for Diva 4BRI)
  can be used for connected by IP conference members (two members for Diva BRI-2M and
  eight members for Diva 4BRI).

T.38 and Clear Channel fax support by chan_capi

vladimir.startsev@eicon.com — Fri, 03 Apr 2009 12:48:40 GMT

chan_capi supports both FoIP (Fax over IP) standards: T.38 and Clear Channel fax with V.34, ECM, intelligen fax processing, on demand change between voice and fax. All provided by Diva hardware in TDM (E.1/T.1/S0) environment fax features are available for T.38 and Clear Channel Fax.

In case chan_capi is used to terminate or initiate the fax transmission all necessary features are provided by Diva softIP. softIP exposes one CAPI interface towards
chan_capi and SIP interface towards IP network.
This is no need to change chan_capi configuration. This is only necessary to specify softIP as CAPI controller. All other configuration details are handled by Diva softIP configuration.

Diva softIP allows to preserve all voice features. This is possible to process voice calls over IP and switch between voise and fax media. Diva softIP can be used
in one system with Diva hardware and supports line interconnect (conferencing) between processed by Diva hardware and by softIP voice streams.

In case softIP is used with one or more Diva boards in resource board mode then V.34 Clear Channel Fax and G.729, iLBC, G.726, G.723, GSM and other vocoders receive available for chan_capi.

softIp can be used in virtualized environment (VMWare, XEN, ...)

CHAN_CAPI README.Diva.fax

vladimir.startsev@eicon.com — Fri, 03 Apr 2009 12:35:46 GMT

Contained in the CHAN_CAPI description of Diva fax features:

Fax features
- Intelligent fax processing
  - ECM
  - Fax compression
- V.34
- FoIP/VoIP T.38 and Clear Channel fax
- FoIP using chan_capi
Fax reception
Fax transmissions

CHAN_CAPI README.media

vladimir.startsev@eicon.com — Fri, 03 Apr 2009 12:30:22 GMT

Contained in chan_capi description of media features

Media control
- Volume control
- AGC
- Pitch control
Tone detection
Tone generation
Human talker detection
Conferencing
- E.1/T.1/S0/Analog to E.1/T.1/S0/Analog
- E.1/T.1/S0/Analog to IP SIP/IAX
- IP SIP/IAX to IP SIP/IAX
- Use DSP resources for IP media processing
  - Clear channel fax with V.34 (33600 Bps)
  - IP media processing and conferencing
- Managed conference with tree types of members
  - Regular member
  - Operator
  - Listener
Interactive media control

Dial Plan: Conference with multiple rooms and media control

vladimir.startsev@eicon.com — Wed, 01 Apr 2009 22:39:25 GMT

[isdn-in]
exten => _X.,1,Answer ; Answer the line
exten => _X.,n,Goto(s,1)
exten => s,1,Set(TIMEOUT(digit)=5) ; Set Digit Timeout to 5 seconds
exten => s,n,Set(TIMEOUT(response)=10) ; Set Response Timeout to 10 seconds
exten => s,n(restart),BackGround(demo-instruct) ; Play some instructions
exten => s,n,WaitExten ; Wait for an extension to be dialed, use to select conference room

New Diva DEMO system online

vladimir.startsev@eicon.com — Thu, 26 Mar 2009 13:24:22 GMT

New Diva DEMO system is online and allows to take a look on the changes in the future version

chan_capi configuration
New sipControl features
SS7 integration

Please use link: Dialogic® Diva® Configuration live demo system