Browse Prior Art Database

EXPLICIT NOTIFICATION NOT TO OVERWRITE CALLING PARTY NUMBER BY SERVICE PROVIDERS DURING SNR FORKED CALLS

IP.com Disclosure Number: IPCOM000221028D
Publication Date: 2012-Aug-22
Document File: 7 page(s) / 347K

Publishing Venue

The IP.com Prior Art Database

Related People

Vamsi Mohan Tirunagari: AUTHOR [+3]

Abstract

Explicit definition of a bit in the Calling Party IE of Q.931 PRI Setup message to ensure that the service provider does not replace the actual calling party with the board number of the enterprise. This explicit bit signifies a request from the enterprise not to overwrite Calling Party Number in Calling Party Number IE.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 41% of the total text.

Page 01 of 7

EXPLICIT NOTIFICATION NOT TO OVERWRITE CALLING PARTY NUMBER BY SERVICE PROVIDERS DURING SNR FORKED CALLS

AUTHORS:

Vamsi Mohan Tirunagari

Ravikumar R

Gowthaman Desingh

CISCO SYSTEMS, INC.

ABSTRACT

    Explicit definition of a bit in the Calling Party IE of Q.931 PRI Setup message to ensure that the service provider does not replace the actual calling party with the board number of the enterprise. This explicit bit signifies a request from the enterprise not to overwrite Calling Party Number in Calling Party Number IE.

DETAILED DESCRIPTION

    For an enterprise telephone network, a service provider provisions range of Direct-Inward Dialing (DIDs) and a main/board number to a specific enterprise. When an outgoing call is placed to the Public Switched Telephone Network (PSTN) through a service provider from the enterprise, the service provider expects the calling party number to be in the range of DIDs configured or will overwrite the calling party number with the board number and place the call to PSTN cloud. For example, in the case of the Single Number Reach (SNR) feature in which the call is originated from the PSTN to an enterprise number, and an SNR is configured to a mobile number, the call is forked by a Call Manager to the mobile with the calling party number as the originated PSTN number. However, since this number is not in the range of the DIDs configured, the service provider will overwrite this number with board number and places the call to the mobile. The user of the mobile will see caller ID as the board number, but not the number of the call originator.

Copyright 2012 Cisco Systems, Inc. 1


Page 02 of 7

    This can lead to confusion. For example, the mobile user will not understand who has placed the call, unless he answers the call and speaks to the other person. If the call
is originated by a telemarketer and the mobile user has configured "Do Not Disturb" for calls from telemarketers with his service provider, the call still reaches the mobile as the calling party number is a board number and it does not belong to the list of telemarketers. In addition, if the user of the mobile number has configured his explicit Do Not Disturb feature for certain numbers in his mobile phone, the call will still ring through to the mobile phone as the calling party number is now replaced with board number.

    The reason for this behavior is that some service providers do not allow customers to send a calling party number that is not allocated to them. This is referred to as a caller- ID spoofing prevention mechanism, employed by some service providers.

    The Redirected Dialed Number Identification Service (RDNIS) and Session Initiation Protocol (SIP) diversion features have been developed to overcome this problem. However, even with these features as they currently exist, there is no implicit meaning or direction to the service provider not to overwrite the calling party number. There are instances in which even though SIP diversion header/RDNIS i...