3.1.25  
CLIP for Analog Stations 
 

Definition  
The "analog CLIP" feature enables the calling number to be displayed on the telephone of the analog extension called. Analog CLIP is supported for all analog telephones that are connected via an analog subscriber line module. Analog CLIP is not supported for analog telephones that are connected via the slave port of an OpenStage phone adapter. The following versions of the "analog CLIP" feature exist:
 •   analog CLIP (from HiPath 3000/5000 V6.0): This feature functions for internal calls and for calls that arrive via ISDN connections.
 •   analog trunk CLIP (from HiPath 3000/5000 V7 or later): This feature functions for calls that arrive via analog trunks. Phone number information is transferred to UP0/E and IP telephones as well as analog telephones.
The name of the calling party (Calling Name Identification Presentation, CNIP) can also be presented and administered.
CNIP is station-dependent.
(Gigaset S100 Professional is supported; Euroset 2020 is not!).  
Vendor information relating to analog telephones MUST be observed.  
Special characters cannot be transmitted. Only seven-bit ASCII characters are supported.  
Analog telephones equipped with VMWI (Visual Message Waiting Indication) show that a callback was activated for that telephone.

Extension of the first call pause using Calling Line Identification Presentation (CLIP)  
When using the "analog CLIP" feature together with a protocol that transfers the CLIP information between the first and second call, the first call pause may be extended compared with the value configured in Manager E. CLIP information transfer takes approx. 3.5 sec. If a shorter value is configured for the call pause in Manager E (e.g. 2 seconds), only the first call pause is extended. Subsequent pauses correspond to the configured values. If the "analog CLIP" feature is deactivated, signaling is performed in accordance with the Manager E settings. This is governed by the CLIP protocol.

Protocol versions supported  

Protocol version  
Description  
ETSI FSK type 1  
FSK data transmission between the first and second ring pattern. The most widespread protocol for transmitting call numbers and names.  
Countries: DE, AT, CH and many more.  
Reference: ETSI EN 300 659-1, chapter 6.1.1  
ETSI FSK type 2  
FSK data transmission before the first ring, start sequence with special ring.  
Countries: FR  
Reference: ETSI EN 300 659-1, chapter 6.1.2 b  
ETSI FSK type 3  
FSK data transmission before the first ring, start sequence with special ring.  
Countries: FR  
Reference: ETSI EN 300 659-1, chapter 6.1.2  
ETSI DTMF type 1  
DTMF data transmission between the first and second ring. Start/stop signal "DC".  
Countries: FI  
Reference: ETSI EN 300 659-1, chapter 6.1.1 and annex B  
Denmark DTMF  
DTMF data transmission before the first ring, start sequence with DTMF tone.  
Countries: DK  
Reference: TS 900-301-1E2  
Bellcore MDMF  
FSK data transmission between the first and second ring. This (multidata) protocol can transmit call numbers and names.  
Countries: USA, CAN, HGK.  
Reference: TIA/EIA-777A  
Bellcore SDMF  
FSK data transmission between the first and second ring. This (single data) protocol only transmits call numbers.  
Countries: USA, CAN, HGK.  
Reference: TIA/EIA-777A  
Brazil DTMF  
DTMF data transmission before the first ring, start sequence with DTMF tone and selection code.  
Countries: BR  
Reference: NET Nš 001/92  
Only on-hook signaling is available for all protocol variants listed.

Supported Features  

Protocol  
Type  
Information elements  
 Supports  
Bellcore SDMF  
FSK (USA)  
 •   Date and time of call
 •   Caller identity
 •   Reason directory number is not present
 X  
 X  
 X  
Bellcore MDMF  
FSK (USA)  
 •   Date and time
 •   Caller number
 •   Dialable directory number
 •   Reason directory number is not present
 •   Reason for forwarding (reserved)
 •   Call qualifier
 •   Caller name
 •   Reason caller name is not present
 •   Visual Message Waiting Indication
 X  
 X  
 X  
 X  
 0  
 0  
 X  
 X  
 X  
ETSI SDMF  
DTMF  
 •   Caller identity
 •   Call forwarding number
 •   Connection: number is not available (corresponds to "Reason number is not present")
 •   Connection: private number (corresponds to "Reason number is not present")
 X  
 0  
 X
 
 X  
ETSI MDMF  
FSK  
 •   Date and time
 •   Caller identity
or Reason caller identity is not present
 •   Identity of called party
 •   Caller name
or Reason caller name is not present
 •   Complementary/Additional caller identity
 •   Call type
 •   Identity of first caller (if forwarded)
 •   Type of forwarded call (if forwarded)
 •   Caller type
 •   Forwarded number (if forwarded)
 •   Identity of network provider
 •   Telephone function selection
 •   Information on the display
 •   Expansion for the user provided by the network operator
 •   Call charges
 •   Additional charges
 •   Parameters for network operators
 X  
 X
X  
 X  
 X  
 X  
 0  
 0  
 0  
 0  
 0  
 0  
 0  
 0  
 0  
 0
 
 0  
 0  
 0  
X  
Supported by protocol/HiPath 3000  
0  
Supported by protocol, not supported by HiPath 3000  
--  
Not supported by protocol  
If date and time information is included in the log, the clock generator and calendar can be updated automatically in the same was as ISDN lines, see Section 9.2 "Date and Time Display".

Model-Specific Data  

 Subject  
 HiPath 3800  
 HiPath 3550  
 HiPath 3500  
 HiPath 3350  
 HiPath 3300  
Feature available in  
 x  
 x  
 x  
Hardware requirements1  
  SLMA  
 SLMA8  
 SLMAE  
 SLMAE8  
 TMANI8  
 HiPath 3550, HiPath 3350:
CBCC (S30810-Q2935-A301)  
 HiPath 3500 HiPath 3300:
CBRC (S30810-Q2935-Z301)  
 SLAD4  
 SLAD8  
 SLAD8R  
 TLANI2  
 TLANI4  
 TLANI8  
 TLANI4R  
Software requirements  
 as of V7  
 as of V7  
1If a board is not listed here, it does not support the "CLIP for Analog Stations" feature.

HiPath 3000/5000 V9, Feature Description, Issue 7   up Top
Disclaimer & Copyright   ID: P31003H3590F100017618   2012-06-25