DOC

Contribution for Osaka Meeting

By Jimmy Rice,2014-07-11 17:25
6 views 0
Contribution for Osaka Meeting ...

ITU Telecommunication Standardization Sector Document APC-1859

    Study Group 16

    Q.12-14/16 Rapporteur Meeting

    Osaka, 15 19 May, 2000

Question(s): Q.13/16, Q.14/16

Source*: Cisco Systems, Inc.

Title: Support for the Redirecting Number IE

Purpose: Proposal

    ___________________

1. Introduction

    A common H.323 application is the implementation of “unified messaging” services. In this

    application, a voice call placed to a destination on the PSTN may be diverted to a unified

    messaging server on an IP network where a voice mail message may be stored along with email

    and fax messages.

In order to deliver the voice message to the correct mailbox, the unified messaging server must

    be able to associate the incoming call with a subscriber. One way to do this association would be

    via knowledge of the number that redirected the call.

In ISDN, the network stores the redirecting number in the Q.931 Redirecting Number IE when

    the call is diverted. However, H.225.0 does not currently include this IE in the Setup message.

    We propose optional inclusion of the Redirecting Number IE in the Setup message in H.225.0.

2. Proposal for H.225.0 v4

The following changes are proposed for H.225.0 v4.

* Contact: Richard K. Bowen Tel: +1 919 392 6948

    Cisco Systems Fax: +1 919 392 6801

    7025 Kit Creek Road, RTP, NC 27709 USA E-mail: rkbowen@cisco.com

    [Begin Addition]

7.2.2.x Redirecting Number

Encoded following clause 4.6.7 of Q.931. This IE is provided only to facilitate interworking

    with the SCN, and not to provide a mechanism for H.323-based call diversion services. Call

    diversion services in H.323 are defined by Recommendation H.450.3.

    [End Addition]

    [Begin Modification]

7.3.10 Setup

    This message shall be sent by a calling H.323 entity to indicate its desire to set up a connection

    to the called entity.

    Follow Table 3-16/Q.931 as modified in Table 12.

    Table 12/H.225.0 Setup

    Information element Length in H.225.0 H.225.0

    status(M/F/O/CM)

    Protocol discriminator M 1

    Call reference M (Note 2) 3

    Message type M 1

    Sending complete O 1

    Repeat indicator F NA

    Bearer capability M 5-6

    Extended facility O 8-*

    Channel identification FFS NA

    Facility O 8-*

    Progress indicator F NA

    Network specific facilities F NA

    Notification indicator O 2-*

    Display O 2-82

    Keypad facility O 2-34

    Signal O 2-3

     2

    Information element Length in H.225.0 H.225.0

    status(M/F/O/CM)

    Calling party number O 2-131

    Calling party subaddress CM (Note 1) NA

    Called party number O 2-131

    Called party subaddress CM (Note 1) NA

    Redirecting Number O 2-*

    Transit network selection F NA

    Repeat indicator F NA

    Low layer compatibility FFS NA

    High layer compatibility FFS NA

    User-user M 2-131

    NOTE 1 Subaddresses are needed for some SCN call scenarios; they should not

    be used for packet-based network side only calls.

    NOTE 2 If an ARQ was previously sent, the CRV used here shall be the same.

    [End Modification]

3. Proposal for H.246 Annex C

This is a proposed mapping from IAM to Setup that can be added as a modification to H.246

    Annex C section C.7.2.8.3.

The mapping of the ISUP parameters in the IAM message to H.225.0 information elements in

    the Setup message is shown in Table 1. The numbers in parentheses show the mapping of

    individual fields. Two redirecting number information elements may be present for multiple

    diversions: the first redirecting number is for the first diversion and the second redirecting

    number is for the last diversion (this scheme is taken from ETS 300 207-1).

    [Begin Modification]

    C.7.2.8.3 Interworking at the exchange where a diverted call is presented to a H.323 network

    For further study.

     3

If a gateway that does not support H.450.3 procedures receives an IAM message containing

    redirecting number and redirection information parameters it maps these parameters to a H.225.0 SETUP message that includes a redirecting number information element as shown in Table 1. In

    the case of multiple diversions within the PSTN an original called number parameter may be

    present in the IAM message. In this case two redirecting number information elements are

    included in the SETUP message as shown in Table 2: the first redirecting number information

    element is for the first diversion and the second redirecting number information element is for the

    last diversion.

    Table 1/Annex C - Mapping of ISUP redirecting parameters for a non-H.450.3 gateway single

    diversion

    IAM -> SETUP ->

    Redirecting number information element

    Redirecting number parameter Type of number (1) Nature of address (1) Numbering plan (2)

     Numbering plan (2) Reason for diversion (4)

     Address signal (3) Number digits (3)

     Redirection information

    parameter

     Redirecting reason (4)

    The numbers in parentheses show the mapping of individual fields

    Table 2/Annex C - Mapping of ISUP redirecting parameters for a non-H.450.3 gateway multiple

    diversions

    IAM -> SETUP ->

    Redirecting number information element

    Redirecting number parameter Type of number (6)

     Nature of address (1) Numbering plan (7)

     Numbering plan (2) Reason for diversion (5) Address signal (3) Number digits (8)

    Redirection information

    parameter

     Redirecting reason (4)

    Original redirection reason (5)

    Original called number parameter Redirecting number information element

     Nature of address (6) Type of number (1)

     Numbering plan (7) Numbering plan (2)

     Address signal (8) Reason for diversion (4)

     Number digits (3)

    The numbers in parentheses show the mapping of individual fields

     4

[End Modification]

_______________

5

Report this document

For any questions or suggestions please email
cust-service@docsford.com