Add description for resource command

README.media

@@ -898,6 +898,100 @@ exten => i,n,Goto(s,restart)
 exten => h,1,Hangup
 /////////////////////////////////////////////////////////////////////
 
++-------------------------------------------------------------------+
+| IP chat (MeetMe/Conference) with access to DSP resources          |
++-------------------------------------------------------------------+
+
+Description:
+  Used to assign DSP resources to connected by IP conference member.
+  If conference member is connected by IP network using 'chat' chan_capi command
+  then this peer can not allocate and use required for media processing DSP resources.
+  This results in processing of IP partipiants as simple conferencing member without
+  any media processing capabilities except line interconnect (conferencing) and
+  conferencing AGC (active talker evaluation).
+  Using 'resource' chan_capi command this is possible to assign DSP resources to
+  by IP network connection before proceeding with 'chat' chan_capi command. This
+  allows use of provided by DSP resources media processing for connected by IP
+  network conference members.
+
+Note:
+  Certain problems arrive if processing send in band DTMF events for
+  IP connections.
+  chan_diva can use sent in band DTMF events to control media
+  processing (chan_capi 'vc' command). This works without problems for
+  E.1/T.1/S0/Analog connections. But in case of IP connections media
+  stream is processed by gateway or is originated by IP device.
+  Most of gateways will remove in band DTMF events from media stream and
+  forward detected DTMF events as RTP payloads. IP devices will not use
+  in band DTMF signaling and send DTMF events as RTP payloads.
+  In both cases DTMF events are not sent in band and processed by signaling
+  before reaching the chan_capi.
+  The solution is to configure gateways and IP devices to send DTMF events
+  in band in addition to sending as RTP payloads or use in band MF signaling.
+
+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).
+  
+
+Syntax:
+capicommand(ressource|controller)
+  controller - CAPI controller
+
+
+Syntax example:
+exten => s,n,capicommand(resource|1)
+exten => s,n,capicommand(resource|1,3)
+exten => s,n,capicommand(resource|1-4)
+exten => s,n,capicommand(resource|1-4,7)
+exten => s,n,capicommand(resource|1-4,7-10)
+
+IVR example:
+/////////////////////////////////////////////////////////////////////
+[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
+
+/////////////////////////////////////////////////////////////////////
+
 +-------------------------------------------------------------------+
 |  echocancel                                                       |
 +-------------------------------------------------------------------+