DSP-2 Card Features

T.30 Fax Suite

In this release, Excel is introducing a suite of intelligent fax capabilities to its DSP Series 2 card. These capabilities are compliant with the ITU T.30 fax protocol, recognized worldwide. Application developers will be able to use the Excel T.30 Fax suite to develop applications that transmit and receive Group 3 facsimiles concurrently on all channels, at rates up to 14,400 bps.

The Excel T.30 Fax suite supports enhanced Group 3 fax features such as 1D, 2D, and MMR encoding, Error Correcting Mode (ECM), normal, fine, and very fine resolutions, and the standard page width formats. The Excel T.30 Fax suite can convert documents into different formats, resolutions, or encodings online (on-the-fly) or offline. For more information about the Group 3 fax standard, see ITU T30 Fax standard.

The Excel T.30 Fax suite functionality resides on the DSP Series 2 card’s existing DSP chips and shares the chips with existing DSP functions, including DTMF, Conferencing, Call Progress Analysis (CPA), voice recording, and playing of announcements. The DSP Series 2 card uses the ITU T.30 fax communication protocol exclusively.

The T.30 Fax suit supports 12 simultaneous faxes per DSP chip
(6 per stream).

This feature is explained in the in the Developer’s Guide: Overview, DSP Resources chapter, in the section T.30 Fax on the DSP Series 2.

This release does not support T.30 Polling Mode.

Requirements

• One DSP Series 2 card

• One DSP Series 2 I/O card

• One DSP Series 2 License

• 12 Resource Points per fax session

• Network File System (NFS)

You do not need a hardware upgrade for this feature, only a software upgrade.

Supported Fax Standards

• V.21 (300 bps) for T.30 fax negotiation

• V.27ter (2,400 / 4,800 bps, required by Group 3)

• V.29 (9,600, 7,200 bps)

• V.17 (14.4, 12, 9.6, 7.2 kbps) transmit/receive

Supported Image Format Conversion

• Image formats conversion, either off-line or while the fax is being sent or received, for MH, MR, (ITUT.4), and MMR (ITUT.6)

• Document files must be in TIFF-F or TIFF-S Format

Supported Resolutions

• Standard

• Fine

• Super-fine

T.38 Support on the IP Network Interface Series 2 Card

The Excel T.30 Fax suite can also be used to produce fax server products for IP telephony gateways when used with the T.38-supporting IP Network Interface Series 2 card. The DSP Series 2 card does not itself support or terminate T.38.

New API Messages

Resource Disconnect (0x0128)

Resource Query (0x012C)

Modified API Messages

DSP SIMM Configure (0x00C0)

This message has had a new function type added:

0x32 Send/Receive Fax

Generic Card Configure (0x0122)

This message has had the following new mandatory TLV added:

0x05FA Object type (Card, 0x0004)

The Generic Card Configure message has also had the following new optional TLVs added:

0x0641 Header Parameter Format

0x0642 T.30 Control Parameter Max Value

0x0643 T.30 Control Parameter Transmit Level

0x0644 T.30 Control Parameter ECM Enabled

0x0645 T.30 Control Parameter Local Session ID

0x0647 Receive Modem Type

0x0648 Receive Resolution Type

0x0649 Receive Encoding Type

0x064B Receive Bad Line

0x064C Receive Page Size

0x0651 Receive Enable ECM

0x0652 Receive Add Header

0x0654 Receive line error threshold

0x0655 Receive Timeout

0x0657 Receive Terminal ID

0x065A Transmit Modem Type

0x065B Transmit Resolution Type

0x065C Transmit Page Size

0x0661 Transmit Enable ECM

0x0662 Transmit Add Header

0x0664 Transmit Enable CNG

0x0666 Transmit Timeout

0x0668 Transmit dbm Level

0x066A Transmit Terminal ID

0x066C Fax Processing Events Set Register

Generic Card Query (0x0123)

This message has had a new mandatory TLV added:

0x05FA Object Type (Card Object, 0x0004)

Along with the Object Type TLV (0x05FA), you must use either the Fax Configuration Query Type TLV (0x066D) or one of the fax configuration parameter TLVs (0x0641-066C).

Return TLVs

For Fax Configure Query Type 0x0001: Tags 0x0642-0x0644

For Fax Configure Query Type 0x0002: Tags 0x0647-0x0655

For Fax Configure Query Type0x0004: Tags 0x065A-0x0668

Note: If any of the configuration parameter TLVs (0x641-0x066C) are sent in the query, the response returns the TLV with the configured value.

Resource Connect (0x0127)

This message has had new mandatory TLVs added for when the Resource Type is Send Fax or Receive Fax:

0x05E0 File ID

