Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rod5413

Pages: [1]
1
Further Update,

After using Rmanager, and using the rawconfig command. It appears that Cell Bar Qualify (GSM.SI3RO.CBQ), Cell Reselection Offset (GSM.SI3RO.CRO), Temporary Offset (GSM.SI3RO.TEMPORARY_OFFSET) and Penalty Time (GSM.SI3RO.PENALTY_TIME).

Have all been disabled.

2
Hi David / Paulc

After doing more testing on the "system information 3" messages (using a network drive test kit)

It appears that all the "Selection Parameters" (under SI3 Rest Octets) are not being transmitted  in the system information 3 message.
This includes,    Cell Bar Qualify, Cell Reselection Offset, Temporary Offset and Penalty Time.

At this point, I would be grateful if someone else could confirm.

Thanks,  Rod


3
Hi Paulc,

When you say Release=6, do you mean Counters.TbfRelease=6 (on the GPRS Advanced tab)?
If so, it didn't change the "malformed packet) fault messages for my setup.

With your changes with the GPRS setup (no malformed packets), are you able to receive and decode a CRO value?

4
Hi David,

Just checking to see if there's anything else I can do to help resolve this issue.

Rod.

5
YateBTS / Re: How do I change the location update reject code?
« on: July 28, 2014, 10:31:16 PM »
Hi Mongo,

You need to change the reject code value within the ybts.cpp file, before compiling.

6
Hi Marian / Monica

Thanks for that, I really appreciate your time and help.

But when I search for the file, its appears that it doesn't exist. After googling the problem, it appears that other people have had the same problem, but I was unable to find a solution.

Also, going through the default install of YateNIB, there is a YBTS tab which has entry field "Datafile" with the entry of "ybtsdata.conf"
It also appears that the file doesn't exist.

Could someone please tell me, what is the difference between these 2 files, and  why they haven't been created?

Rod.

7
Hi,

I was looking for a database within Yatebts, that contained basic GSM Tap info (UDP, port 4729)
The sort of recorded information I'm after is; Location update request, Location update rejected, Measurement reports, Identity request, Identity response, IMSI, IMEI and TMSI (if possible).

Any help is greatly appreciated.

Rod

8
Hi David,

I have tried using other handsets, but had not luck decoding the CRO value.
I've also used a Sagem OT-290 engineering handset, which also couldn't decode the CRO.

Thanks again for all your help and time.

Rod.

9
Hi David,

I've tried adjusting the CRO value using the Yate command line.

"mbts rawconfig GSM.SI3RO.CRO value"       

But it still appears not to be working. I tried multiple things for value e.g. 64, 63, 10, 1, 2, etc.
I've enable the GPRS, (is there anything else in the GPRS settings that needs to be enabled?). Is there anything else I can check?.

If anyone could please tell me how to change the code listed below, (to increase the CRO value), it would be greatly appreciated.

// (pat) 11-26-2011 If you enable this in the OpenBTS sql, the microtech
   // modem stops registering.

   // See GSM 04.08 10.5.2.34 and 05.08 9 Table 1.
   // 12-12: Pat reversed the logic of this so the default is to have the rest octets
   // if any of the other SI3R0 things are defined, unless you specifically
   // define GSM.SI3RO as 0:
   if (gConfig.defines("GSM.SI3RO")) {
      mHaveSI3RestOctets = gConfig.getNum("GSM.SI3RO");
      if (!mHaveSI3RestOctets) return;
   }

   // Optional Cell Selection Parameters.

   // CELL_BAR_QUALIFY. 1 bit. Default value is 0.
   if (gConfig.defines("GSM.SI3RO.CBQ")) {
      mCBQ = gConfig.getNum("GSM.SI3RO.CBQ");
      mHaveSI3RestOctets = true;
      mHaveSelectionParameters = true;
   }
   // CELL_RESELECT_OFFSET. 6 bits. Default value is 0.
   // C2 offset in 2 dB steps
   if (gConfig.defines("GSM.SI3RO.CRO")) {
      mCELL_RESELECT_OFFSET = gConfig.getNum("GSM.SI3RO.CRO");
      mHaveSI3RestOctets = true;
      mHaveSelectionParameters = true;
   }
   // Another offset to C2 in 10 dB steps, applied during penalty time.
   // 3 bits.  // Default is 0 dB but "7" means "infinity".
   if (gConfig.defines("GSM.SI3RO.TEMPORARY_OFFSET")) {
      mTEMPORARY_OFFSET = gConfig.getNum("GSM.SI3RO.TEMPORARY_OFFSET");
      mHaveSI3RestOctets = true;
      mHaveSelectionParameters = true;
   }
   // The time for which the temporary offset is applied, 20*(n+1).
   if (gConfig.defines("GSM.SI3RO.PENALTY_TIME")) {
      mPENALTY_TIME = gConfig.getNum("GSM.SI3RO.PENALTY_TIME");
      mHaveSI3RestOctets = true;
      mHaveSelectionParameters = true;
   }

10
YateBTS / Re: How do I change the location update reject code?
« on: July 05, 2014, 02:15:19 AM »
Thanks Marian,

Your help is greatly appreciated.  ;D ;D ;D

11
Thanks David,

Very much appreciated.  ;D ;D ;D

12
Hi Guys,

Just wondering if it's possible to set-up a "cell reselection offset (CRO) using YateBTS.
Any help would be greatly appreciated.

13
YateBTS / How do I change the location update reject code?
« on: July 03, 2014, 06:06:43 PM »
Hi guys,

I've just started playing around with YateBTS, and found that when a handset is rejected from a location update, it appears that the handset is given a invalid code (Reject cause =111 Protocol error, unspecified).
The effect on this rejected handset is that it doesn't return to it's previous network. It just stays hanging around, disconnected from any network (so it appears).
So my question is, can this reject code be easily changed, and where about in the ybts.cpp file does the changes need to be made.
Any help regarding this matter is greatly appreciated.

Pages: [1]