My Oracle Support Banner

Pin_fld_direction Always Stores 1 For Both Incoming As Well As Outgoing Calls (Doc ID 942419.1)

Last updated on MARCH 18, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and later
Linux x86-64
Linux x86-64

Symptoms

-- Problem Statement:
Pin_Fld _direction stored in the table event_session_tlco_gsm_t is always set to the value 1 for both incoming and outgoing call, which is wrong.


in case of incoming call, i.e. Mobile terminated call, value should be 1 and for MO calls value should be 0.

 if Subscription-Id-data = calling_number then its a outgoing call and direction should be 0 and if
Subscription-Id = called_number then its a incoming call and direction = 1.
This is required because there should be some field to differentiate between incoming and outgoing call.

Basic Scenario :
When trying the scenario of both incoming as well as outgoing call. in outgoing call,
Subscription ID-Data = Calling Station-ID and in this case the direction we are expecting in the
event_session_tlco_gsm_t table is 0 and in incoming call, Subscription ID-Data = Called Station-ID
and in this case the direction we are expecting in the event_session_tlco_gsm_t table is 1. but we
are getting 1 in both the cases.


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.