0x05E2 File Location

0x0602 Resource Type

The Resource Connect message has also had new optional TLVs for when Resource type is Send Fax or Receive Fax:

0x0641 Header Parameter Format

0x0642 T.30 Control Parameter Max Value

0x0643 T.30 Control Parameter Transmit Level

0x0644 T.30 Control Parameter ECM Enabled

0x0645 T.30 Control Parameter Local Session ID

0x0651 Receive Enable ECM

0x0652 Receive Add Header

0x0655 Receive Timeout

0x0657 Receive Terminal ID

0x065B Transmit Resolution Type

0x065C Transmit Page Size

0x0661 Transmit Enable ECM

0x0662 Transmit Add Header

0x0664 Transmit Enable CNG

0x0668 Transmit dbm Level

0x066A Transmit Terminal ID

Mandatory TLV in the Response:

0x0602 Resource Type

Call Processing Event (0x002E)

This message has had a new Call Processing Event type added: 0x41 (DSP2 fax processing events)

Data[0,1]: Fax processing event code

Data[2,n]: Fax processing event data

Conference in a Conference

You can now create a private sub-conference (child conference) within a larger conference (parent conference). When a smaller group of participants within a larger conference want to talk privately, they can do so while still hearing the audio from the larger conference. The sub-conference parties participate with one another in full duplex, while becoming listen-only parties in the larger conference.

The Conference in a Conference feature is available on the DSP Series 2 card only. It is not available on either the DSP-ONE or MFDSP card.

The feature allows users to create a child conference, move parties from the parent conference to the child conference and back, and delete the child conference.

A child conference consumes no resource points that weren't already being consumed by the parent conference. If you add a leg to the child conference, the extra leg consumes one leg's worth of additional resource points, just as it would if you added a leg to a parent conference.

This feature is explained in the Developer’s Guide: Overview, DSP Resources chapter, in the section, Conference in a Conference on the DSP Series 2.

Dependencies and Considerations

• Child conferences can be created for Unified Conferences only.

• Only parties that are already connected to the parent conference can be connected to the child conference.

• If a party is removed from the parent conference, it will also be removed from any child conference it is participating in.

• A party can be in only one child conference at a time.

• Only parties that are connected 2-way in a parent conference can be moved into a child conference.

• When a child conference is deleted forcibly, the channels connected to it are connected back to the parent conference and the child conference is immediately deleted.

• When a child conference is deleted gracefully, the Excel platform waits until all the parties connected to the child conference are either removed or reconnected to the parent conference before deleting the child conference. The default behavior is graceful deletion.

• When a parent conference is deleted forcibly, all parties connected to the parent and the associated child conferences are removed, and the parent and all its child conferences are immediately deleted.

• When a parent conference is deleted gracefully, the Excel platform waits until all parties in the parent and the associated child conferences are removed. When all parties connected to a child conference have been removed or reconnected to the parent conference, the child conference is deleted. When all the child conferences have been deleted and no parties are left in the parent conference, the parent conference is deleted.

• A child conference inherits its advanced conferencing features from the parent conference at the time the child conference is created. Setting or modifying Advanced Conferencing parameters for a child conference is supported initially.

• Play/Record Files into child conferences is not supported initially.

Simultaneously Playing Multiple Files into a Conference on the DSP Series 2 Card

You can now simultaneously play multiple files into a conference. The same File ID can be played multiple times. Any subsequent action on the playing file (such as Modify or Stop) identifies the file using a combination of the Conference ID and the Play File ID. Therefore, if you modify or stop a File ID, you cause the change to happen to all instances of that File ID being played in the specified conference. File queues are not permitted when playing multiple files into a conference. Multiple file plays are not permitted when queued files are being played.

When playing multiple files into a conference simultaneously, standard Play File resource points are used for each Play File.

API Changes

Play File Modify

• The Conference ID AIB has been added

• The optional File ID TLV has been added

The following text has been added to the desciption of the Play File Modify message:

When modifying a file that is playing to a conference, use the Conference AIB instead of the Channel AIB. If you are modifying a file that is playing to a conference, use the optional File ID TLV. If you use the File ID TLV, all instances of that File ID being played in the specified conference are modified. If the File ID TLV is absent, all the files playing into that conference are modified.

Play File Stop

• The Conference ID AIB has been added

• The optional File ID TLV has been added

• The following text has been added to the desciption of the Play File Stop message:

When stopping a file that is playing to a conference, use the
Conference AIB instead of the Channel AIB. If you are stopping a
file that is playing to a conference, use the File ID TLV. If you use
the File ID TLV, all instances of that File ID being played in the
specified conference are stopped. If the File ID TLV is absent, all
the files playing into that conference are stopped.