TIM15001 R2.0 VU TEN I1 Student Guide

7/25/2019 TIM15001 R2.0 VU TEN I1 Student Guide

1/398


2/398


3/398


4/398


5/398


6/398


7/398


8/398


9/398


10/398


11/398


12/398


13/398


14/398


15/398


16/398


17/398


18/398


19/398


20/398


21/398


22/398


23/398


24/398


25/398


26/398


27/398


28/398


29/398


30/398


31/398


32/398


33/398


34/398


35/398


36/398


37/398


38/398


39/398


40/398


41/398


42/398


43/398


44/398


45/398


46/398


47/398


48/398


49/398


50/398


51/398


52/398


53/398


54/398


55/398


56/398


57/398


58/398


59/398


60/398


61/398


62/398


63/398


64/398


65/398


66/398


67/398


68/398


69/398


70/398


71/398


72/398


73/398


74/398


75/398


76/398


77/398


78/398


79/398


80/398


81/398


82/398


83/398


84/398


85/398


86/398


87/398


88/398


89/398


90/398


91/398


92/398


93/398


94/398


95/398


96/398


97/398


98/398


99/398


100/398


101/398


102/398


103/398


104/398


105/398


106/398


107/398


108/398


109/398

Page 109

All Rights Reserved Alcatel-Lucent 2007 Edition

All Rights Reserved Alcatel-Lucent 2010

TIM150015060 ICS 2.0 Overview109

Applications Overview - 5450 ISCHSS resolution - SLF/HSS Processing a Query in Distributed IMS

Co-located SLF/HSS (on the right) :1. Query to SLF.2. SLF performs a look-up on the public

identity and determines that therequest is for the co-located HSS;SLF forwards request to co-locatedHSS.

3. Co-located HSS processes requestand returns a response.

HSS not co-located (on the left) :4. Query to SLF.5. SLF performs a look-up on the

public identity and determines thatthe request is for an non co-locatedHSS; SLF returns redirect responsewith the address of the HSS.

6. Re-attempt query to that HSS7. Non co-located HSS processes

request and returns a response.

I/S-CSCF

SLF

1

2

HSS

1440 USDS/8650 SDM .

34

HSS

1440 USDS8650 SDM .

567

Note: 5060 ICS operates in a similar way,but only supports integrated SLF in iHSS .

SLF currently not supported. 5060 ICS will support an integrated SLF (iSLF) in Release 1.2.1 & Later.TIM15001, refer to Module 6 Char ging. )


110/398

Page 110




Applications Overview - 5450 ISCBorder Functions - Heartbeat between P-CSCF and S-CSCF

The P-CSCF provides a heartbeat mechanism to keep track of the status of itsassociated S-CSCFs and to take recovery action if an S-CSCF is unreachable.

The heartbeat mechanism detects connectivity between P-CSCF and S-CSCF:May be a direct route between P-CSCF and S-CSCFMay be a route through IBCFs; for example, PCSCF IBCF1 IBCF2 S-CSCF in thecase of roamers with their P-CSCF residing in a visited network

If the S-CSCF heartbeat is enabled, a P-CSCF:Dynamically maintains a list of target S-CSCFs for each successful UE registration.Sends a heartbeat request (SIP OPTIONS message) to target S-CSCFs at regular intervals.Treats a 408 Request Timeout or a 503 Service Unavailable response as a failure.

An S-CSCF is considered unreachable after N consecutive heartbeat failures.The P-CSCF will treat this as if the S-CSCF had lost its registry ( out-of-sync ).The P-CSCF, upon detection of loss of S-CSCF registry, will quickly locate the affectedUEs and take immediate recovery actions to trigger an impacted UE to re-register withthe network.

LSM R18.0, FID 10919.195/WI 76.981: Heartbeat between border element P-CSCF and core element S-CSCFThis feature provides a heartbeat mechanism using SIP OPTIONS for P-CSCF to keep track S-CSCF status. The

list of target S-CSCFs is built dynamically at the P-CSCF upon successful UE registration (200 OK response toREGISTER message). The S-CSCF status, based on its response to heartbeat requests, is maintained at the P-CSCF. If a target SCSCF is determined to have lost its registry or is suspected to have lost its registry, the P-CSCF will take immediate recovery actions (when possible) that aim to trigger an impacted UE to re-registerwith the same or a new S-CSCF. This feature is controlled (enabled/disabled) by a provision flag in P-CSCFprofile.

The S-CSCF status is reachable (initial ) or unreachable.Any other response than 408 Request Timeout or 503 Service Unavailable is considered as a success response

for this feature.This feature is most useful when the P-CSCF and the S-CSCF are not co-resident on the same IMS server. The

heartbeat between P-CSCF and S-CSCF is not applicable to the 5060 ICS configuration because the P-CSCFand S-CSCF are located on the same IMS Server.

Only one of the recovery mechanisms (some of which are mutually exclusive) should be used and in followingorder (whichever one is applicable):

a) Either one of the Keep Alive mechanisms (SRD-CSCF-3108 or 3109);b) Registration suppression;c) Send NOTIFY to UE.The P-CSCF needs to spread "marking" all UEs as "impacted" over some time period, for example, 10 minutes,

to avoid potential registration storm from impacted UE (especially for UEs that have keep-alive enabled.)

