[GSM] Calling subscriber number identification from log file

[dacoder]

Which L3 message contains the Calling subscriber number? The 'Setup' L3 message contains only Called subscriber number.

thanks

[linhhy]

Hi,

In MOC log you can find Called subscriber number in "Setup" message and in MTC log you can find the Calling subscriber number in "Setup" message

[techfolkcmr]

Hi,

In MOC log you can find Called subscriber number in "Setup" message and in MTC log you can find the Calling subscriber number in "Setup" message

I see only calling number's IMSI & TMSI in setup message and not mobile number.

[linhhy]

I see only calling number's IMSI & TMSI in setup message and not mobile number.

Pls look detail in the log below:

000142 09:19:23.750 L3 UL CC Setup
CC Setup
TI flag: 0, Transaction ID: 0x0
IE: Bearer Capability
- .Radio Channel Requirement: dual rate support MS/full rate preferred,
- .Coding Standard: GSM standardized coding as described below,
- .Transfer Mode: circuit mode,
- .Information Transfer Capability: speech,
- .Speech version indication: GSM full rate speech version 3),
IE: Called Party BCD Number
- .Type of Number: unknown,
- .Numbering Plan Id: ISDN/Telephony,
- .Called Party #: 01648670372

000150 09:19:22.703 L3 DL CC Setup
CC Setup
TI flag: 0, Transaction ID: 0x0
IE: Bearer Capability
- .Radio Channel Requirement: full rate support only MS,
- .Coding Standard: GSM standardized coding as described below,
- .Transfer Mode: circuit mode,
- .Information Transfer Capability: speech,
IE: Calling Party BCD Number
- .Type of Number: unknown,
- .Numbering Plan Id: ISDN/Telephony,
- .Presentation indicator: Presentation allowed
- .Screening indicator: Network provided
- .Calling Party #: 01698646671

[techfolkcmr]

Pls look detail in the log below:

000142 09:19:23.750 L3 UL CC Setup
CC Setup
TI flag: 0, Transaction ID: 0x0
IE: Bearer Capability
- .Radio Channel Requirement: dual rate support MS/full rate preferred,
- .Coding Standard: GSM standardized coding as described below,
- .Transfer Mode: circuit mode,
- .Information Transfer Capability: speech,
- .Speech version indication: GSM full rate speech version 3),
IE: Called Party BCD Number
- .Type of Number: unknown,
- .Numbering Plan Id: ISDN/Telephony,
- .Called Party #: 01648670372

000150 09:19:22.703 L3 DL CC Setup
CC Setup
TI flag: 0, Transaction ID: 0x0
IE: Bearer Capability
- .Radio Channel Requirement: full rate support only MS,
- .Coding Standard: GSM standardized coding as described below,
- .Transfer Mode: circuit mode,
- .Information Transfer Capability: speech,
IE: Calling Party BCD Number
- .Type of Number: unknown,
- .Numbering Plan Id: ISDN/Telephony,
- .Presentation indicator: Presentation allowed
- .Screening indicator: Network provided
- .Calling Party #: 01698646671

Friend have a look at the log of mine below. I dont have any issue on L3 UL CC Setup

000448 11:28:38.755 L3 UL CC Setup UL-DCCH UplinkDirectTransfer

Uu_RRC: UL_DCCH_Message
- . .integrityCheckInfo
- . . .messageAuthenticationCode: 2773593929
- . . .rrc-MessageSequenceNumber: 7
- . .message:- uplinkDirectTransfer
- . . . .cn-DomainIdentity: 0 ( cs_domain)
- . . . .nas-Message

CC Setup
TI flag: 0, Transaction ID: 0x0
IE: Bearer Capability
- .Radio Channel Requirement: full rate support only MS,
- .Coding Standard: GSM standardized coding as described below,
- .Transfer Mode: circuit mode,
- .Information Transfer Capability: speech,
- .Speech version indication: GSM full rate speech version 3),
IE: Called Party BCD Number
- .Type of Number: unknown,
- .Numbering Plan Id: ISDN/Telephony,
- .Called Party #: 334455
IE: Supported Codec List - GSM: GSM FR, GSM EFR, FR AMR, HR AMR, UMTS: UMTS AMR, UMTS AMR 2,

000455 11:28:38.755 L3 DL MM TMSI Reallocation Command DL-DCCH DownlinkDirectTransfer

Uu_RRC: DL_DCCH_Message
- . .integrityCheckInfo
- . . .messageAuthenticationCode: 2088376625
- . . .rrc-MessageSequenceNumber: 5
- . .message:- downlinkDirectTransfer:- r3
- . . . . .downlinkDirectTransfer-r3
- . . . . . .rrc-TransactionIdentifier: 2
- . . . . . .cn-DomainIdentity: 0 ( cs_domain)
- . . . . . .nas-Message

MM TMSI Reallocation Command
Skip Indicator: 0x0
IE: Location Area Identification - MCC=***, MNC=**, LAC=****
IE: Mobile identity - TMSI: 1584738654 (0x5E75315E)


But i dont have any L3 DL CC Setup message in my Log.

001804 13:08:29.708 L3 DL CC Release DL-DCCH DownlinkDirectTransfer

Uu_RRC: DL_DCCH_Message
- . .integrityCheckInfo
- . . .messageAuthenticationCode: 2154473268
- . . .rrc-MessageSequenceNumber: 9
- . .message:- downlinkDirectTransfer:- r3
- . . . . .downlinkDirectTransfer-r3
- . . . . . .rrc-TransactionIdentifier: 0
- . . . . . .cn-DomainIdentity: 0 ( cs_domain)
- . . . . . .nas-Message

CC Release
TI flag: 1, Transaction ID: 0x0
IE: Cause
- .Coding Standard: GSM PLMNS Standard
- .Location: User
- .Cause value: class - Normal Event (Hex 1), value - normal call clearing (Hex 00)
- .Diagnostic(s) if any:


I am running a script with auto answer and duration 120s. Call Ends automatically and i wont terminate. Can you explain a bit about your process in making call & termination

[linhhy]

Hi, L3 DL CC Setup message is normal message coming from every normal call, but it only appear on log file with Mobile terminated call.

[techfolkcmr]

Hi, L3 DL CC Setup message is normal message coming from every normal call, but it only appear on log file with Mobile terminated call.

Consider the following scenario. I have a single mobile whose number i dont know (for ex: xxxxxxxxxx) connected to tool and it is dialling Some YYYYYYYYYY number. As per your procedure I can see Calling number (MTC Event) & Called number (MOC Event) as YYYYYYYYYY which is obviously true but is there any L3 message in which i can see my own number XXXXXXXXXX in this case.

[linhhy]

Consider the following scenario. I have a single mobile whose number i dont know (for ex: xxxxxxxxxx) connected to tool and it is dialling Some YYYYYYYYYY number. As per your procedure I can see Calling number (MTC Event) & Called number (MOC Event) as YYYYYYYYYY which is obviously true but is there any L3 message in which i can see my own number XXXXXXXXXX in this case.
With your scenario mentioned you cant see XXXXXXXXXX number in the log.
You can see XXXXXXXXXX number in the log as dialing number if your mobile number YYYYYYYYYY connect to tool and setup for XXXXXXXXXX number call to YYYYYYYYYY number.