HiPath 8000 Version 2.
*1PA31003-H8022-F100-2-7618* 1P A31003-H8022-F100-2-7618 The information provided in this document contains merely general descriptions or characteristics of performance which in case of actual use do not always apply as described or which may change as a result of further development of the products. An obligation to provide the respective characteristics shall only exist if expressly agreed in the terms of contract. The trademarks used are owned by Siemens Enterprise Communications GmbH & Co.
5848his.fm History of Changes History of Changes 0 Version Number Date 1 September 2006 Initial release 2 October 2006 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.2, Feature Description Guide Summary Second publication of document. Addition of information for Genesys call center and Agent Console application, and for HiPath ProCenter integration. Miscellaneous corrections.
5848his.fm History of Changes 0-2 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
848TOC.fm Contents Contents 0 1 Important Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.1 About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.2 Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 2 SIP Endpoint User Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5848TOC.fm Contents 5.2 Automatic Callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 5.3 Automatic Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 5.4 Caller Identity Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 5.5 Calling Identity Delivery and Suppression. . . . . . . . . . . . . . . . . . . . . . . . .
5848TOC.fm Contents 6.16 Multiple Language Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12 6.17 Station Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12 6.18 Voice VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14 7 Other Group Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5848TOC.fm Contents 11.4 PRI—Supported and Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 11.5 PRI Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 12 QSIG Tunneling Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5848TOC.fm Contents 15.8 Feature Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.9 Log File Retrieval Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.10 Maintenance Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.11 On-Demand Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.
5848TOC.fm Contents 18.4 Data Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2 18.5 Internal Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2 18.6 Interworking with Automated Attendant Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3 18.7 Local Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
notices.fm Important Notices About This Book 1 Important Notices 1.1 About This Book 1.1.1 Audience This book is intended for those who would like a better understanding of the HiPath 8000 features, including Siemens customers, systems engineers (SEs), and sales representatives. 1.1.2 Prerequisite Knowledge You should be familiar with basic telecommunications equipment functionality and terminology. 1.1.
notices.fm Important Notices About This Book ● Chapter 3, “Keyset Telephone User Features” describes features specific to keyset operations. The keyset operations features provide multiple line capability, and other associated functions, for a SIP endpoint configured as a keyset. Keysets are sometimes known as multiline telephones. ● Chapter 4, “HiPath 8000-Based Station Call Forwarding User Features” describes the station call forwarding features that reside in the HiPath 8000.
notices.fm Important Notices About This Book ● Chapter 15, “Serviceability Features” describes the HiPath 8000 features that improve serviceability, such as diagnostics and debug tools, code controls, and administrator controls. ● Chapter 16, “SIP Signaling Features” describes the HiPath 8000 features that support SIP signaling and the interworking with other elements such as application servers, voice conferencing applications, and voice mail systems.
notices.
notices.fm Important Notices Documentation Feedback ● optiPoint 410/420 Advance S, V6.0, User Manual ● optiPoint WL 2 Professional S, Administration Manual ● optiPoint WL 2 Professional S, Operating Manual 1.1.6 Special Notices If applicable, potentially dangerous situations are noted throughout this guide. The three alert methods are defined below: DANGER A danger notice calls attention to conditions that, if not avoided, will result in death or serious injury.
notices.fm Important Notices Documentation Feedback 1.2.2 Countries Other than U.S. Please provide feedback on this document as follows: ● Submit a trouble ticket to ICTS. - or- ● 1-6 Use the Document Feedback form that you can access from the front page of the HTML version of this document. A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
sip_endpoint_user_features.fm SIP Endpoint User Features 2 SIP Endpoint User Features This chapter provides an overview of local user features that reside in the following Siemens SIP endpoints: ● optiPoint 410 S and optiPoint 420 S ● optiClient 130 S ● optiPoint WL 2 Professional S ● optiPoint 150 S Other SIP telephones used with the HiPath 8000 function differently. Refer to the device’s documentation for more information.
sip_endpoint_user_features.fm SIP Endpoint User Features Endpoint Types Overview 2.1 Endpoint Types Overview 2.1.1 optiPoint 410 S and optiPoint 420 S The optiPoint 410 S and optiPoint 420 S telephones are modern multifunction SIP telephones. The following are brief descriptions of each: ● The optiPoint 410 S supports 19 function keys, 18 of which are programmable. It provides support for adapters and modules, including the self-labeling key module. Because it is fully compliant with the IEEE 802.
sip_endpoint_user_features.fm SIP Endpoint User Features Endpoint Features Summary 2.2 Endpoint Features Summary Table 2-1 lists the local user features; it also indicates the Siemens SIP endpoints that support each. Feature Abbreviated dialing • optiPoint WL 2 Professional S Table 2-1includes the keyset operations features described in Chapter 3, “Keyset Telephone User Features”. Depending on the endpoint, some of these features are endpoint-based, HiPath 8000-based, or a combination of the two.
sip_endpoint_user_features.fm optiPoint WL 2 Professional S Call forwarding return— endpoint-based optiPoint 150 S Feature optiClient 130 S optiPoint 410/420 S SIP Endpoint User Features Endpoint Features Summary Comments • • See also consultation hold.
sip_endpoint_user_features.fm Directory list optiPoint WL 2 Professional S optiPoint 150 S Feature optiClient 130 S optiPoint 410/420 S SIP Endpoint User Features Endpoint Features Summary Comments • Do not disturb • Do-not-interrupt dialing • Drop call key • • • DTMF tone dialing • Dynamic WBM addressing • • • • Easy answer See also Stop/Escape key.
sip_endpoint_user_features.fm • • Join • Keypad lock Keyset operation support • The optiPoint WL 2 Professional S supports adaptive jitter buffer control. • See call join. • • See also Section 3.4, “Keyset Operation Modes”, on page 3-5. For optiPoint 410/ 420 S keyset telephones, this feature is HiPath 8000-based. • See Chapter 3, “Keyset Telephone User Features”.
sip_endpoint_user_features.fm • • See also Section 3.9, “Multiline Appearance”, on page 3-11. For optiPoint 410/420 S keyset telephones, this feature requires configuration in the endpoint and in the HiPath 8000. Multiline origination and transfer • • See also Section 3.10, “Multiline Origination and Transfer”, on page 3-13. Multiline preference • • See also Section 3.11, “Multiline Preference”, on page 3-14.
sip_endpoint_user_features.fm Registration by name or number • • • • See also call log. See also ringer tones. • • Repertory dialing • • • Ring tone, variable • • • • Ringer cutoff • • • • • See also ring tone, variable. • • See also call waiting (camp-on).
sip_endpoint_user_features.fm Feature optiPoint 410/420 S optiClient 130 S optiPoint 150 S optiPoint WL 2 Professional S SIP Endpoint User Features Endpoint Features Summary Transfer, blind • • • • See also Section 5.28, “Transfer”, on page 5-32. Transfer, unscreened • • • • See also Section 5.28, “Transfer”, on page 5-32. Transfer, with third-party consultation • • • • See also Section 5.28, “Transfer”, on page 5-32.
sip_endpoint_user_features.fm SIP Endpoint User Features Endpoint Features Summary 2-10 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
keyset_telephone_user_features.fm Keyset Telephone User Features 3 Keyset Telephone User Features This chapter describes features specific to keyset operations. A keyset telephone is configured with a primary line (also known as a prime line), which is the main DN of a keyset telephone associated with the device. A keyset telephone can also have additional secondary and phantom line appearances, both of which are defined in this chapter.
keyset_telephone_user_features.fm Keyset Telephone User Features Audible Ringing on Rollover Lines 3.1 Audible Ringing on Rollover Lines 3.1.1 Definition The audible ringing on rollover lines feature permits lines to audibly signal new incoming calls while the user is active on the keyset. This feature is also known as rollover ringing. 3.1.2 Functional Operation > For the optiClient 130 S, rollover ringing is configured in the endpoint. Refer to the optiClient 130 S, V4.
keyset_telephone_user_features.fm Keyset Telephone User Features Delayed Ringing 3.1.3 Guidelines for Implementation and Use optiPoint 410/420 S keyset telephone: If the loudspeaker is in use: ● – Alert ring reverts to alert beep. If the user is in open listening mode, the beep is applied through the handset; otherwise the beep is applied through the loudspeaker. – Standard ring reverts to no ring. Rollover ring is not applied: ● – For lines that are set for alerting only.
keyset_telephone_user_features.fm Keyset Telephone User Features Direct Station Select Key optiPoint 410/420 S keyset telephones: Assigns the Immediate Ring feature key to the device. ● When a call is presented to a line provisioned for delayed ringing, the associated line key LED flashes to indicate that the call is present. Upon timeout of the delay ring timer, the device begins to audibly alert (ring), and the associated incoming call display is presented.
keyset_telephone_user_features.fm Keyset Telephone User Features Keyset Operation Modes > The DSS LED reflects the status of the line (DN) programmed for the DSS key, not the status of the user associated with the prime DN device. The user presses the DSS key to call the party associated with the key. A blinking DSS key indicates an incoming call for another user with the same DSS key appearance.
keyset_telephone_user_features.fm Keyset Telephone User Features Keyset Operation Modes 3.4.2 > Functional Operation For the optiClient 130 S, keyset operation modes are configured in the endpoint. Refer to the optiClient 130 S, V4.0, Administrator Documentation and Operating Instructions for more information.
keyset_telephone_user_features.fm Keyset Telephone User Features Keyset Operation Modes ● HiPath 8000-based station speed calling: Refer to Section 5.25, “Station Speed Calling—HiPath 8000-Based”, on page 5-29. The following HiPath 8000 features use the primary line's configured data if the telephone is configured for device-based operation: ● Calling party name and number upon alerting or answer: Refer to Section 5.4, “Caller Identity Service”, on page 5-4.
keyset_telephone_user_features.fm Keyset Telephone User Features Line Focus Call transfer if provisioned on the line that originates the operation: Refer to Section 5.28, “Transfer”, on page 5-32. ● 3.4.3 CDR When a keyset user initiates a call from a line configured for line-based operation, the HiPath 8000 records the line used and the device from where the call was initiated. 3.
keyset_telephone_user_features.fm Keyset Telephone User Features Line Reservation The optiPoint 410/420 S keyset telephones also support a configurable option to either place the call on manual hold or to release it when the user is active on one line and selects the same line or a different line. This feature is controlled via the endpoint. 3.6.
keyset_telephone_user_features.fm Keyset Telephone User Features Manual Hold 3.7.2 Functional Operation The keyset telephone automatically reserves a line whenever the user is being prompted for a destination address and hears dial tone. The line key LED indicates this reserved state. One line can be reserved at a time on a given keyset. The keyset cancels the reservation after a preconfigured period determined by the reservation timer.
keyset_telephone_user_features.fm Keyset Telephone User Features Multiline Appearance ● The user can hang up and originate or answer a call on another line on that keyset. ● Any user with that line appearance can press the line key and retrieve the held call. ● A hold ringback timer is started. If the timer expires, the held call is presented as an alerting call to all keysets sharing that line. Each line has its own configurable timer.
keyset_telephone_user_features.fm Keyset Telephone User Features Multiline Appearance 3.9.2 > Functional Operation For the optiClient 130 S, multiline appearance is configured in the endpoint. Refer to the optiClient 130 S, V4.0, Administrator Documentation and Operating Instructions for more information.
keyset_telephone_user_features.fm Keyset Telephone User Features Multiline Origination and Transfer 3.10 Multiline Origination and Transfer 3.10.1 Definition The multiline origination and transfer feature provides the capability to: ● Originate or answer calls at any line appearance at any keyset ● Transfer calls via consultation transfer ● Transfer calls via manual hold This feature is controlled via the endpoint. 3.10.
keyset_telephone_user_features.fm Keyset Telephone User Features Multiline Preference 3.11 Multiline Preference 3.11.1 Definition The multiline preference feature: ● Allows a keyset to automatically select which line it uses when the user originates or answers a call. ● Lets a user override the automatic selection of a line and manually select the line to use. This feature is controlled via the endpoint. 3.11.
keyset_telephone_user_features.fm Keyset Telephone User Features Phantom Lines Automatic line selection occurs whenever an outgoing call commences and a line has not been pre-selected. Automatic line selection also occurs when a line needs to be reserved for dialling and a line as not been pre-selected— for example, when entering a digit via the keypad while on-hook and idle. Ringing line preference is the default. 3.11.
keyset_telephone_user_features.fm Keyset Telephone User Features Preview 3.13 Preview 3.13.1 Definition The preview feature permits a keyset user to view display information associated with certain lines without answering the call or retrieving it from hold. This feature is useful to anyone who handles a number of simultaneous calls because it provides the ability to make an intelligent choice of which calls to answer first and to identify high-priority callers.
keyset_telephone_user_features.fm Keyset Telephone User Features Visual Indicators for Line and Feature Key Status – Go onhook or offhook as appropriate. – Answer a ringing call. 3.14 Visual Indicators for Line and Feature Key Status 3.14.
keyset_telephone_user_features.fm Keyset Telephone User Features Visual Indicators for Line and Feature Key Status Line Status Line Type LED State Flash Rate Comments Idle Off n/a Flutter -orOn 50 ms on, 50 ms off This LED state is applicable to the line with the focus (refer to Section 3.5, “Line Focus”, on page 3-8. Secondary On n/a This indication is given on other appearances of the active line.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features 4 HiPath 8000-Based Station Call Forwarding User Features This chapter describes the station call forwarding features that reside in the HiPath 8000. These features are accessible via feature access code; the user can also assign a frequently-used feature to a feature key or repdial key. Siemens SIP endpoints also have local call forwarding features.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—All Calls 4.1 > Call Forwarding, Station—All Calls Siemens SIP endpoints also provide the capability to locally configure and control unconditional call forwarding. However: ● It is strongly recommended that the endpoint-based call forwarding features not be used simultaneously with other station call forwarding features that reside in the HiPath 8000.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—All Calls 4.1.2 Functional Operation The subscriber activates the station call forwarding—all calls feature as follows: 1. The subscriber goes off-hook, receives a dial tone, and enters *72. The subscriber hears a recall dial tone. 2. The subscriber dials the DN of the remote station to which calls are to be forwarded.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Busy Line 4.2 > Call Forwarding, Station—Busy Line Siemens SIP endpoints also provide the capability to locally configure and control call forwarding on busy. However: ● It is strongly recommended that the endpoint-based call forwarding features not be used simultaneously with other station call forwarding features that reside in the HiPath 8000.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Courtesy Call 4.2.2 Functional Operation The subscriber activates the station CFBL feature as follows: 1. The subscriber goes off-hook, receives a dial tone, and enters *90. The subscriber hears a recall dial tone. 2. The subscriber dials the DN of the remote station to which calls are to be forwarded.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Don’t Answer 4.3.2 Functional Operation The system administrator determines if the courtesy call option is active for each subscriber. After a subscriber dials the DN of the forwarding destination, one of the following events take place: ● If the remote station is idle: The HiPath 8000 rings it.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Don’t Answer > 4.4.2 ● If a subscriber is not currently registered, calls to that subscriber are diverted to the station CFDA forward-to DN. ● The system administrator can also configure the station CFDA feature such that when the subscriber activates it, calls automatically route to a fixed destination. Refer to Section 4.6, “Call Forwarding, Station—Fixed”, on page 4-8.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Enhanced Table 4-2 lists and describes the displays associated with this feature for the calling party, forwarding party, and forwarded-to party.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Remote Activation This capability is available for the station CFBL and station CFDA features. Refer to Section 4.2, “Call Forwarding, Station—Busy Line”, on page 4-4 and Section 4.4, “Call Forwarding, Station—Don’t Answer”, on page 4-6. 4.6.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Remote Call Forwarding 4.8 Call Forwarding, Station—Remote Call Forwarding 4.8.1 Definition The HiPath 8000-based station remote call forwarding (RCF) feature provides the capability to redirect calls intended for subscriber to a fixed destination.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Selective ● Selective call forwarding ● Time-of-day station call forwarding It allows the forwarded-to station to call the forwarding station and override (ignore) the forwarding. Therefore, the forwarded-to user can call the party that has forwarding active towards them. This occurs even when calling party information is not delivered to the subscriber.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Time-of-Day > 4.11.2 Call forwarding—return is an inherent capability of time-of-day forwarding; it allows the forwarded-to station to call the forwarding station and override (ignore) the forwarding. Refer to Section 4.9, “Call Forwarding—Return”, on page 4-10.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Call Forwarding, Station—Voice Mail Because a telephone user interface for administering the feature is not provided, a courtesy call is not provided when calls are forwarded due to time-of-day forwarding. 4.12 Call Forwarding, Station—Voice Mail 4.12.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features CDR 4.12.2 Functional Operation The system administrator sets the RTP parameter Srx/Main/CFVMCompatibility to specify if station CFBL, station CFDA, or both can be assigned to a subscriber at the same time CFVM is subscribed, as follows: ● ● Station CFBL: – When set to True, CFBL and CFVM can be assigned to the same subscriber. When both are assigned and active, CFBL takes precedence in a busy-line situation.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Guidelines for Implementation and Use ● Individual call forwarding CDRs are generated for the B-to-C and C-to-D call legs. 4.14 Guidelines for Implementation and Use The following are the forwarding target requirements: ● The number must be a routable destination in the private network or in the PSTN—for example, it cannot be a feature access code.
call_forwarding_user_features.fm HiPath 8000-Based Station Call Forwarding User Features Guidelines for Implementation and Use 4-16 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
other_user_features.fm Other User Features Anonymous Call Rejection 5 Other User Features This chapter describes other user features that reside in the HiPath 8000. Examples of such features are calling identity delivery and suppression features, abbreviated dialing features, redial and call return features, and display features.
other_user_features.fm Other User Features Anonymous Call Rejection To activate the anonymous call rejection feature, the subscriber goes off-hook, receives a dial tone, and enters *77. The HiPath 8000 provides a confirmation tone or announcement to acknowledge the activation. When anonymous call rejection is activated, the HiPath 8000 checks incoming calls to determine if the presentation of the calling party’s DN is allowed.
other_user_features.fm Other User Features Automatic Callback ● Number of activations that were provided with a confirmation tone because the confirmation announcement facilities were not available ● Number of deactivations that were provided with a confirmation tone because the confirmation announcement facilities were not available 5.1.4 CDR Call detail recording (CDR) is provided on a usage-sensitive basis.
other_user_features.fm Other User Features Automatic Recall To activate the automatic callback feature, the subscriber must make a call and either hear busy tone or receive no answer. The subscriber then goes onhook, goes offhook again, and enters *66. The user can also enter *66 upon hearing the busy tone. In either instance, the HiPath 8000 provides a confirmation tone or announcement to acknowledge that it received the callback request.
other_user_features.
other_user_features.fm Other User Features Calling Identity Delivery and Suppression ● CorNet-NQ/QSIG interworking provides support for calling (alerting/connected) party display at the calling party. ● Refer to Section 12.7.2, “Caller Identity Service”, on page 12-6 for information about the interworking that takes place for this feature between the HiPath 8000 and a legacy PBX. 5.5 Calling Identity Delivery and Suppression 5.5.
other_user_features.fm Other User Features Calling Name Delivery If the caller activates CIDS, the HiPath 8000 does not retrieve the permanent presentation status of the caller’s DN permanent presentation status. Instead, it delivers or suppresses the calling identity information according to the CIDS access code the subscriber entered. 5.5.3 Networking ● The presentation indicators for network parties are obtained from the data stored in the UCE context.
other_user_features.fm Other User Features Calling Name Delivery Blocking 5.6.3 Networking ● The presentation indicators for network parties are obtained from the data stored in the UCE context. ● SIP-Q sends the presentation indicators for network parties. 5.7 Calling Name Delivery Blocking 5.7.
other_user_features.fm Other User Features Calling Number Delivery 5.8 Calling Number Delivery 5.8.1 Definition The calling number delivery (CND) feature provides the terminating party with the possibility of receiving the number of the originating party. The calling party information is obtained from the system database.
other_user_features.fm Other User Features Calling Number Delivery Blocking 5.9 Calling Number Delivery Blocking 5.9.1 Definition The calling number delivery blocking (CNDB) feature, sometimes known as outgoing number delivery block, provides subscribers the capability to change the presentation status of their number when making a call. This feature can be provisioned at the business group level with a denied option at the subscriber level. Counters are provided for feature activation attempts. 5.9.
other_user_features.fm Other User Features Conference, Station-Controlled This feature is applicable to a subscriber who is also a call center agent on the Genesys call center and can control calls presented through the console application. The application lets the subscriber answer calls, make calls, transfer calls, and perform other useful functions. > Refer also to Section 16.7, “Interworking with Genesys Call Center”, on page 16-6.
other_user_features.fm Other User Features Conference, Station-Controlled – ● A conference-unaware participant does not know that the current call is a conference; it is a simple point-to-point call. Conference-unaware participants are always passive participants as well. Active or passive – An active participant has the ability to invoke advanced functionality associated with the conference feature—for example, initially creating a conference and adding parties to it.
other_user_features.fm Other User Features Customer-Originated Trace 5.12 Customer-Originated Trace 5.12.1 Definition The customer-originated trace feature (sometimes known as malicious call trace) provides subscribers the capability to generate an automatic trace of the last call received. Subscribers typically use this feature in response to malicious, harassing, or nuisance calls, in order to provide a trace over time of such activity.
other_user_features.fm Other User Features Hot Desking 5.14 Hot Desking 5.14.1 Definition The hot desking feature provides subscribers the capability to log on to and use a telephone in another office, or at another position in the same office. The telephone in the other office or position (the remote office telephone) then has all of the same HiPath 8000-provided features and capabilities as the telephone in the subscriber's usual office or position (the home office telephone).
other_user_features.fm Other User Features Last Number Redial Regardless of the telephone type, the remote office telephone’s message waiting indicator provides the status of the home DN’s mailbox upon logon. After logging off, the message waiting indicator is restored to show the status of the remote office telephone, rather than that of the home DN’s mailbox. 5.14.
other_user_features.fm Other User Features Return Call 5.16.2 Functional Operation The system administrator specifies the music to provide by using the intercept name associated with the music. This music can be identical for every instance in which a subscriber is placed on hold.
other_user_features.fm Other User Features Screen List Editing > 5.17.2 Siemens SIP endpoints also have local features that simplify returning of calls. Refer to the applicable user manual for information about those features. Functional Operation The system administrator can allow the subscriber to recall callers who have their calling identity suppressed. The administrator can also limit recalls to intraswitch calls (calls between business group members) only.
other_user_features.fm Other User Features Selective Call Acceptance 5.19.2 Functional Operation The selective call acceptance screen list is a set of numbers, each of which can be up to 15 digits long, for which calls should be connected to the subscriber. The screen list can contain up to 32 entries. To activate the selective call acceptance feature, the subscriber goes off-hook, receives a dial tone, and enters *27.
other_user_features.fm Other User Features Selective Call Forwarding Peg Counter Description SCA Attempt Denied Resource Unavailable The number of overflow counts for the SPCS and/or any circuits used to provide selective call acceptance control procedures. These counts are available on an individual SPCS basis. Table 5-1 Selective Call Acceptance Feature—Traffic Measurements (Sheet 2 of 2) 5.19.4 CDR CDRs are provided on a usage-sensitive basis.
other_user_features.fm Other User Features Selective Call Forwarding 5.20.2 Functional Operation The selective call forwarding screen list is a set of numbers, each of which can be up to 15 digits long, for which calls should be forwarded to a remote station. Business group extensions can also appear on the screen list. The screen list can contain up to 32 entries. To activate the selective call forwarding feature, the subscriber goes off-hook, receives a dial tone, and enters *63.
other_user_features.fm Other User Features Selective Call Rejection 5.21 Selective Call Rejection 5.21.1 Definition The selective call rejection feature, sometimes known as selective caller reject, provides the capability to build a list of numbers (known as a screen list) from which the subscriber does not want to accept incoming calls. This feature can be provisioned at the business group level with a denied option at the subscriber level. 5.21.
other_user_features.fm Other User Features Serial Ringing Peg Counter Description SCR Call To Denial Announcement The hourly peg counts of rejected calls. SCR All Calls Screened The hourly peg counts of all calls screened for a subscriber with selective call rejection active. SCR Customer Denied The overflow counts for the number of customers denied access to Resource Unavailable selective call rejection because of unavailable system resources.
other_user_features.fm Other User Features Serial Ringing > 5.22.2 > The simultaneous ringing feature is similar to this feature, but it rings several locations at the same time. Refer to Section 5.23, “Simultaneous Ringing”, on page 5-25. Functional Operation The system administrator determines the access codes associated with the serial ringing feature.
other_user_features.fm Other User Features Serial Ringing After the feature is activated, incoming calls cause the main DN to ring. If it is not answered in the configured ring duration interval, the next destination DN is rung for its configured ring duration interval. The first DN to answer is connected. > The HiPath 8000 uses the subscriber’s dialing characteristics, rather than the caller's, when it sets up calls to the numbers in the serial ringing list.
other_user_features.fm Other User Features Simultaneous Ringing 5.23 Simultaneous Ringing 5.23.1 Definition The simultaneous ringing feature provides subscribers the capability to be simultaneously rung at multiple locations. This is especially useful for those whose job duties require them to be in or around many different work areas throughout the day. > 5.23.2 > The serial ringing feature is similar to this feature, but it rings one location at a time. Refer to Section 5.
other_user_features.fm Other User Features Simultaneous Ringing Depending on configuration, the subscriber can also manage the simultaneous ringing list as follows: If the remote feature access (RFA) option is active, the subscriber can manage the list from any telephone, not just from the home DN. ● After dialing the RFA DN as configured by the HiPath 8000 administrator, the HiPath 8000 prompts the subscriber to enter the subscriber’s home DN, followed by a prompt to enter the subscriber’s PIN.
other_user_features.fm Other User Features Station Dialing 3. The user dials the correct home DN (main number) followed by the correct PIN. The media server collects these digits and passes them to the HiPath 8000. 4. The HiPath 8000 confirms the PIN and provides a confirmation tone or announcement to the user. 5. The user has the same access to the feature as if it was accessed from the home DN. However, local (non-PSTN extensions) must be prefixed with the digits 02.
other_user_features.fm Other User Features Station Dialing 5.24.2 Functional Operation The user can dial in the following ways: ● Offhook dialing: The user lifts the handset and hears dial tone (or obtains dial tone in a different manner) and enters keypad digits. The digits are automatically processed, without the need for inter-digit timeout or user intervention. ● Context dialing: The user enters and modifies digits before the HiPath 8000 processes those digits.
other_user_features.fm Other User Features Station Speed Calling—HiPath 8000-Based In this example, there are additional digits present, so the HiPath 8000 accepts these as the public network destination. Therefore, the HiPath 8000 must always assume that context dialing is being used, and must always look for the additional digit. 5.25 Station Speed Calling—HiPath 8000-Based 5.25.
other_user_features.fm Other User Features Teleworking ● 2-digit speed calling entry: *75, followed by the number (20 through 49) to associate with the entry, and the number to store for the entry To dial a speed calling list entry, the subscriber goes off-hook, receives a dial tone, and enters the number associated with the entry—for example, to dial entry 23, the subscriber enters the digits 23.
other_user_features.fm Other User Features Toll and Call Restrictions 5.27 Toll and Call Restrictions 5.27.1 Definition The toll and call restrictions feature provides destination limitations on calls originated at designated stations and private facilities. The associated subfeatures can be assigned to any subscriber or private facility with callorigination capability, unless otherwise restricted by an assigned feature. 5.27.
other_user_features.fm Other User Features Transfer 5.27.3 ● Guidelines for Implementation and Use The screening is based on the North American numbering plan (NANP). These features do not screen calls made using other dialing plans (such as extension dialing and business group dialing plans). Refer to the following for more information about these features: ● – Section 6.7, “Business Group Dialing Plan”, on page 6-5 – Section 6.14, “Extension Dialing”, on page 6-11 – Section 9.
other_user_features.fm Other User Features Transfer 5.28.2 Functional Operation The transfer features are implemented between the SIP endpoint and the HiPath 8000, as follows: ● The request and type of transfer is controlled by the telephone. ● The processing and checking (for example, for transfer restrictions) is controlled by the HiPath 8000.
other_user_features.fm Other User Features Transfer Transfer Status Transferring Party (Party A) Display Transferred Party (Party B) Display TransferredTo Party (Party C) Display Party A puts party B on consultation hold by selecting Blind Transfer — Party A’s name — and number; see note 1 Party A performs a blind transfer to party C, party C is ringing — Party C’s name and number Party B’s name and number Party C answers — Party C’s name and number Party B’s name and number 1.
other_user_features.fm Other User Features Transfer Table 5-5 lists and describes the displays associated with transfers with third-party consultation for the transferring party, transferred party, and transferred-to party.
other_user_features.fm Other User Features Transfer Security 5.29 Transfer Security 5.29.1 Definition The transfer security feature provides the capability to ensure that: ● A transferred party is not left ringing for too long at another internal user’s endpoint ● A user does not transfer a party to an invalid destination This feature can also provides an intercept to a provisioned destination if a call transfer recall occurs and the transferring party is busy and cannot be camped onto. > 5.29.
other_user_features.fm Other User Features Transfer Security 5.29.3 CDR For complex call scenarios—for example, when a call is transferred with consultation—a thread identifier correlates the CDRs associated with each leg of the call. Refer to Section 13.2, “Call Detail Record Generation”, on page 13-1. A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
other_user_features.fm Other User Features Transfer Security 5-38 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
business_group_features.fm Business Group Features Attendant Answering Position 6 Business Group Features This chapter describes features that are specific to business groups. These features simplify such tasks as dialing plan administration, intragroup communication, and traffic measurements.
business_group_features.fm Business Group Features Attendant Answering Position 6.1.2 Functional Operation The system administrator identifies a hunt group as an attendant answering group. The administrator also specifies values for the following capabilities available to all hunt groups: ● Time-in-queue threshold value: Refer to Section 7.2, “Hunt Group”, on page 7-3. ● Night service DN: Refer to Section 7.5, “Hunt Group—Night Service”, on page 7-6.
business_group_features.fm Business Group Features Business Group Access Codes 6.2 Business Group Access Codes The business group access codes feature allows the assignment of feature access codes, network access codes, and attendant access codes to be separately administrable for each business group. 6.3 Business Group Account Codes 6.3.
business_group_features.fm Business Group Features Business Group Billing ● 6.5 If the authorization code is invalid: The system prompts the subscriber to re-enter the authorization code. If the second entry is also invalid, the call is given intercept treatment. Business Group Billing The business group billing feature supports the Message Detail Recording - Regional Accounting Office (MDR-RAO) per GR-610 Message Detail Recording (MDR) (FSD 02-021110).
business_group_features.fm Business Group Features Business Group Dialing Plan 6.7 Business Group Dialing Plan 6.7.1 Definition The business group dialing plan provides virtual private branch exchange (PBX) service via the HiPath 8000 and appears to be a standalone entity within which the business group-specific dialing plan is in force. To reach lines outside of the business group, the caller usually dials an access code.
business_group_features.fm Business Group Features Business Group Dialing Plan > ● The customer can use * and # as the first (and perhaps only) digit of any of the access codes. ● If needed, the customer can specify a code from 1 to 5 digits for use as an equivalent to *. ● * code conflicts are resolved by use of critical inter-digit timing or use of # as an end-of-dialing indicator. Access Number of Description Code Type Digits Attendant 1 to 5 Connects a HiPath 8000 user to the attendant.
business_group_features.fm Business Group Features Business Group Main Number – L1-L0-extension: if L1 is administered in the private numbering plan – L2-L1-L0-extension: if L2 is administered in the private numbering plan On-net dialing: On-net access code (HiPath on-net barrier code) is dialed before the fully qualified private number.
business_group_features.fm Business Group Features Business Group Traffic Measurements > The basic traffic tool is another performance monitoring tool used to view snapshots of the traffic for incoming SIP calls to the HiPath 8000. Refer to Section 15.3, “Basic Traffic Tool”, on page 15-3. 6.9.2 Functional Operation The system administrator can activate or deactivate this feature for the business group. The business group measurement data is delivered to the iSMC or HiPath 8000 Assistant.
business_group_features.fm Business Group Features Business Group Web Portal Measurement Description Originating usage Traffic usage generated by originating calls measured at a single, common point in the system network. The measurement collection software scans all calls in the system every 100 ms. It counts the number of calls originated from the business group. The resulting count represents the usage for that period (i.e., count x 100ms = usage).
business_group_features.fm Business Group Features Direct Outward Dialing 6.12 Direct Outward Dialing 6.12.1 Definition The direct outward dialing (DOD) feature allows subscribers to have direct outward dialing access to the PSTN. This access is usually signaled using a 1- to 5-digit PSTN access code that is defined in the business group dialing plan. Refer to Section 6.7, “Business Group Dialing Plan”, on page 6-5.
business_group_features.fm Business Group Features Extension Dialing 6.14 Extension Dialing 6.14.1 Definition The extension dialing feature allows a subscriber in a business group to dial other subscribers in the same business group by dialing an abbreviated number that is synonymous with the extension number. Extension dialing is also known as station-to-station dialing. > 6.14.2 Although this feature is sometimes known as intercom dialing, it does not provide a speakerphone-like capability.
business_group_features.fm Business Group Features Multiple Language Announcements 6.16 Multiple Language Announcements The multiple language announcements feature provides the capability to assign different languages to each subscriber, incoming trunk group, endpoint, and PRI. > Siemens SIP endpoints also have local features that provide the capability to define the language for menu prompts. Refer to the applicable user manual for information about those features.
business_group_features.fm Business Group Features Station Restrictions 6.17.2 Functional Operation The HiPath 8000 checks station restrictions before completing calls and performing call transfers. If a call is found to be in violation of configured restriction levels, the system routes the call to error treatment and subsequently releases it. Because station restriction is not a visible subscriber service, it does not increment a visible usage counter. 6.17.2.
business_group_features.fm Business Group Features Voice VPN 6.17.2.3 Fully-Restricted Lines with Attendant Access A fully-restricted line with attendant access can access the attendant for information and to requests transfers to another DN within the business group.
other_group_features.fm Other Group Features Call Pickup—Group 7 Other Group Features This chapter describes the group call pickup feature, which allows users to answer calls on behalf of one another, and the hunt group feature, which permits calls to be routed to an idle line within a group of specified lines.
other_group_features.fm Other Group Features Call Pickup—Group 7.1.2 Functional Operation The system administrator creates the pickup group. Every business group can be configured with its own feature access code, or the default value **3 can be used. During an incoming call to a pickup group member, the following notifications take place: For the called station: The called party hears ringing. ● For other pickup group members: Pickup Call? appears on each member’s display.
other_group_features.fm Other Group Features Hunt Group 7.1.4 Guidelines for Implementation and Use The following are the guidelines associated with the group call pickup feature: The system administrator must configure each pickup group member’s SIP terminal number and service ID to be equal to the group member’s DN. ● Important Note > If the pickup group member is not configured in this manner, the feature does not function properly.
other_group_features.fm Other Group Features Hunt Group 7.2.2 Functional Operation A call is placed to a hunt group by dialing the pilot number. The hunting sequence may be as follows: ● Circular hunting with memory: An incoming call causes the HiPath 8000 to progressively search for an idle station within the hunt group, starting with station position stored when the previous call to the hunt group was made.
other_group_features.fm Other Group Features Hunt Group—Make Busy 3. Otherwise, if CFBL is active on the group via the pilot DN, the call is forwarded. Refer to Section 4.2, “Call Forwarding, Station—Busy Line”, on page 4-4. 4. Otherwise, if an Overflow DN is present, the call is routed to it. Refer to Section 7.7, “Hunt Group—Overflow”, on page 7-7. 5. Otherwise, busy tone is given. This is the default.
other_group_features.fm Other Group Features Hunt Group—Music On Hold To deactivate the make busy feature, the subscriber goes off-hook, receives a dial tone, and either enters he correct access code or presses the Hunt Make Busy key again. When a hunt group member change the make-busy status, the member hears an announcement that indicates whether the service is active. 7.4 Hunt Group—Music On Hold Refer to Section 5.16, “Music On Hold—HiPath 8000-Based”, on page 5-15. 7.
other_group_features.
other_group_features.fm Other Group Features Hunt Group—Queuing 7.8 Hunt Group—Queuing 7.8.1 Definition Queuing provides an enhancement to the basic hunt group overflow on busy treatment, modifying both the determination and handling of busy conditions for the group. Refer to Section 7.2.2, “Functional Operation”, on page 7-4 for details about how busy conditions are determined, along with the sequence of treatment upon determining busy.
other_group_features.fm Other Group Features Hunt Group—Stop Hunt 7.9 Hunt Group—Stop Hunt 7.9.1 Definition The stop hunt feature provides the ability to terminate all hunting within the group when encountered on a member of the hunt group. It is checked during the hunt before moving to the next line in the hunt sequence. Calls to a line’s private DN are still permitted, as are call originations. 7.9.
other_group_features.fm Other Group Features Hunt Group—Traffic Measurements The hunt group measurement data is delivered to the iSMC or HiPath 8000 Assistant. The hunt group administrator can access the group’s measurements and monitor the group by periodically performing a visual inspection of the reported data.
emergency_calling_features.fm Emergency Calling Features Definition 8 Emergency Calling Features This chapter describes how the HiPath 8000 uses a Siemens or Cisco gateway, sometimes in conjunction with the Telident station translation system (STS), to provide emergency calling (E911) support. This chapter is applicable to the United States only. > Refer to the HiPath 8000 E-911 Support and Planning Guide for more information about this feature.
emergency_calling_features.fm Emergency Calling Features Configuration Options – Cisco gateway in conjunction with a Telident STS > Although the Telident STS is not required for emergency calling in configurations that use the RG 8700, the enterprise can choose to incorporate one into its system for other purposes. For simplicity, the remainder of this chapter uses the term Siemens gateway to refer to the HiPath 4000 and RG 8700, except where operation differs among the products. > 8.
emergency_calling_features.fm Emergency Calling Features Functional Operation – The HiPath 8000 sends the LIN to a gateway with a Telident STS or CAMA trunk. or – The Telident STS associates the calling party number sent by the HiPath 8000 to the associated LIN in its database. Depending on the gateway used: – HiPath 4000 or Cisco gateway: The Telident STS sends the LIN to the PSAP using a CAMA trunk. – RG 8700 gateway: The gateway sends the LIN to the PSAP using a CAMA trunk.
emergency_calling_features.fm Emergency Calling Features Functional Operation When the HiPath 4000 gateway is used: 1. The HiPath 8000 signals the user’s calling party information to the Siemens gateway, as follows: ● If the LIN is administered in the HiPath 8000: The HiPath 8000 sends the user’s LIN. ● If the LIN is administered in the Telident STS: The administrator configures the HiPath 8000 to send the CPN, which is the user’s fully-qualified private number.
emergency_calling_features.fm Emergency Calling Features Guidelines for Implementation and Use 8.3.2 RG 8700 Gateway When the RG 8700 gateway is used: 1. The HiPath 8000 signals the user’s calling party information to the gateway. When it sends the user’s LIN, the signaling is performed in accordance with the CorNet-NQ protocol. The HiPath 8000 sends the LIN in the SIP body in the clear to the RG 8700. 2. The gateway converts the LIN to the 10-digit NANP CAMA MF format. 3.
emergency_calling_features.fm Emergency Calling Features Guidelines for Implementation and Use The HiPath 8000’s rate area capabilities provide for source-based routing of emergency calls to the correct Siemens gateway when the enterprise network encompasses multiple E911 tandem switch jurisdictions. ● Cisco gateway: If the HiPath 8000 network spans PSAP jurisdictions, each local PSAP jurisdiction requires its own Cisco gateway and Telident STS.
routing_and_translation_features.fm Routing and Translation Features Digit Modification for Digit Outpulsing 9 Routing and Translation Features This chapter describes the HiPath 8000 features that provide routing and translation, including public numbering plan compliance and routing that varies depending upon such factors as origin, traffic, and bearer capability. > 9.
routing_and_translation_features.fm Routing and Translation Features E.164 Compliance 9.2.2 Functional Operation When the user enters *99, a connection is made to an announcement that states the DN of the line from which the call is being made. 9.3 E.164 Compliance 9.3.1 Definition The E.164 compliance feature provides the ability to dial or receive any E.164 compliant number. 9.3.2 Functional Operation The subscriber can dial any number, including international prefixes and country codes.
routing_and_translation_features.fm Routing and Translation Features International Translation Support 9.4.3 Networking ● Intercept destinations cannot exist across the network interface. ● Refer to Section 12.7.4, “Intercept Treatment”, on page 12-7 for information about the interworking that takes place for this feature between the HiPath 8000 and a legacy PBX. 9.5 International Translation Support The international translation support feature provides E.
routing_and_translation_features.fm Routing and Translation Features North American Numbering Plan Compliance 9.7.1 555-1212 Line Numbers The 555-1212 line numbers feature provides support for 555-1212 numbers for directory assistance. 9.7.2 Carrier Access Codes The carrier access codes (CAC) feature provides three-digit access codes that are sent in conjunction with four-digit carrier identification codes (CICs). The format of CAC is three digits preceding a four-digit CIC.
routing_and_translation_features.fm Routing and Translation Features Routing Features 9.7.5 Prefix Digit Translation This feature provides the translation of the international and national prefixes that are used. Normally, the international prefix is 00 and the national prefix is 0, but this feature allows other combinations of digits to be used as the international or national prefix as specified by the dialing plan. 9.7.
routing_and_translation_features.fm Routing and Translation Features Routing Features 9.8.4 Bearer Capability Routing The bearer capability routing feature allows the routing of calls to different trunk groups based on the originator's bearer capability. For example, all 64 kbps bearer calls can route to one trunk group and all other bearer capabilities to a different trunk group. The bearer capability of a call can be one of the following: ● Speech ● 3.
routing_and_translation_features.fm Routing and Translation Features Vertical Service Codes > In the following description of requirements to reroute calls, a survivable branch refers to a gateway switch such as the RG 8700 or Comdasys Convergence 1600. When the host (HiPath 8000) connection is lost, the survivable branch permits subscribers to continue to make calls locally (SIP-to-SIP), as well as calls to and from the PSTN (SIP-to-ISDN and ISDN-to-SIP), including E911 calls.
routing_and_translation_features.fm Routing and Translation Features Virtual DN 9.10 Virtual DN The virtual DN feature permits the system administrator to create a DN that does not have a connection. The DN can be used for station RCF or it can be a means of reserving a number for future use. > 9-8 If the DN is being used for station RCF, it cannot be subscribed to any other services. Refer to Section 4.8, “Call Forwarding, Station—Remote Call Forwarding”, on page 4-10 for more information.
call_admission_control_features.fm Call Admission Control Features Definition 10 Call Admission Control Features This chapter describes the HiPath 8000’s integrated call admission control (CAC) feature, which provides for management of the bandwidth used for the transport of media traffic (such as RTP audio and T.38 fax) through the bottleneck links that may exist in an enterprise network. > 10.
call_admission_control_features.fm Call Admission Control Features CAC Groups and Policies 10.2 CAC Groups and Policies A CAC group represents the group of endpoints being served by the bandwidth-limited link which needs to be monitored.
call_admission_control_features.fm Call Admission Control Features Functional Operation ● The IP address and name of the WAN access router serving the CAC group (such as a branch office) that sends SNMP traps indicating the link up/down status of the primary access link. This item is only required if the optional Link Failure Web Service is used.
call_admission_control_features.fm Call Admission Control Features CAC Rerouting 10.4 CAC Rerouting One of the benefits of the integrated CAC solution is the HiPath 8000's ability to provide rerouting via the PSTN in case there is not enough bandwidth in the bandwidth-limited link from the branch office to the WAN. The rerouting call scenarios are tightly coupled with the HiPath 8000’s ability to reroute calls based on a provisionable set of SIP response codes. Refer also to Section 9.8.
call_admission_control_features.fm Call Admission Control Features Call Denial If there is not enough bandwidth available in either link, the resource reservation is not successful and the RM function sends a negative response equivalent to a SIP 606 response code. The HiPath 8000 then reroutes the call between these two subscribers through their local SIP gateways and the PSTN. 10.4.2 Rerouting PSTN Calls to Alternate SIP Gateways PSTN calls can also be rerouted to alternate SIP gateways.
call_admission_control_features.fm Call Admission Control Features Traffic Measurement the secondary capacity for the CAC policy of the associated access link. If the primary link access is restored, the Link Failure Web Service also provides a command to the HiPath 8000 to switch back to the primary capacity of the CAC policy. 10.
pri_features.fm PRI Features Calling Number Delivery over PRI 11 PRI Features This chapter describes HiPath 8000 features that support network-side PRI capabilities.
pri_features.fm PRI Features PRI—Supported and Unsupported Features 11.4 PRI—Supported and Unsupported Features The following PRI features are supported: ● B-channel selection algorithm: Low-Low and High-High ● PRI hunt group policies: – Sequential forward – Sequential backward – First-in-first out – Round robin forward – Round robin backward ● B-channel availability control, also known as B-channel availability signaling (BCAS) procedures.
qsig_tunneling_features.fm QSIG Tunneling Features Definition 12 QSIG Tunneling Features This chapter describes SIP-Q, which permits the HiPath 8000 to interwork with another HiPath 8000, the HiPath 4000, or a QSIG PBX connected via the RG 8700 gateway.
qsig_tunneling_features.fm QSIG Tunneling Features Definition This feature applies where one of the subscribers in a call is a SIP device and another party is behind a gateway served by NQ/QSIG tunneling over SIP. A typical corporate network may consist of legacy PBXs employing QSIG networking, interconnected with an IP network employing SIP. A call can originate in either the QSIG or SIP network, and can subsequently be interworked via a gateway that provides translation and mapping between QSIG and SIP.
qsig_tunneling_features.fm QSIG Tunneling Features Functional Operation ● Section 9.1, Path Replacement ● Section 9.8, Additional Progress Description SIP-Q also provides the following features network-wide: ● SIP-Q-to-SIP-Q pass-through—for example, when a legacy user is routed over IP to another legacy user located a distance away. This capability can save TDM costs for an enterprise. ● Failover recovery superior to that of H.323 standard communications. 12.
qsig_tunneling_features.fm QSIG Tunneling Features Call Diversion Over Multiple Platforms This is accomplished by implementing the following: ● Supplementary Service Call Transfer (SS-CT) ● Transit functionality ● Path Replacement additional network feature (ANF-PR) Refer also to Section 12.6, “Transfer”, on page 12-5. 12.
qsig_tunneling_features.fm QSIG Tunneling Features Transfer 12.6 > Transfer Refer also to Section 5.28, “Transfer”, on page 5-32. The QSIG SS-CT and ANF-PR operations are supported for transfer by join (both attended and semi-attended transfers) and blind transfer scenarios in which one of the parties is a SIP-Q gateway. From the QSIG perspective, the HiPath 8000 can be a transferring, transferred and transferred-to PBX.
qsig_tunneling_features.fm QSIG Tunneling Features Local Feature Interworking 12.7.1 Call Pickup—Group > Refer to Section 7.1, “Call Pickup—Group”, on page 7-1 for a description of this feature. ● If a HiPath 8000 subscriber calls a legacy user, another legacy user in the same PBX can pick up the call. ● If a legacy user calls a HiPath 8000 subscriber, another HiPath 8000 subscriber can pick up the call. ● A pickup group member can only pick up calls in the same PBX as the ringing telephone.
qsig_tunneling_features.fm QSIG Tunneling Features Local Feature Interworking Hunting can only occur between users on the same PBX. For example: ● If a HiPath 8000 subscriber calls a legacy user, the call is hunted to a legacy user in the same PBX. This situation is treated similarly to station call forwarding. ● If a legacy user calls a HiPath 8000 subscriber, the call is hunted to a HiPath 8000 subscriber. 12.7.4 Intercept Treatment > ● ● Refer to Section 9.
qsig_tunneling_features.fm QSIG Tunneling Features CDR ● If a HiPath 8000 subscriber (A) is connected to a legacy user (B) and another legacy user in the same PBX (C) calls A, A consults with C and then invokes conference with all three. ● If a legacy user (A) is connected to a HiPath 8000 subscriber (B) and a legacy user in the same PBX (C) calls A, A consults with C and then invokes conference with all three.
CDR_features.fm CDR Features Billing for Business Groups 13 CDR Features This chapter describes the CDR features that simplify call tracking and billing for the HiPath 8000. > ● Refer to the HiPath 8000 Call Detail Recording (CDR) Reference Guide for detailed information about CDR. ● Refer to the following for information about administration and operational practices associated with these features: ● 13.
CDR_features.
CDR_features.fm CDR Features Usage Reporting 13.5 Usage Reporting The usage reporting feature provides for the generation of CDRs for all calls, distinguishing between completed and non-completed calls (ring no answer, busy status).
CDR_features.fm CDR Features Usage Reporting 13-4 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
security_features.fm Security Features Account and Password Management Security 14 Security Features This chapter describes the HiPath 8000 features that provide security for various aspects of the system, such as billing records, data files, and administration interfaces.
security_features.
security_features.fm Security Features Data File Security ● If the billing server initiates the transfer (also known as file transfer by pull), either FTP or secure file transfer protocol (SFTP) can be used. > Because HiPath 8000 Assistant is installed on the compact HiPath 8000 itself, it uses neither FTP nor SFTP to access data. Both types of connections can be protected with IPsec as long as the billing mediation server supports it. Refer to Section 14.9, “IPsec Baseline”, on page 14-8. 14.
security_features.fm Security Features Event Logging 14.4.2 Functional Operation A host-based intrusion detection system (IDS) monitors incoming traffic in parallel to the traffic being sent to normal application processing. When incoming traffic from an IP address exceeds the provisioned threshold, all traffic from that IP address is placed on a black list, and is temporarily blocked. The black list operates as follows: 1.
security_features.fm Security Features Event Logging – Recent non-security related OAM&P activity via the recent change log > 14.5.1 This security event log is different from, and is kept completely separate from, the system event log, which logs abnormal runtime activity. Functional Operation The security log files are rotated on a daily basis. Archived security log files for the previous 30 days are retained; files older than 30 days are automatically removed.
security_features.fm Security Features File Transfer Security ● Commands that retrieve customer data ● Data synchronization commands ● Data or network element recovery commands 14.6 File Transfer Security 14.6.1 Definition The file transfer security feature provides for the transfer of CDR files or traffic measurement data files. Either the billing mediation server or the HiPath 8000 can initiate the transfer; however, it is preferable for the HiPath 8000 to do so. 14.6.
security_features.fm Security Features Hypertext Transfer Protocol over SSL 14.6.3.2 Confidentiality Supported FTP confidentiality options vary by interface and include the following: ● iNMC and iSMC: FTP transfers may be protected via IPsec. ● Basic traffic tool: Secure FTP is used to securely retrieve data from the HiPath 8000. ● CDR delivery: Refer to Section 14.2.2, “Functional Operation”, on page 14-2. ● OS-level FTP for management of the HiPath 8000 Linux servers: Secure FTP is supported.
security_features.fm Security Features IPsec Baseline When the user attempts to log on, the iNMC or iSMC performs OS-level authentication of the user name and password against the server system/domain on Windows. The iNMC and iSMC servers also support the modification of user’s password if the user exists on the server system itself, rather than on the Windows domain. 14.9 IPsec Baseline 14.9.
security_features.
security_features.fm Security Features Provisioning and Security Logging The password protection mechanism is based on the Twofish algorithm, which is a two-way encryption algorithm. This is different from the requirement for one-way encryption on normal user passwords because the iNMC must be able to retrieve the password from the database to insert it into the command with the remote network element (NE).
security_features.fm Security Features Secure Storage of CDR Password Secure Shell is also present in the CLI. Refer to Section 14.13, “Secure CLI”, on page 14-10. 14.15 Secure Storage of CDR Password Passwords for the HiPath 8000 CLI login are stored encrypted within the Linux OS. Applicationlevel passwords for transferring CDRs from the HiPath 8000 to the billing mediation server are stored via two-way encryption within the HiPath 8000 database. 14.16 SIP Privacy Mechanism 14.16.
security_features.fm Security Features TLS Support originator of a message—for example, a Via header might reveal the service provider through whom the user sends requests, which might in turn strongly hint at the user's identity to some recipients. For these reasons, the participation of intermediaries is also crucial to providing privacy in SIP. 14.17 TLS Support 14.17.1 Definition The transport layer security (TLS) support feature provides for secure signaling based on TCP and the TLS protocols.
security_features.fm Security Features TLS Support ● When responding to a 401 (or 407) challenge from the HiPath 8000 in response to any form of a SIP request, such as a SIP REGISTER or SIP INVITE Endpoint authentication is performed using HTTP digest authentication over the TLS-secured link. Refer to Section 16.2, “HTTP Digest Authentication”, on page 16-1. Within a single administrative domain, server authentication takes place when the TLS connection is established.
security_features.fm Security Features TLS Support 14-14 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
serviceability_features.fm Serviceability Features Administrator Identification and Authentication 15 Serviceability Features This chapter describes the HiPath 8000 features that improve serviceability, such as diagnostics and debug tools, code controls, and administrator controls. > 15.
serviceability_features.fm Serviceability Features Backup and Restore 15.2 Backup and Restore 15.2.1 Definition The backup and restore features provides for full system backup of the HiPath 8000 data as well as the code, including the operating system and all applications. This supports the restoration of the entire single- or dual-node cluster in case of a catastrophic event. The backup and restore process is applicable to the following scenarios: ● Failure of a complete dual-node cluster.
serviceability_features.fm Serviceability Features Basic Traffic Tool ● The backup feature described in this section does not back up the following elements: – Database contents: The database backup procedures is required. – Database archive logs: As long as a database backup is created, these files are not required. – Call data records: These records are generally transferred from the system on a regular basis, and therefore need not be backed up.
serviceability_features.fm Serviceability Features Call Gapping Code Controls ● Busy hour call attempts for the current day ● Statistical data for selected period ● Statistical data for today The graphical output is based on data the system collects every 15 minutes. The user can print the output from any of the graphical screens. 15.3.2.
serviceability_features.fm Serviceability Features Element Mass Provisioning 15.6 Element Mass Provisioning 15.6.1 Definition The element mass provisioning feature provides for the mass processing of provisioning commands. This feature supports those commands that are available via the iNMC and HiPath 8000 Assistant. 15.6.2 Functional Operation This feature uses command line scripts implemented via the CLI to simplify the provisioning of network elements.
serviceability_features.fm Serviceability Features Log File Retrieval Tool When creating or modifying subscribers, the administrator can assign a feature profile to apply to all HiPath 8000 subscribers, or can assign a business group-specific feature profile to the subscriber. 15.
serviceability_features.fm Serviceability Features Process Debug Tool Two different times (peak and off-peak) define different timer values between each Trunk/PRI channel audit. The default value of the timers are 1 second for peak times and 0.25 seconds for off-peak times. These times are also configurable, and can be fine-tuned to ensure that the audit cycles through all the resources at least twice a day without taking system time away from call processing. 15.
serviceability_features.fm Serviceability Features System Upgrade The updating and downgrading of this area is an automated part of the patchset loading instructions or file. This information can be displayed locally or remotely, and can be printed. 15.16 System Upgrade The system upgrade feature provides for an automated software installation process and software upgrade process. It can be activated remotely and is non-service affecting. It also includes a fallback to a "Safe" configuration. 15.
sip_signaling_features.fm SIP Signaling Features Audit Mechanisms 16 SIP Signaling Features This chapter describes the HiPath 8000 features that support SIP signaling and the interworking with other elements such as application servers, voice conferencing applications, and voice mail systems. > 16.
sip_signaling_features.fm SIP Signaling Features HTTP Digest Authentication In accordance with RFC 3261, SIP: Session Initiation Protocol, it is always used for authentication in the HiPath 8000. > 16.2.2 Refer to Section 14.17, “TLS Support”, on page 14-12 for information about how digest authentication is used with TLS.
sip_signaling_features.fm SIP Signaling Features Integration with HiPath Xpressions 16.3 Integration with HiPath Xpressions This feature provides SIP support for routing to and from the Siemens HiPath Xpressions system. Xpressions is Siemens' preferred unified messaging product.
sip_signaling_features.fm SIP Signaling Features Integration with HiPath ProCenter 16.4.2 Functional Operation With the HiPath 8000 integration, the HiPath ProCenter server communicates with the HiPath 8000 via CSTA XML. This allows the HiPath ProCenter server to monitor user (agent) and group (hunt group) devices. The media server is always used to play music in queue, and is the default during any HiPath ProCenter queue processing flow when there is no other step.
sip_signaling_features.fm SIP Signaling Features Integration with OpenScape If HiPath ProCenter is not functioning properly, users can continue to answer calls through backup routing. The core backup routing concept of HiPath ProCenter is that if the application becomes unavailable, the switch routes calls to available users who are logged on to the switch until the application is restored.
sip_signaling_features.fm SIP Signaling Features Interworking with Application Servers rules. Based on the HiPath 8000 associated AoR device availability and rules, the call may be routed to the HiPath 8000 where normal translation is performed, resulting in the call being routed to the HiPath 8000 user's device. Calls from external interfaces to the published OpenScape AoR are processed the same as calls initiated by HiPath 8000 users to the OpenScape published AoR. 16.
sip_signaling_features.fm SIP Signaling Features Interworking with Unified Messaging Systems The RG 8700 also provides a survivable media gateway when connection to HiPath8000 is lost. The RG8700 has minimum service knowledge; all service knowledge is with the HiPath 8000. After the HiPath 8000 selects the service and routes to a specific endpoint, the RG 8700 maps the requested service to its ISDN equivalent.
sip_signaling_features.fm SIP Signaling Features Interworking with Voice Mail Systems 16.11 Interworking with Voice Mail Systems 16.11.1 Definition The interworking with voice mail systems feature provides signaling and interworking with SIPbased third-party voice mail systems.
sip_signaling_features.fm SIP Signaling Features SIP Over TCP/TLS Support 16.14 SIP Over TCP/TLS Support 16.14.1 Definition The SIP over TCP/TLS support feature provides SIP over TCP and SIP over TLS, in accordance with RFC 3261.
sip_signaling_features.fm SIP Signaling Features SIP Privacy Mechanism 16.14.3 Guidelines for Implementation and Use As defined by RFC 3261 and implemented by the HiPath 8000, the TLS security mechanism has known limitations related to scalability and reliability. These limitations are described in section 26.4.3 of RFC 3261. In the HiPath 8000, these limitations manifest themselves as follows when TLS is used: ● HiPath 8000 port capacity is reduced.
sip_signaling_features.fm SIP Signaling Features SIP UA Registration Renewal During WAN Outage 16.18 SIP UA Registration Renewal During WAN Outage This feature provides a mechanism to improve recovery from intermittent losses of connectivity by allowing SIP UA registrations to be renewed on a provisional basis. From the perspective of the SIP UA, this feature maintains its registration during a WAN outage until the configured time in seconds expires.
sip_signaling_features.fm SIP Signaling Features SIP UPDATE Method Support 16-12 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
csta_support_features.fm CSTA Support Features 17 CSTA Support Features This chapter describes how the HiPath 8000 provides a standard European Computer Manufacturers’ Association (ECMA) Computer Supported Telecommunications Applications (CSTA) protocol interface to external CTI applications, which permits applications such as ComAssistant, OpenScape, and HiPath ProCenter to control the HiPath 8000 SIP endpoints.
csta_support_features.fm CSTA Support Features CSTA Protocol Interface 17.1 CSTA Protocol Interface 17.1.1 Definition This feature provides a CSTA protocol interface to applications, such as CAP and ComAssistant, that support the ECMA standard. This feature has been released only with the Siemens Common Application Platform (CAP) to control and monitor telecommunication activities on SIP endpoints.
csta_support_features.fm CSTA Support Features CSTA Services Support 17.2 CSTA Services Support Table 17-1lists the CSTA services the HiPath 8000 supports.
csta_support_features.
csta_support_features.fm CSTA Support Features Data Synchronization 17.4 Data Synchronization CSTA-enabled applications can make use of the data synchronization feature. Refer to Section 18.4, “Data Synchronization”, on page 18-2. 17.5 HiPath 8000-Provided Calling Name The HiPath 8000 provides the calling name via the call monitoring events to the CSTA-enabled application. This calling name is only presented to the application user if the external directory does not match an entry for the user's DN.
csta_support_features.fm CSTA Support Features Multiple Time Zone Support 17-6 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
system_functions_features.fm System Functions and Features Agent for OAM&P 18 System Functions and Features This chapter describes the HiPath 8000 functions and features that support such tasks as alarm reporting, message waiting indicator control, and recovery handling. > 18.
system_functions_features.fm System Functions and Features Announcements 18.3 Announcements The announcements feature provides: ● Audible notifications for the status of certain HiPath 8000 features ● User prompts to enter information when it is required to execute a feature The media server provides announcements for the HiPath 8000; the compact HiPath 8000’s integrated media server provides its announcements.
system_functions_features.fm System Functions and Features Interworking with Automated Attendant Systems 18.6 > Interworking with Automated Attendant Systems An automated attendant system accepts all incoming calls and leads the caller through a menu offering different options, such as company operator assistance, direct extension dialing, voice-controlled services, and voice mail connection. Automated attendant functions are included with the IP Unity Messaging application.
system_functions_features.fm System Functions and Features Message Waiting Indicator The HiPath 8000 ensures that subscribers continue to receive accurate MWI in any of the following circumstances: ● The SIP endpoint loses power temporarily. ● A restart of the SIP endpoint becomes necessary. ● A temporary WAN outage prevents an update of the MWI when a message was left for the subscriber. ● A hot desking subscriber logs in at a remote office telephone. Refer also to Section 5.
system_functions_features.fm System Functions and Features Overload Handling The HiPath 8000 supports the message waiting indicator notification function according to the mandatory requirements of GR-866-CORE. VMWI is supported according to GR-1401-CORE. The indications are provided through signaling and interworking with Siemens or third-party voice mail systems. 18.9.
system_functions_features.fm System Functions and Features Overload Handling ● Ensures that accepted calls result in completed calls Overload can occur due to random periods of high traffic or administration and maintenance activities. Therefore, the overload mechanism monitors response time and tracks the number of messages on input queues. The signaling managers and applications then respond to the situations appropriately. Overload controls do not require administration. 18.10.
system_functions_features.fm System Functions and Features Recovery Handling Threshold Threshold Description Maximum Value Minor CPU usage This value represents the minor load congestion level threshold 90 value (as a percent) for CPU usage. Major CPU usage This value represents the major load congestion level threshold 95 value. Critical CPU usage This value represents the critical load congestion level threshold 98 value.
system_functions_features.fm System Functions and Features SDP Transparency In addition, within a session media type, various encodings in the form of codec specifications are available, which permits efficient utilization of the bandwidth resource for the media session. The network elements involved in the media exchange are able to negotiate their media encoding requirements at various stages of the media session or call.
system_functions_features.fm System Functions and Features Silence Suppression Disabling For SIP endpoints, SDP data is transported transparently without parsing, which permits the SIP session manager to forward the received SDP data to the second leg of the call without any modification in the parameters. Within the HiPath 8000, the UCE is the interacting coordinator among different signaling types. The connection control manager (CCM) is not aware of the remote endpoint it is talking to.
system_functions_features.fm System Functions and Features SOAP Interface 18.14 SOAP Interface The simple operations and administration protocol (SOAP) interface feature provides an interface between the HiPath 8000 and the following management tools: ● Service Management Center (iSMC): The iSMC is a full-featured interface that system administrators use to control all subscriber-related capabilities and features.
system_functions_features.fm System Functions and Features T.38 Fax Support ● Backup and restore activities ● Recent change functions Logging configurations (level, filename, output destination) are controlled by process level through either the GUI, command line interface, or SNMP. Each process in the system generates its own log. The log is formatted as a flat file which can be viewed by using a standard editor and includes the option of being output to the screen or to some other type of viewpoint.
system_functions_features.fm System Functions and Features T.38 Fax Support 18-12 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
alpha_feature_listing.fm Alphabetical Feature Listing A Alphabetical Feature Listing This appendix provides a comprehensive, alphabetical list of HiPath 8000 features, classified by feature type. It includes a cross-reference to assist in easily locating each feature description in this guide.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Application servers— interworking SIP signaling See interworking with application servers. Attendant answering position Business group Section 6.1 on page 6-1 Audible ringing on rollover lines Keyset telephone user Section 3.1 on page 3-2 Audit mechanisms SIP signaling Section 16.1 on page 16-1 Audits, internal System functions and features See internal audits.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Business group web portal Business group Section 6.10 on page 6-9 Call admission control Call admission control features Section 10.1 on page 10-1 Call completion on busy subscriber Other user features See automatic callback. Call detail record generation CDR Section 13.2 on page 13-1 Call forwarding—no reply HiPath 8000-based station call forwarding See call forwarding—don’t answer (CFDA).
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Call forwarding, station— HiPath 8000-based station call time-of-day forwarding Section 4.11 on page 4-11 Call forwarding, station— HiPath 8000-based station call voice mail forwarding Section 4.12 on page 4-13 Call gapping code controls Serviceability Section 15.4 on page 15-4 Call pickup—group Other group features Section 7.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Click to answer Other user features Section 5.10 on page 5-10 Conference, stationcontrolled Other user features Section 5.11 on page 5-11 Convedia CMS 1000 media server support System functions and features See media server support. Courtesy call HiPath 8000-based station call forwarding See call forwarding— courtesy call. CSTA protocol interface CSTA support Section 17.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Endpoint control licensing Serviceability Section 15.7 on page 15-5 Enhanced call forwarding HiPath 8000-based station call (ECF) forwarding See call forwarding—timeof-day. Event logging Security Section 14.5 on page 14-4 Extension dialing Business group Section 6.14 on page 6-11 Feature status notification Other user features Section 5.13 on page 5-13 File transfer security Security Section 14.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Hunt group—queuing Other group features Section 7.8 on page 7-8 Hunt group—stop hunt Other group features Section 7.9 on page 7-9 Hunt group—traffic measurements Other group features Section 7.10 on page 7-9 Hypertext transfer protocol over SSL Security Section 14.7 on page 14-7 In-use indication Keyset telephone user See visual indicators for line and feature key status.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Interworking with unified SIP signaling messaging systems Section 16.9 on page 16-7 Interworking with voice SIP signaling conferencing applications Section 16.10 on page 16-7 Interworking with voice mail systems SIP signaling Section 16.11 on page 16-8 IP Unity media server support System functions and features See media server support. IPsec baseline Security Section 14.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Multiline origination and transfer Keyset telephone user Section 3.10 on page 3-13 Multiline preference Keyset telephone user Section 3.11 on page 3-14 Multiple language announcements Business group Section 6.16 on page 6-12 Multiple time zone support CSTA support Section 17.8 on page 17-5 Music on hold—HiPath 8000-based Other user features Section 5.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Phantom lines Keyset telephone user Section 3.12 on page 3-15 Pickup group Other group features See call pickup—group. Prefix digit translation Routing and translation Section 9.7.5 on page 9-5 PRI supported and unsupported features PRI Section 11.4 on page 11-2 PRI trunking PRI Section 11.5 on page 11-2 Process debug tool Serviceability Section 15.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Routing—alternate with overflow among route types Routing and translation See alternate routing with overflow among route types. Routing—bearer capability Routing and translation See bearer capability routing. Routing—origindependent Routing and translation See origin-dependent routing. Routing—time-of-day Routing and translation See time-of-day routing.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description SIP REFER method support SIP signaling Section 16.16 on page 16-10 SIP session management— concurrent sessions SIP signaling Section 16.17 on page 16-10 SIP UA registration renewal during WAN outage SIP signaling Section 16.18 on page 16-11 SIP UPDATE method support SIP signaling Section 16.19 on page 16-11 SOAP interface System functions and features Section 18.
alpha_feature_listing.fm Alphabetical Feature Listing Feature Feature Type Description Time-of-day call forwarding HiPath 8000-based station call forwarding See call forwarding—timeof-day. Time-of-day routing Routing and translation Section 9.8.7 on page 9-7 TLS support Security Section 14.17 on page 14-12 Toll and call restrictions Other user features Section 5.27 on page 5-31 Traffic measurements— business group Business group See business group traffic measurements.
alpha_feature_listing.fm Alphabetical Feature Listing A-14 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
feature_access_codes.fm Feature Access Codes B Feature Access Codes Users can invoke features that reside in the HiPath 8000 without special feature keys by entering feature access codes. Feature access codes are sometimes known as vertical service codes. > Features that reside in the SIP endpoint are not invoked with feature access codes. Refer to the applicable user manual for more information. Table B-1 lists the default feature access codes.
feature_access_codes.fm Feature Access Codes Feature Access Code Selective call acceptance *27 (activate) *28 (deactivate) Selective call rejection *60 (activate) *80 (deactivate) Station speed calling, HiPath 8000-based—one-digit list programming *74 Station speed calling, HiPath 8000-based—two-digit list programming *75 Trace, customer-originated *57 Table B-1 B-2 Default Feature Access Codes (Sheet 2 of 2) A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
supported_sip_methods.fm Supported SIP Methods C > Supported SIP Methods Several feature descriptions in this guide make references to SIP methods. This appendix provide a brief description of each. Contact your Siemens representative for sources of detailed information about SIP, its operation, and its uses. Table C-1 lists and describes the SIP methods the HiPath 8000 supports. Method Description ACK This method indicates successful session setup. It is sent by the node that initiates a call.
supported_sip_methods.fm Supported SIP Methods C-2 A31003-H8022-F100-2-7618, October 2006 HiPath 8000 V2.
5848IX.
5848IX.fm Index C call admission control CAC groups 10-2 CAC policies 10-2 CAC rerouting 10-4 call denial 10-5 definition 10-1 link failures, handling of 10-5 call completion on busy subscriber/no reply (CCBS/NR) See automatic callback.
5848IX.
5848IX.
5848IX.
5848IX.fm Index See also networking.
5848IX.
5848IX.
5848IX.
5848IX.
www.siemens.com/hipath The information provided in this document contains merely general descriptions or characteristics of performance which in case of actual use do not always apply as described or which may change as a result of further development of the products. An obligation to provide the respective characteristics shall only exist if expressly agreed in the terms of contract. The trademarks used are owned by Siemens Enterprise Communications GmbH & Co. KG or their respective owners.