As of ICS 1.2.1 also Heartbeat between iAGCF and S-CSCF. (very similar mechanism with minor differenceconcerning recovery procedure


111/398

Page 111




Applications Overview5450 ISCUser Profile Revisited


112/398

Page 112




Applications Overview - 5450 ISCUser Profile Overview

Associated with an IMS subscription.Assigned by the network operator.

Provisioned at the HSS.Contains at least:One Private User Identity (PRID)A single service profile of one or more Public User Identities (PUID)

Supports Implicit Registration Set (IRS).Supports preference-based routing.In 3GPP Rel-6 & later:

Multiple PRIDs per IMS subscriptionShared PUIDsSupport of forking.

The IMS subscription, its associated PRIDs and PUIDs need to be provisioned at HSS.

At each UE, a PRID (=IMPI stored on the ISIM) and at least one PUID need to be provisioned and securely stored.

A PRID is typically associated with a User Equipment (UE) or a device. (For instance, the PRID needs to be securely stored in ISIMapplication, if ISIM is used for access IMS.) The term PRID, device and UE are often used interchangeably.

A service profile is a collection of user-specific information that is permanently stored in the HSS, which is transferred from the HSS to anassigned S-CSCF on user registration or on a terminating initial request for an unregistered user. It consists of three parts:

Public Identification (one or more PUIDs)

Core Network Service Authorization

Initial Filter Criteria.

Multiple service profiles allows different treatment for different public user identities

One or more PUIDs can be assigned by the home network operator to an IMS subscriber and PUIDs are used for requestingcommunications to other users. At least one public user identity needs to be securely stored or provisioned at each UE.

A shared PUID may be registered at a given time from multiple UEs that use different PRIDs and with different contact addresses.However, one PUID can register only one contact per UE.

Preference-based routing means different registrations can be differentiated by means of the private user identity and the used IP address.Caller preference allows a caller to indicate the preferences to the IMS core how he/she wishes the call to be handled. Caller preferenceconsists of caller feature preference and caller request preference. Currently only feature preference is supported (e.g., a call should orshould not fork or a call should or should not be directed to a video capable device).

In 3GPP Rel-6:

Sequential forking means that different items of UE are contacted one by one: for example, the S-CSCF first sends the request to UE #2and, if Joe fails to respond, within a certain time limit the S-CSCF then tries to reach Joe through UE #1.

Parallel forking means that different items of UE are contacted at the same time: for example, when two items of UE are ringing, Joecan decide which UE to use for the incoming session; however, in the end the session can only be connected to a single item of UE.


113/398

Page 113




Applications Overview - 5450 ISCMultiple PRIDs and Shared PUIDs

The figure shows an example of the relationship of Multiple PRIDs and shared PUIDs. In this example, PUID 3 and PUID 4are shared PUIDs by all PRIDs in the same subscription.

It is possible that different UEs of the same IMS subscription may register its PUIDs through the same P-CSCF or differentP-CSCFs.


114/398

Page 114




Applications Overview - 5450 ISCShared PUIDs

One or more PUID(s) can be shared across the multiple PRIDs within the sameIMS subscription.A shared PUID can be registered at a given time from multiple UEs that usedifferent PRIDs and with different contact addresses.


115/398

Page 115




Applications Overview - 5450 ISCServing-CSCF Service Profile Overview

A service profile consists of:

Zero, one, or more initial Filter Criteria (iFC):Zero or one Trigger Point:Boolean expressions of groups of Service Point Triggers (SPTs)One application server to be contacted if Trigger Point is met

Zero, one, or more shared iFC (SiFC) sets:One or more iFCs, locally administered and stored at the S-CSCF


116/398

Page 116




Applications Overview - 5450 ISCUser Profile Information Example

An example of a user profile as stored in the S-CSCF:

[email protected]

sip:[email protected]

Private user ID

1 10 Public user IDs

As a result of this feature the S-CSCF has the capability to evaluate a set of Filter Criteria to invoke theApplication Servers based on the information associated with each Filter Criteria. A newProfilePartIndicator attribute is provided in the subscriber profile by the HSS towards the S-CSCF:

Possible values REGISTERED and UNREGISTERED, indicating if the iFC is a part of the registered orunregistered user profile. If ProfilePartIndicator is missing from the iFC, the iFC is considered to be relevantto both the registered and unregistered parts of the user profile, i.e. belongs to the common part of theuser profile.

Additional information:3GPP: IP Multimedia (IM) Subsystem Cx and Dx interfaces;

Signalling flows and message contents(3GPP TS 29.228 version 5.6.0 Release 5)IMPI = IMS Private User IdentityIMPU = IMS Public User Identity


117/398

Page 117




Applications Overview - 5450 ISCUser Profile Information Example (continued)

0

0

0 0 SUBSCRIBE

1 0 From joe

First trigger point

AND within groups, ORbetween groups

When the SIP Methodcontains SUBSCRIBE

The SIP FromHeader fielddoes not contain joe

and

Additional information:The "first trigger point" is first because

of the priority value (lowest numeric value => highest priority)

not because it is the first in order of appearance.

See 3GPP29.228 or 3GPP2 X.S0013-00500 V2.0 appendix B and C.


118/398

Page 118




Applications Overview - 5450 ISCUser Profile Information Example (continues)

sip:[email protected]

0

Then contact this AS

If not successful incontacting AS, thencontinue


119/398

Page 119




Applications Overview - 5450 ISCService Point Triggers

The Service Point Triggers (SPTs) define the filters that the S-CSCF checks:

Request URISIP methodSIP header, with attribute:

HeaderPresence or absence of any SIP headerContentValue of the SIP header (if required)

Session Case, indicating whether the filter should be used by the S-CSCFhandling:

OriginatingTerminating for a registered end userTerminating for an unregistered end user

Additional information:"Session Case" is the "Direction of the SIP request" (originating, terminating registered, or terminating

unregistered), according to 3GPP2 X.S0013-005-0 v2.0. and 3GPP TS 29.228.

Option to apply regular expression matching to SIP headers for filter criteriaBased on configuration flag, allows for regular expressions to be used for determining a match on the SIP

headers themselves in SPT (current implementation applies regular expression matching on the content ofthe SIP header, but not the header). This allows for checking content specified in a single SPT againstmultiple SIP headers.


120/398

Page 120




Applications Overview - 5450 ISCShared iFC Set

A shared initial Filter Criteria (SiFC) set is a subset of iFCs that may beshared by several service profiles.

How is it used?

In the SAA message, the HSS downloads unique identifiers of SiFC setsto the S-CSCF.The S-CSCF maps the downloaded identifiers onto the SiFC sets that arestored in a locally administered database.If SiFC is not enabled on the S-CSCF, the HSS downloads the iFCs of therequired set explicitly.

This Feature is to provide the Shared Initial Filter Criteria (SiFC) as per 3GPP Release 6 specifications toreduce the memory needs on S-CSCF and Cx link capacity.

Basically, this is an HSS capability; if the HSS does not support SiFC sets, no special default behaviour isrequired for the S-CSCF.

Additional information:Note there is a potential inconsistency issue with the two separate local databases in the HSS and the S-CSCF that contain the filter criteria information.

To support SiFC, the network operator needs to provision SiFC sets, iFCs on both HSS and S-CSCF and isresponsible for data consistence. Such provisioning is actually beyond the scope of this course, but somehigh-level information included here:

Refer to QDI # 29856:In order to keep data consistent, e5450 ISC is used to provision SiFC related data to HSS and S-CSCF. When

configuring, e5450 ISC sends an XML-formatted config file to OMC-CN and then it is passed to the CNFGserver via the MI server (using SSH port forwarding function).

In S-CSCF, there is a flag to indicate if SiFC feature is enabled. If this capability is supported by both HSS andS-CSCF and SiFC set ID(s) is included in SAA or PPR message, S-CSCF will explode the SiFC set(s) into normaliFCs, these iFCs are stored with explicit downloaded iFCs (if there are any), so the existing GSP (GlobalService Profile, IMR 825408) mechani5450 ISC can be used without change.

The following FS GUI provisioning is required: In NGSS Parameters/Timers , select the Enable checkbox for theShared Initial Filter Criteria parameter. (default Disable )


121/398

Page 121




Applications Overview5450 ISCiAGCF


122/398

Page 122




Applications Overview 5450 ISCiAGCF - Overview

The Access Gateway Control Function (AGCF) extends the reach of the IMSnetwork to include analog terminals being served by Access Gateways(AGWs).

The Access Gateway Control Function (AGCF) is defined by the TISPANstandards.

In terms of the TISPAN architecture for an IMS-based PSTN/ISDN Emulation Subsystem (PES) (ETSI TS 182 012),the AGCFs role is analogous to that of a SIP-based Voice over IP Gateway (VGW) since it appears as UE fromthe perspective of the IMS Core Network (CN). However, iAGCF interfaces with H.248 gateways (ISAM) andits operation does not fully comply with TISPAN PES specifications for VGW operation; e.g., TISPANsapproach for using SIP to implement hookflash-based services is not supported.


123/398

Page 123




Applications Overview 5450 ISCiAGCF - Introduction

Alcatel-Lucent offers the AGCFcombined with Call and Session ControlFunctions (CSCF). This AGCF is calledthe internal AGCF (iAGCF).

PSTN endpoints are connected to theIMS through Access Gateways.

Access Gateways are controlled by theiAGCF through H.248/Megaco signaling.

PSTN

H.248/Megaco


124/398

Page 124




Applications Overview 5450 ISCiAGCF - Access Gateways

An AGW located at the subscriberresidence is called a ResidentialGateway (RGW). The RGW supportsa limited number of endpoints.

The AGW located at the premises ofthe network provider supports ahuge number of endpoints. Anexample of is the Alcatel-Lucent7302 ISAM-V.

ISAM-V: Intelligent Service AccessGateway Manager with Voicepackage.

PSTN


125/398

Page 125




Applications Overview 5450 ISCiAGCF - AGW Initialization

When the AGW initializes it contactsthe iAGCF. After the initialization iscomplete the endpoints are activeand can be used for call processing.

PSTN


126/398

Page 126




Applications Overview 5450 ISCiAGCF - Functions and Redundancy

Main functions of the iAGCF:On behalf of the AGW perform aregistration with the Serving CSCFCall control for AGW endpoints.Call control makes use of asubscriber databaseAGW control

The iAGCF uses redundant hardware.The iAGCF can be combined withother services on the samehardware.

PSTN


127/398

Page 127




Applications Overview 5450 ISCiAGCF CSCF connectivity

For the endpoints on the AGW theiAGCF acts as a SIP User Agent (SIP UA).

The iAGCF appears as a P-CSCF to theI-CSCF and S-CSCF.

5420 CTS

PSTN

SIP UA


128/398

Page 128




Applications Overview 5450 ISCiAGCF - Subscriber Database

5420 CTSFSDB

PSTN

The iAGCF uses a subscriber databasecontaining:Private User Identity (PRID)Public User Identity (PUID)Data required for endpoint features(e.g. hotline)Endpoint identity:

Gateway identityIdentity of the port on the gateway

The iAGCF database is integrated withthe Feature Server Database (FSDB).

The iAGCF has a local copy of theiAGCF subscriber data. This data isreceived from the FSDB.

The subscriber data required by the iAGCF is integrated into the existing 5420 CTS Feature Server Database(FSDB) on a diskfull ATCA blade.


129/398

Page 129




Applications Overview 5450 ISCiAGCF - Class 5 Services

The 5420 CTS provides Class 5 servicesfor the iAGCF subscribers.

5420 CTS

TISPAN defines two coupling methods:Tight Coupling: the application server provides the majority of the Class 5 services. Most of the services aretransparent to the AGCFLoose Coupling: Next to the application server the AGCF provides part of the Class 5 services.

The current release of the iAGCF supports Tight Coupling only.


130/398

Page 130




Applications Overview 5450 ISCiAGCF - Registration

The iAGCF uses bulk registration to register all endpoints of an AGW withthe IMS core.

Bulk registration is an Alcatel-Lucent proprietary method.

With Bulk Registration the iAGCF sends one SIP registration message for the entire AGW.


131/398

Page 131




Applications Overview 5450 ISCiAGCF - Call Origination Scenario

1. A subscriber dials a telephonenumber

2. The AGW forwards the dialed digitsto the AGCF

3. The AGCF uses the local subscriberdatabase to compose a SIP INVITEmessage on behalf of the originatingsubscriber

4. The AGCF sends the SIP INVITE to S-CSCF

5. The request is routed to theapplication server (CTS) found inthe subscriber profile for applyingoriginating services

6. The S-CSCF sends the SIP INVITE tothe I-CSCF of the terminating party(or BGCF in case of TDM termination)

A bearer path (RTP stream) is setup from the AGW.

1

4

6

5

2

3

5420 CTS

A bearer path is setup from the AGW for the RTP stream


132/398

Page 132




Applications Overview 5450 ISCiAGCF - Call Termination Scenario

1. The I-CSCF receives a SIP INVITE2. The I-CSCF retrieves the address of

the S-CSCF from the HSS3. The request is forwarded to the S-

CSCF4. The request is routed to the

application server (CTS) found inthe subscriber profile for applyingterminating services

5. The request is forwarded to theAGCF

6. The AGCF consults the localsubscriber database for the AGW

and endpoint information7. The AGCF controls the AGW fortermination of the call

A bearer path is setup to the AGW forthe RTP stream

1

6

5

23

6

4

5420 CTS

1


133/398

Page 133




Applications Overview 5450 ISCiAGCF - Knowledge Check

Please answer the following question:

What functions are performed by the iAGCF?(More than one answer may be correct.)

A. Registers the AGWs with the S-CSCFB. Basic call handlingC. Contact the P-CSCF for outgoing callsD. Process originating calls from endpointsE. Process terminating calls to endpoints


134/398

Page 134




Applications Overview 5450 ISCiAGCF - Knowledge Check

Please answer the following question:

The iAGCF provides all Class 5 services.This statement is:

A. TrueB. False.


135/398

Page 135




Applications Overview5420 CTS


136/398

Page 136




Blank Page

This page is intentionally left blank


137/398

Page 137




Applications Overview5420 CTSFunctionality


138/398

Page 138




Applications Overview 5420 CTSThe 5420 CTS in the IMS Architecture

The 5420 CTS is a SIP applicationserver that functions as a TelephonyApplication Server (TAS) providing:

Number normalizationDigit manipulationCall-processing logic (tight coupling)Service logic to apply broadcategories of services to the endusers:

Residential supplementary servicesBusiness supplementary servicesRegulatory servicesWireless servicesNetwork servicesAdministrative servicesBilling services

Web portal services (optional)

The 5420 CTS provides supplementary services for subscribers using the following endpoints:

SIP phone, which includes both hardphones and softphones

POTS phones attached to for instance an Integrated Access Device (IAD) or AnyMedia LAG (and in the futurethe Alcatel-Lucent Compact Switch configured as a Line Access gateway (LAG)).

Digit manipulation involves number normalization (into E.164 format) and number conversion (translation), suchas E911, which is used for Translations during call-processing and routing.


139/398

Page 139




Applications Overview 5420 CTSComponents

5420 CTS

Addi tional information:The 5420 CTS is an Alcatel-Lucent Telephony Application S erver that provides:SIP Back-to-Back User Agent capabilities

Call control: basic telephony capabilities, such as maintaining the half-call view, digit analysis, numbernormalization (E.164)

Supplementary services provided by two separate TAS components (will be discussed later in this lesson; seeFlashable and Non-flashable endpoints )

Storage of subscriber data in the feature server database: subscriber party information and supplementaryservices (features) information.

Furthermore, when subscribers are provisioned, provisioning data is stored in the HSS and the Lucent

Communication Manager web portal.

The 5420 CTS also controls the media server, because most supplementary services require announcementsand/or tones to be played. The Media S erver also provides conferencing service.

Finally, the 5420 CTS generates charging information (Diameter ACR messages) to be used for AccountingManagement.


140/398

Page 140




Applications Overview 5420 CTSBasic Functions Session Origination

Functions performed by the 5420 CTSduring session origination:

1. Receive an INVITE message from theS-CSCF with a private tag indicatingan origination

2. Query the subscriber database toobtain the data of the calling party

3. Apply the appropriate originatingservices and/or perform numbernormalization

4. Send an INVITE back to the S-CSCFwith the same private tag

5. When the transaction is completed,send charging data

5420 CTS

1 4

2

3


141/398

Page 141




Applications Overview 5420 CTSBasic Functions Session Termination

Functions performed by the 5420 CTSduring session termination:

1. Receive an INVITE message from theS-CSCF with a private tag indicatinga termination

2. Query the subscriber database toobtain the data of the called party

3. Verify the terminating UE isregistered and check UE state

4. Apply the appropriate terminatingservices

5. Send an INVITE back to the S-CSCFwith the same private tag

6. When the transaction is completed,send charging data

5420 CTS

1 5

2

3 4

Addi tional information:Check the state of the terminating UE: for example to determine if busy or idle.

Note that the terminating services depend on the dialed number!


142/398

Page 142




Applications Overview 5420 CTSMedia Services

The 5420 CTS requires a MediaServer (MS) to:

Play a specific tonePlay a simple (specific recorded) orvariable announcementPrompt & collect:

Keypad inputInteractive Voice Response

Provide conference services

An MS acts as a combined MediaResource Function Controller(MRFC) / Media Resource FunctionProcessor (MRFP).

If custom announcements and/or tones are to be used, they should have the following format:

The file name must end in .wav, and use .wav formatting as described next.

The encoding format should be g.711 mu-law (or A-law). Use the same encoding format as used by existingsystem announcements (which are mu-law as stored on LED, but for sites that have converted systemannouncements to A-law, then custom announcements for those sites should also use A-law).

The samples should be 8-bits per sample, 8000 samples per second, single channel. This results in file sizes ofapproximately 8K for each second of announcement duration.


143/398

Page 143




Applications Overview 5420 CTSTreatment, Tones and Announcements

When service processing performed by the 5420 CTS determines that atreatment must be applied (treatment event), the 5420 CTS:

Selects a media server to use from a provisioned list of Media ResourceFunctions that is stored in the configuration databaseSends a SIP INVITE message to that media server; the message includesthe URL of the announcement file(s) and/or tone file(s) to play, basedon the treatment ID

Audio files storage depends on media server requirements:

5900 MRF: the audio files must be downloaded and stored locally

AudioCodes: the audio files are stored on the 5400 LCP (which providesan HTTP web server to transfer the sound files)

Provisioning determines whether the 5420 CTS constructs the request URIto play the file locally or from the MI service.

Media server provisioning in FS GUI: IMS-> Parameters/Timers->5420 CTS->Media Parameters

For AudioCodes, the 5420 CTS stores the audio files in the /tftpboot/annc/eng_us directory on the MI service;the provisionable eng_us part is the default locale. Locale directories are used to support multiplelanguages and country variants The play parameter consists of Play=http: ///tft pboot/annc/eng_us/

For eMRS, file server parameter is set to MRF and Play=fil e://

Addi tional information:

The Announcement Tool that runs on the MI service can be used to download a copy of the audio files:

Can download from the Alcatel-Lucent Electronic Distribution/Delivery (LED) site (3G-MSC only?)

Can download from the On-Line Customer Support (OLCS) site: www.support.Alcatel-Lucent.com

Can also be used to send a copy of the audio files from the MI service to the eMRS.

A service provider may want to customize announcements, for example to:

Have their own actor record the announcements

Change the wording of the announcements

Record in a different language (the announcements files should be stored in a different local directory fromeng_us)

The customized announcements files can be downloaded using the Announcement Tool as well.


144/398

Page 144




Applications Overview 5420 CTSMedia Server Interoperability

Up to eight media servers in distributed pooled mode:

Round-robin media server selectionMore than one 5420 CTS can access a media serverEach 5420 CTS can access any media server

The 5420 CTS acts as a SIP user agent client, opening SIP dialogs inconjunction with:

NETANN (tone and simple announcement playback; conferencing)MSCML (multiple and variable announcement playback; prompt &collect)

Announcement Tool that runs on the 5400 LCP can be used to downloadand distribute the initial audio files to media servers.

Messages flowing through the S-CSCF are prescribed by the IMS architecture. However, only the direct signalingconnection from the 5420 CTS to the MS is supported and the 5420 CTS does not support a dialog that isinitiated by the media server.

The 5420 CTS expects that when a 200 OK from the media server is received after having processed a incomingSIP INVITE, this means that it process the request without encountering any errors in either parsing themessage received or allocating the necessary resource to honor the request.

Addi tional information:If the first selection attempt fails for any reason other than any retransmission time out, the 5420 CTS shall send

same request to the next MRF in the list. A call that required multiple dialogs (e.g. conference call) with MRF shall use the same MRF for all dialogs. After

setup a call leg successfully with one MRF, it shall never switch to another MRF although a later call leg mayfail from the selected MRF.

There are two types of announcements to be supported: simple announcements (single audio file) and complexannouncement (multiple audio files or variable announcements ).

The NETANN protocol will be used for:Request to play simple announcements (within the SIP request URI for the simple announcementRequest to play tonesRequest to perform conferences.

The MSCML protocol will be used for:Request to play the complex announcements (extensions-payload-in SIP INFO messages)Prompt & collect.


145/398

Page 145




Applications Overview 5420 CTSThe Web Portal

The 5420 PCM (PersonalCommunication Manager) can beassigned as a web portal to provideconverged services for subscribers:

Offers an interface (GUI) to enableservices such as click-to-dial, click-to-conference, etc.Relays the call-control requests tothe 5420 CTS for processingReceives status information from the5420 CTS about calls to/fromdirectory numbers

When provisioning a subscriber, data is also stored in the database of the Lucent CM.

LCM can interact with voicemail systems:

Display Message Waiting Status

Allow user to retrieve voicemail messages using their computer



146/398

Page 146




Applications Overview 5420 CTSDigit Translation

Addi tional information:The DPE data includes:Digit tables (new tables specifically designated to the 5420 CTS have been defined):

Feature codes and carrier dial -around codes

Operator assistance codes

Emergency services routing number

Direct dialed call translations; a digit table that is configured with the appropriate digit deletion and prefixingrules to convert any valid number dialed by this subscriber into E.164 number format

Multiple dialing plan tables (the table ID is needed because the switch can support multiple dialing plans)

Per -subscriber dialing plan assignment.

One result of the DPE is to determine the call type, such as Valid local number, National number, Internationalnumber, Directory assistance, Toll-free number, and Emergency number.

The Location Based Routing service (distributed configuration only) This allows a special code to be dialedthat uses the knowledge of the subscribers location in order to translate the special code to the appropriatelocal number for that physical location.

Example: A subscriber enters *PIZZA on their telephone keypad. The Location Based Routing service interpretsthis special code based on entries in the Special Code Table as provisioned by the system administrator. Thespecial code is routed to the appropriate local number based on a provisioned geographic identifier, such as zipcode.


147/398

Page 147


All RightsR eserved Alcatel-Lucent 2010


Applications Overview 5420 CTSNon-Flashable Endpoints and Flashable Endpoints

Only one bearer path towards an endpointmay exist

Set Multiple bearer paths towards anendpoint may exist

Only one INVITE dialog can exist between anendpoint and the 5420 CTS

Two or more INVITE dialogs can existbetween an endpoint and the 5420 CTS

Hookflash events are reported to the 5420CTS with INFO message

A hookflash event initiates a new INVITEdialog

Simple endpoint or advanced endpoint(provisioned as simple endpoint

Advanced endpoint

The other services are applied by the S-TAScomponent of the 5420 CTS

The other services are applied by the S-TAS component of the 5420 CTS

Services that are signaled by a hookflash areapplied by the D-TAS component of the 5420CTS

Services that are signaled by a hookflashare applied by the endpoint

Flashable endpointsNon-flashable endpoints

Addi ti onal i nformat ion:Non-flashable endpoints are capable of providing multiple-call services themselves.The 5420 CTS is able to operate with endpoints that provide local support of multiple calls as well as endpoints

that do not. However, some potential 5420 CTS customers have dictated that simpl e e ndpoints be used forthe majority of (if not all) subscribers, where all customer-dialed flash events are processed at the networklevel. Therefore, the advanced endpoints are provisioned as simple endpoints.

As far as service behavior is concerned, if it is NOT a flashable endpoint, then 3-way call, call hold, and callwaiting are done in the endpoint, not by the 5420 CTS. The exception to this is that even advanced SIPendpoints (not flashable) can use the web portal for click-to-conference and then it is done by the 5420 CTS.For flashable endpoints, call hold, call transfer, 3-way call, and call waiting appear to work much like ananalog phone, even for a flashable SIP phone.

For more information, refer to QDI # 27720 (5420 CTS requirements), Section 4.5 SIP Endpoints and QDI #27645 (NGFS Software Architecture), Page 61-71.

Flashable endpoints are endpoints that require D-TAS support in order to provide all services, besides thefunctions of the S-TAS; non-flashable endpoints endpoints do not require D-TAS support, because thoseendpoints are capable of providing certain services (such as multiple-call services) themselves.

The 5420 CTS is able to operate with endpoints that support local support of multiple calls as well as endpointsthat do not. However, some potential 5420 CTS customers have dictated that simple endpoints be used forthe majority of (if not all) subscribers, where all customer-dialed hookflash events are processed at thenetwork level. Therefore, the advanced endpoints are provisioned as simple endpoints.

Flashable endpoints signal hookflash via INFO messages and the 5420 CTS interprets and controls the bearerpath. Another difference is that flashable endpoints will always have a single bearer path to the phone, whileSIP phones not operating as flashable can have multiple bearer paths. As far as service behavior isconcerned, if it is NOT a flashable endpoint, then 3-way call, call hold, and call waiting are done in theendpoint, not by the 5420 CTS. The exception to this is that even advanced SIP endpoints (not flashable)can use the web portal for click-to-conference and then it is done by the 5420 CTS. For flashable endpoints,call hold, call transfer, 3-way call, and call waiting appear to work much like an analog phone, even for aflashable SIP phone.

For more information, refer to QDI # 27720 (5420 CTS requirements), Section 4.5 SIP Endpoints and QDI #27645 (NGFS Software Architecture), Page 61-71.


148/398

Page 148




Applications Overview 5420 CTSS-TAS and D-TAS

Non-flashable endpoints Flashable endpoints

Non flashable endpoints

Note that this is a simplified logical diagram: the endpoints are not physically connected to the 5420 CTS. The purpose is justto show the relationship between the application component (S-TAS = Subscriber TAS and the endpoints.

S-TAS is always in the call (it it the actual TAS)The provisioningd data in the 5420 CTS for such endpoints must be set to indicate that the endpoint is Non-flashable.

The services that are signaled by a hookflash are often referred to as Multiple-call services, such as mid-call and multi-waycall: Call Hold, Call Transfer, 3-Way Call, and Call Waiting.

Flashable endpoints

The S-TAS is always in the call (it it the actual TAS) and the D-TAS (= Device-specific TAS) comes into play in the case offlashable endpoints. In general, a D-TAS provides device-dependent services (such as Call Waiting and Call Hold) whenthe endpoint itself is not capable of handling them or whenever the design of a specific service can be simplified by using

the D-TAS. In addition, a D-TAS can provide device-dependent services for intelligent devices when it is required that thenetwork is responsible for handling those services.

Actually, the distinction is between simple endpoints and advanced endpoints. Simple matches the concept of a SIP IADwith traditional circuit analog POTS phones behind it.. However, many advanced endpoints can operate either way, thusact as either flashable or non-flashable. The provisioningd data in the 5420 CTS for each endpoint must be set to indicatewhether or not the endpoint is Flashable. If an endpoint can operate either way, the Service Provi der must ensurethe value of this field in th e 5420 CTS is consistent with the way the endpoint is configured to operate!


149/398

Page 149




Applications Overview - 5420 CTSSession Origination from Non-Flashable Endpoint

The S-CSCF finds a match on a triggerin the iFC and redirects the INVITEmessage to the S-TAS

The S-TAS applies the originatingservices and/or performs numbernormalization and routes back to theS-CSCF

Assume the S-CSCF finds no match onother iFC triggers; so it is doneredirecting to application serversand forward INVITE message to thenext node

To called partyhome network

Advanced endpo in t(non-flashable)

S-TASD-TAS

5420 CTS

SIP subscribers who use a non-flashable endpoint only require the S-TAS functions

Note that the flow of the arrows reads from left-to-right and that the arrows are in line!

The Initial Filter Criteria that are used depend on the type of registration service profile:

Origination from or termination to SIP subscriber

Termination to a POTS subscriber attached to an IAD or AnyMedia LAG

Origination from or ringback termination to a POTS subscriber attached to an IAD or AnyMedia LAG.

Ask the students how the S-TAS decides the type of services.

Answer: This is based on the private tag that the S-CSCF includes in the INVITE message



150/398

Page 150




Applications Overview 5420 CTSSession Termination to Non-Flashable Endpoint

The S-CSCF finds a match on a triggerin the IFC and redirects the INVITEmessage to the S-TAS

The S-TAS applies the terminatingservices and routes back to the S-CSCF

Assume the S-CSCF finds no match onother IFC triggers; so it is doneredirecting to application serversand forward INVITE message to theP-CSCF

S-TASD-TAS

5420 CTS

From callingparty home

network

Ad vanced endpoin t(non-flashable)

SIP subscribers who use a non-flashable endpoint only require the S-TAS functions.

Note that the flow of the arrows reads from right-to-left and that the arrows are in line!



151/398

Page 151




Applications Overview 5420 CTSSession Origination from Flashable Endpoint

The S-CSCF finds a match on a triggerin the IFC and redirects the INVITEmessage to the D-TAS

The D-TAS applies any multi-callservices and routes to the S-TAS

The S-TAS applies the originatingservices and/or performs numbernormalization, and routes back tothe S-CSCF

Assume the S-CSCF finds no match onother IFC triggers; so it is doneredirecting to application serversand forwards INVITE message to the

next node

S-TASD-TAS

5420 CTS

To called partyhome network

Simple endpoin t(flashable)

Instructor directive:SIP subscribers who use a flashable endpoint require both D-TAS and S-TAS functions.

Note that the flow of the arrows reads from left-to-right and that the arrows are in line!

Note also that there is no separate trigger for the S-TAS. A separate trigger will be an option i n R3.

Of course the POTS phone should be connected through an IAD (not shown for simplicity).



152/398

Page 152




Applications Overview 5420 CTSSession Termination to Flashable Endpoint

The S-CSCF finds a match on a triggerin the IFC and redirects the INVITEmessage to the S-TAS

The S-TAS applies the terminatingservices and/or performs numbernormalization services, and routesto the D-TAS

The D-TAS applies any multi-call androutes back to the S-CSCF

Assume the S-CSCF finds no match onother IFC triggers; so it is doneredirecting to application serversand forwards INVITE message to the

P-CSCF

S-TASD-TAS

5420 CTS

Simple endpoin t(flashable)

From callingparty home

network

SIP subscribers who use a flashable endpoint require both D-TAS and S-TAS functions.

Note that now the S-TAS and the D-TAS are in the session in reverse order.

Of course the POTS phone should be connected through an IAD (not shown for simplicity).



153/398

Page 153




Applications Overview 5420 CTSKnowledge Check

Please answer the following question.

The 5420 CTS plays tones and announcements.This statement is:

A. TrueB. False


154/398

Page 154




Applications Overview 5420 CTSKnowledge Check

Please answer the following question.

Which statements about flashable endpoints are true?

A. Handles multiple-call services internallyB. Can be an advanced endpoint, such as a SIP phoneC. Requires the D-TAS application component of the 5420 CTSD. Reports a hookflash event in a SIP INFO message.


155/398

Page 155




Applications Overview5420 CTSServices


156/398

Page 156




Applications Overview 5420 CTSService Categories

The 5420 CTS services can be divided in the following categories:

Supplementary servicesResidential supplementary servicesBusiness supplementary services

Other ServicesRegulatory servicesWireless servicesNetwork services

Administrative servicesBilling services

Services can be divided in different categories:

Supplementary servicesResidential supplementary servicesBusiness supplementary services

Other servicesRegulatory servicesWireless servicesNetwork services

Administrative servicesBilling services

The first part of this section gives an overview and description of the regulatory, wireless, network,administrative and billing services.

The second part of this section will focus on business and residential supplementary services. It will give anoverview of which supplementary services are available and how they are packaged. Also some examplescenarios of supplementary services are given.

More detailed descriptions of the services can be found in the customer documentation:5420 Converged Telephony Server (CTS) Application User GuidePart I: The Alcatel-Lucent Converged Telephony Server

Chapter 5. Services


157/398

Page 157




Applications Overview 5420 CTSRegulatory Services

Regulatory services include:

Carrier selection and carrier pre-selectionCustomer originated traceEmergency serviceGovernment Emergency Telecommunications Service (GETS)Local number portabilityMalicious call trace/nuisance call traceMulti-Level Precedence end Preemption (MLPP)Selective nomadic blocking

Non-paying subscriber treatmentLocation Number

Carrier selection and carrier pre-selection

Carrier selection is a way for a subscriber who is connected to the access network to choose a carrier for a specific call. For example, itmakes it possible for the subscriber to choose which carrier to use for a particular international destination.The following carrier selection types exist: LATA based carrier selection Digit analysis based carrier selection IN Query based carrier selection.

Customer Originated TraceThe Customer Originated Trace (COT) service is a subscriber-invoked service that allows a customer to trace the number of a calling party.

This is often used to determine the origination of harassing or other nuisance calls. There are two parties involved in a COT: the customer who receives the call and requests the trace the agency (e.g., a law enforcement agency) that receives the output message containing the trace results.

Emergency serviceThe emergency service allows users to initiate a call to the appropriate Public Safety Answering Point (PSAP), typically via a nationwide

uniform number. At the PSAP (orcall center), an emergency operator determines the nature of the emergency and dispatchesassistance or makes contact with another agency as appropriate.The following are examples of nationwide emergency numbers: 911 in the United States 000 in Australia 112 in the European Community 119 in some Asian countries, with special numbers in some countries for police, ambulance or fire.Mobile and Nomadic subscribersThe emergency calling service provided by 5420 CTS is sufficient for fixed users. Fixed users do not move during calls (mobile users) or

between calls (nomadic users). This service provides functionality beyond what is specified in the National Emergency NumberAssociations (NENA) i1 specification. To support nomadic and mobile users, NENA i2 is supported. It provides a separate EmergencyApplication Server (EAS) and appropriate external interfaces which conform to the NENA i2 architecture.

Government Emergency Telecommunications Service (GETS)GETS is a service mainly for the US market which allows authorized government users to gain access to the network during emergency

situations. The user dials an access number to place a GETS call, which causes the call to complete to one of the inter exchangenetworks, where authentication via PIN code and collection of the final routing number are performed. GETS calls are provided withspecial treatment to assure a high probability of completion


158/398

Page 158




Applications Overview 5420 CTSRegulatory Services (continued)

Regulatory services include:

Carrier selection and carrier pre-selectionCustomer originated traceEmergency serviceGovernment Emergency Telecommunications Service (GETS)Local number portabilityMalicious call trace/nuisance call traceMulti-Level Precedence end Preemption (MLPP)Selective nomadic blocking

Non-paying subscriber treatmentLocation Number

Local Number Portability

Local Number Portability (LNP) is not provided directly by the 5420 CTS. Other IMS elements, particularly the MGCF are used to supportLocal Number Portability.

Malicious call trace/nuisance call trace

Malicious call trace/nuisance call trace (NCT) is a public safety service that allows a service provider to identify the origination ortermination of a telephone call. This capability is often used to determine the origination or termination of harassing or other nuisancecalls.

Multi-Level Precedence and Preemption (MLPP)

The Multi-Level Precedence and Preemption MLPP provides prioritized call handling service: Precedence involves assigning a priority level to a call Preemption involves the seizing of resources, which are in use by a call of a lower precedence, by a higher level precedence call in the

absence of idle resources. Users in networks that do not support this service will not be affected by this service.Please not that for this release MLPP is only supported on Alcatel-Lucent CP 1000.

Selective Nomadic Blocking

The Selective Nomadic Blocking service (SNB) provides capabilities that meet a service providers obligation to comply with FederalCommunications Commission (FCC) standards by blocking non-emergency calls for nomadic users. A nomadic user is one who changeslocation between (but not during) calls.

Non-Paying Subscriber Treatment

This service deals with announcements for calls originated by non-paying subscribers. With this service, the Service Provider (SP) is able tokeep non-paying subscriber from originating a call or divert a call. This service does not keep a non-paying subscriber from answering acall. When call origination or call diversion is blocked by this service, the caller hears an announcement.

Location NumberAn optional Location Number may be populated in per-subscriber data. When a Location Number is populated, it will be included in a

P-Access-Network-Info header based on ETSI ES 283 003.


159/398

Page 159




Applications Overview 5420 CTSWireless Services

Wireless services include:

Dual Mode Service/WiFi RoamingHSS Shared subscriber dataFemto Base Station Router Interface (FemtoBSR)

Dual Mode Service/WiFi Roaming

Dual-mode service allows a user with a dual mode (CDMA/WiFi or GSM/WiFi) handset (cell phone) to roam from a: WiFi (ITU Q.802.11) network (hotspot or home) to a mobile phone network, or Mobile phone network to a WiFi network.This service allows: End users to perform handover for an active call Wireless service providers to save air bandwidth and provide better quality of service.Note This functionality is only supported in the distributed configuration.

HSS Shared subscriber dataHSS shared subscriber data allows the 5420 CTS to read and update information held in the ANSI/CDMA USDS and UMTS

HLR to facilitate feature data sharing for services. The subscriber dynamic data for these basic features is kept in syncbetween the 5420 CTS subscriber database and the HSS/HLR. This allows a dual mode CDMA-IMS or UMTS-IMS handset to

behave identically regardless of the access technology.

Femto Base Station Router Interface (FemtoBSR)A Femto Base Station router (FemtoBSR) device is a short-range wireless base station that can be deployed in homes and

other locations, and enables a non-SIP mobile phone to interact with the IMS network.The FemtoBSR acts as a cell tower as far as the mobile phone is concerned. The FemtoBSR will interwork wireless

protocols to SIP protocols. The mobile phones attached to the FemtoBSR are not provisioned in any CTS static data. TheCTS discovers the identity of attached mobile phones as originating and terminating INVITE requests are received. Theassociation of mobile phone to a FemtoBSR call is determined by the To header for terminating INVITE messages, andthe From header for originating INVITE messages.

Although the mobile phones are not provisioned in the CTS, most services will work at the mobile phone level. Forexample, when a terminating INVITE arrives associated with a particular mobile phone the CTS needs to determinewhether there is an existing

call on the FemtoBSR associated with that mobile phone in order to properly apply Call Waiting. The current status ofother mobile phones behind the FemtoBSR is not relevant for purposes of Call Waiting.

The FemtoBSR looks like a simple endpoint to the CTS, defined as a Party ID. The FemtoBSR supports a limited set ofservices including Call Waiting, Flash Originating, N-Way calling, Call transfer, Dialing Plan, and Calling Line Identity


160/398

Page 160




Applications Overview 5420 CTSNetwork Services

Network services include:

Short code translationLocation-based routing

Short Code TranslationThe Short Code Translation (SCT) service allows mobile subscribers to place calls to users of other VoIP

services using a Uniform Resource Locator (URL) address instead of a directory numbers (DN). This is doneby using the address book function of the mobile handset.

Location Based RoutingThe Location Based Routing service allows a special code to be dialed that uses the knowledge of the

subscribers location in order to translate the special code to the appropriate local number for thatphysical location..

Example

A subscriber enters *PIZZAon their telephone keypad. The Location Based Routing service interprets this

special code based on entries in the Special Code Table as provisioned by the system administrator. Thespecial code is routed to the appropriate local number based on a provisioned geographic identifier, such aszip code.

Note Location Based Routing is only supported with the distributed configuration


161/398

Page 161




Applications Overview 5420 CTSAdministrative Services

Administrative services include:

Configurable feature codesAnnouncement locale & multi-lingual announcementsService provider defined CPE profilesWildcard Public IDs

Configurable feature codesThe configurable feature codes service enables providers to configure per-service activation and deactivation

codes. Subscribers use these codes to activate/deactivate supplementary services.

Announcement Locale & Multi-Lingual Announcements5420 CTS supports the specification of up to two announcement locales in global and per-subscriber data. The

locale is used to construct the URL of announcement files.Various assignments are possible, however, the two most typical cases are: A global locale is assigned and is the default for all subscribers (e.g. the predominant local language).

Selected subscribers may be assigned a differentlocale, based on their language preference. A subscriber is assigned two locales, so that all announcements will be given in two languages. A brief

silence is inserted between the two announcements, composed of 0.5 seconds of comfort noise (tone ID21)

Service Provider Defined CPE ProfilesEach 5420 CTS subscriber is associated with a Customer Premise Equipment (CPE) Profile. The profile specifies

certain CPE-specific capabilities and SIP message header contents used to access those capabilities. Alcatel-Lucent provides a set of pre-defined CPE profiles. This section documents all

of the available CPE profile attribute and value settings, along with their behaviors. The service provider mayuse the information provided in the section of the 5420 CTS application user guide to design their own CPEprofiles to meet CPE and network requirements not handled by the ALU pre-defined profiles.

Wildcard Public IDsA Wildcard Public Identifier (PUID) is a short-hand method of designating a range of PUIDs. Wildcard PUIDs are

intended to support registered service for a group of PUIDs such as a registered PBX interface.


162/398

Page 162




Applications Overview 5420 CTSBilling Services

A CTS Charging profile enables the service provider to control thegeneration of billing records.

The following options are available:INVITE DialogSDP in SIP INVITE DialogDial CodesIncomplete CallsInhibit Terminating ACRsCarrier Id Recording FormatTime Granularity (for AOC and Metering)

The settings in the Charging Profile apply to all Party Ids in the 5420 CTS

SDP in SIP INVITE DialogThis option allows the service provider to determine whether SDP information should be included in the ACR

messages. This option also allows the service provider to select how much of the SDP information should beincluded in the ACR messages.

Dial CodesThis option allows a service provider to turn on or turn off the generation of ACR messages when a CTS

supplementary service dial codes is detected.

Incomplete CallsThis option allows a service provider to turn on or turn off the generation of ACR message for incomplete calls.

Inhibit Terminating ACRs

This option allows a service provider to inhibit the transmission of terminating billing records. Terminatingbilling may be inhibited to increase system capacity in those cases where terminating billing records are notneeded.

Carrier Id Recording FormatCertain networks may permit the user to select a carrier for their call, either by pre-subscription or call-by-

call selection. This option allows a service provider to include per-call carrier information in billing records.

R17: The CTS R6.1 Metering will use the following new parameter in the Charging Profile in the Configurationdatabase:

Time Granularity: the supported values are one-second (default ) and one-tenth-second.In additional to adding the Time Granularity parameter, another change of the FSGUI (also OMCP GUI) is to

change the name of ACR Charging Profile into CTS Charging Profile. The reason for the change is that,since release 6.1, CTS come to have charging parameters for CCR instead of ACR (such as the timegranularity scale) to be added to the configuration database. That means CTS needs a common chargingprofile for both ACR and CCR, rather than a charging profile solely for ACR.


163/398

Page 163




Applications Overview 5420 CTSSupplementary Services and Features

The 5420 CTS provides a wide ranges supplementary services forresidential and business subscribers.

In the 5420 supplementary services are often referred to as features.

Supplementary services are combined into so called feature packagesto keep ordering and engineering simple.

A la carte features (or independent) features are features that are notpart of a feature package, but that can be assigned to a subscriberin addition to its feature package

With each 5420 CTS release, additional features are added. To keep the engineering and the ordering of the5420 CTS simple, CTS provides access to features in packages or bundles.

Each 5420 CTS subscriber is assigned a feature package and the service provider has the option to make all ofthe features in the package, or just a subset, available to that subscriber. Different 5420 CTS subscriberscan be assigned different feature packages.

5420 CTS engineering allows the flexibility to support many different feature packages on the same 5420 CTS,however, each individual subscriber cannot be assigned more than one feature package.

As 5420 CTS supports new features in future releases, these new features may be added to existing featurepackages, or new feature packages may be created supporting these new features. When new features areadded to existing feature packages, these features automatically become available for the service providerto assign to subscribers that already have the feature package.

In addition to feature packages, 5420 CTS also supports Ala Carte features. Ala Carte features are featuresthat can be assigned to a subscriber in addition to those available in the subscribers assigned featurepackage. An example of an ala Carte feature is Attendant Console.


164/398

Page 164




Applications Overview 5420 CTSFeature Templates

Feature 1

Feature 2

Feature 9

Feature 3

Feature 4

Feature 5

Feature 7

Feature 6

Feature 8

Feature template 1

Feature template 2

Feature template 3

Subscriber a

Subscriber b

Subscriber c

Subscriber d

Subscriber e

Subscriber f

Subscriber g

Subscriber h

Subscriber iSubscriber j

Feature Package

An operator can create feature templates in order to simplify subscriber feature provisioning.A feature template can hold a number of features from a feature package.In stead of assigning the each feature individually to a subscriber, the operator can simply assign a feature

template to that subsricriber.


165/398

Page 165




Applications Overview5420 CTSSubscriber Services Scenarios


166/398

Page 166




Applications Overview - 5420 CTSSubscriber Services Scenarios - Overview

This subsection gives detailed scenarios of a selection of subscriberservices. The example scenarios are:

Call WaitingCall PickupSimultaneous RingingTISPAN Conferencing


167/398

Page 167




Applications Overview5420 CTSSubscriber Services Scenarios - Call Waiting


168/398

Page 168




Applications Overview - 5420 CTSServices Example: Call Waiting

Call Waiting (CW) is a residential supplementary service:

While a call is in session, a tone is played to a subscriber to indicate anew incoming call has arrived.

The subscriber can use the hook flash to put the call in session on holdand answer the new call.

The subscriber uses the hook flash again to hang-up on the third partyand return to the original call.

CWT is assigned per PartyID and applies to all associated PUIDs.

Call Waiting - Terminating (CWT) notifies a customer of an incoming call while another call is alreadyestablished. The service allows a customer to put the present call on hold and establish a connection withthe new caller. CWT is a terminating service that does not impact call origination.

Call Waiting can be performed as a network-level feature (for flashable endpoints), or can be provided withinthe endpoint itself (with advanced endpoints). In both cases, the 5420 CTS maintains subscriber data thatdictate the maximum number of simultaneous call appearances. For 5420 CTS- supported call waiting, themaximum will be two call appearances.

CWT is assigned per PartyID and applies to all associated PUIDs.

With non- flashable (advanced endpoints), it is the responsibility of the endpoint to supply the call waitingtone and interpret an appropriate user action (e.g. flash) as a request to answer the second call and placethe first call on hold. Likewise, the endpoint will also interpret additional flashes as requests to toggle theactive and held calls; the 5420 CTS will not be aware that the active and held calls have been exchanged.

With flashable endpoints , Call Waiting is supported within the 5420 CTS. The 5420 CTS will monitor thenumber of call appearances and will inform the endpoint when a second call request has been received.The endpoint will play the call waiting tone and will report a flash by sending a SIP INFO message to the5420 CTS. After receiving an INFO message with flash indication, the 5420 CTS will put the first call on holdand will connect the new caller to the endpoint. Additional INFO requests (to report additional flashes) willinstruct the 5420 CTS to toggle the active and held calls.


169/398

Page 169




Applications Overview - 5420 CTSCW Call Flow for Simple Endpoint (1)

UE-1 CTS-1 UE-2 UE-3

B

C

VP1: Call exists between UE-1 and UE-2

INVITE (SDP offer)

INFO (play call waiting tone X)

200 OK INFO

INFO (flash)

200 OK INFO

180 Ringing (no SDP)

A

D

INFO (cancel tone)

200 OK INFO

This scenario depicts a Call Waiting scenario involving a simple endpoint. The 5420 CTS will instruct theendpoint to play a call waiting tone when a second call request arrives, and the endpoint will reportsubscriber-dialed hook flash back to the 5420 CTS.

(Although not specifically shown, Filter Criteria specify that the 5420 CTS is application server for originating(calling) number and the terminating (called) number.)

A. This scenario begins at a point where a call exists between UE-1 and UE-2, and UE-3 attempts to place acall to UE-1. UE-1 is a simple endpoint.

B. CTS-1 detects that an active call exists between UE-1 and UE-2 and it determines that UE-1 has activatedCall Waiting. CTS-1 must instruct UE-1 to inject a call waiting tone. If the subscriber also has DistinctiveCall Waiting Tones feature, CTS-1 must be able to specify WHICH call waiting tone should be injected.

C. The simple endpoint UE-1 must be able to interpret INFO request and inject appropriate call waiting tone.In addition, UE-1 reports user-dialed hook flash to CTS-1.

D. The call waiting tone must no longer be played to UE-1; either the endpoint is smart enough to turn off thetone when the flash was detected, or CTS-1 will have to send an INFO message with a cancel tonerequest. The worst case scenario is that the CTS-1 will have to send INFO, so that is shown.

The SIP INFO method is described in RFC 2976, and is used to transmit mid-call event notifications and mid-call instructions between an 5420 CTS and endpoints for the following reasons:Simple SIP endpoint sends INFO with an indication that the user has pressed the hook flash.CTS sends INFO to simple SIP endpoint with an instruction to provide call waiting tone to the user.CTS sends INFO to simple SIP endpoint with an instruction to cancel the call waiting tone.CTS sends INFO to MRF with MSCML instructions to play announcements or perform prompt and collectprocedure.

MRF sends INFO to CTS to report status and/or transmit digits collected from the user.


170/398

Page 170





UE-1 CTS-1 UE-2 UE-3

200 OK INVITE (SDP answer)

reINVITE (SDP offer with new session ID,no media lines, and IP address=0.0.0.0)

ACK (for 200 OK INVITE)

E

F


reINVITE (SDP offer from UE-3)


200 OK INVITE (SDP answer from UE-1)


VP2: Voice path established between UE-1 and UE-3; UE-2 is on hold

E. CTS-1 must now swap the active and held calls sent to UE-1. First, put the current call on hold.CTS-1 sends a SIP reINVITE to UE-2 with an IP address of 0.0.0.0 (which is normally used to preventendpoints from attempting to establish RTP streams to a caller ).

F. UE-2 is now on hold and CTS-1 must establish the bearer path between UE-1 and UE-3.


171/398

Page 171





UE-1 CTS-1 CTS-2 UE-2 CTS-3 UE-3

H

200 OK INVITE (SDP offer)

reINVITE (no SDP)


reINVITE(use offer received fromUE-1, IP address=0.0.0.0)


GINFO (flash)

200 OK INFO

IreINVITE (SDP offer from UE-1)



ACK (for 200 OK INVITE, with SDP answer from UE-2)

VP3: Voice path re-established between UE-1 and UE-2; UE-3 is on hold

G. The UE-1 subscriber can use the hook flash to toggle between the active and held calls. UE-1 endpointreport the hook flash to CTS-1 in an INFO request.

H. CTS-1 must now swap the active and held calls sent to UE-1. First, put the call with UE-3 on hold.I. UE-3 is now on hold and now CTS-1 must re-establish the bearer path between UE-1 and UE-2.


172/398

Page 172




Blank Page

This page is intentionally left blank


173/398

Page 173




Applications Overview5420 CTSSubscriber Services Scenarios - Call Pickup


174/398

Page 174




Applications Overview - 5420 CTSServices Example: Call Pickup

Call Waiting (CW) is a business supplementary service:

Call Pickup allows to answer a call that is ringing at another endpoint ina pre-defined Call Pickup group.

A Call Pickup group consists of:One ControllerMultiple members.

An enhancement is Directed Call Pickup, where a call that is ringing at another endpoint in another pre-defined Call Pickup group can be answered when:The Directed Group feature has been assigned andThe Directed Pickup options have been enabled.

Important Call Pickup characteristics:Call Pickup Groups comprise sets of PUIDs, not Party IDs, so that only a subset of calls to an endpoint are

subject to Call Pickup. (Imagine an endpoint that has a personal PUID and a business PUID, where callsdialed with the business PUID are in the Pickup Group, but calls dialed

Documents

TIM15001 R2.0 VU TEN I1 Student Guide