Yate Community Forum
OpenLTE => YateBTS => Topic started by: rod5413 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.
-
Hi,
ybts.cpp:
See YBTSMM::locUpdTerminated()
-
Thanks Marian,
Your help is greatly appreciated. ;D ;D ;D
-
Is the reject cause code required to be set prior to compiling or am I miss interpreting this? I am trying to set my system to reject cause code of 13 (no roaming this LAC). In OpenBTS there was a config line you could set, but I am unable to find that in YateBTS. I do appreciate the help.
-
Hi Mongo,
You need to change the reject code value within the ybts.cpp file, before compiling.
-
You may use a script to catch the user.register message after the registering module (I suppose you are using nib.js for that).
Set the handler priority at higher value then nib.js (I think 100 is ok).
Check the error parameter.
You should ignore the message if the error is 'noauth'.
You may set your code in the error parameter.
-
Thanks for pointing me in the right direction.