Yate Community Forum
Yate server => Yate bugs => Topic started by: chewwtoy on January 23, 2017, 09:45:43 AM
-
I set my MCC to 262 (Germany) and my MNC to 10 (M2M test Network) however my Routing Area Identification is not being set correctly for GPRS.
I tapping turned on an monitored the GPRS LLC message from my bts and the MCC and MNC are both being set to 712 (not 262). The LAC and RAC are being set correctly. Is anyone experiencing this issue?
I'm currently using Yate 5.5.1 devel1 r6165 (built from SVN)
-
Hi,
Please provide a wireshark capture and a Yate log, if possible.
-
The PCAP is here: https://www.dropbox.com/s/ivl84pmprcbyc9w/Routing%20Area%20Issue.pcapng?dl=0
The file is big! (255MB)
Look for line number 1038 with the filter "gsmtap && gsm_sms" enabled. Time is 159.688363.
-
Can you also post the configuration (ybts.conf)?
Also, did you do anything special (issued commands, modified code)?
-
Here is the ybts.conf file...
I have made no modifications.
https://www.dropbox.com/s/rpiw5jge6sefem6/ybts.conf?dl=0
-
1. YOu said you set MCC to 262 and MNC to 10, but it's set to 26204 (which is Vodafone's). You also set the ShortName to Vodafone (Do you see it on the phone?). Please keep in mind that you could cause problems for actual Vodafone customers.
2. What version of YateBTS have you installed?
3. What phone are you using?
-
I've tried a few MNC's to test. They all gave the same results.
Currently using YateBTS release 5.0.1 built Jan 19 2017 rev598
We're using an IOT device based on Heuwei IOT.
-
Bump...
-
Hi,
I cannot recreate your problem. The code reads the MCC and MNC for GPRS from the same place the GSM procedures read it.
Did you do any Yate reloads between CS attach and GPRS attach?
-
I did not? Is there an issue with the version of Yate or YateBTS that I'm using?
-
Please post the Yate version, YateBTS version, how did you installed it, how are you starting the YateBTS and where is your configuration file located.
Are you running in nib or roaming mode?
Also what is your testing procedure?
A log from YateBTS with debugging enabled would also help (see http://wiki.yatebts.com/index.php/ Troubleshooting section and the debug options in ybts.conf file).
-
I'm using YateBTS release 5.0.1 built Jan 19 2017 rev598 and Yate 5.5.1 devel1 r6165 (built from SVN).
I'm starting yate from the terminal. "sudo yate"
My config file is located in /usr/local/etc/yate/
I'm running in nib mode.
Testing went as follows:
I tell the mobile device to connect to the network (262 10 or 01 or 04, etc). It makes connection and is able to send and receive SMS messages. It does not get an IP address. To see the status of the device, I telnet into the BTS interface (telnet 0 5038). I run command mbts gprs list. I can see my ISMI listed but the status is Registration Pending and it stays there for a long time. To find out why I enabled GSM tapping. I logged the results using Wireshark ( https://www.dropbox.com/s/ivl84pmprcbyc9w/Routing%20Area%20Issue.pcapng?dl=0). I noticed that the Routing Area ID is not correct.
I will follow up with a log from YateBTS with debugging enabled.
-
Can you also tell me on what machine/platform you are running the YateBTS?
Does this behaviour manifest with any other device (which would do an AttachRequest for GPRS, not a RoutingAreaUpdate) ?
Did you do a clean build and install?
Also can you post the output of the command "mbts rawconfig"?
-
Hello,
I am having the exact same issue as "chewwtoy", please see attached screenshots.
Has anyone successfully resolved this issue ?
Best regards,
Nicolas
-
Please tell me on what type of hardware you are running yateBTS and what compiler you are using for compiling YateBTS.
-
Hello,
I am using bladeRF, I am not sure what you mean by compiler, it's being ran on ubuntu.
Best regards,
Nicolas
-
By hardware I meant what kind of PC you are running on (Intel, ARM, which type of CPU, which version of operating system ).
By compiler I meant the version of GCC (seeing that you're on Ubuntu - I guess you are using gcc). You can check the version by using in a terminal gcc --version command.
How did you install YateBTS and which version is it?
-
there are requested details :
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
YATE 5.5.1-devel1 r
yatebts Release 5.0.1 formal build date Jun 11 2016 rev
3,7 Gio
Intel® Core™ i3-3225 CPU @ 3.30GHz × 4
Intel® Ivybridge Desktop
64 bits
310,8 Go
It has been installed nearly a year ago I can not remember clearly how we installed it, probably using apt get
-
Then please post the output of
dpkg -s yate-bts
We don't provide Debian packages for YateBTS, so I'm interested from where it was installed and what version it is.
-
Hello,
The command you told me to use replies an error saying the package is not installed.
As I wrote previously it's been nearly a year it's installed and I did it with a friend more used to linux environement I do not really remember how it been installed.
-
From where did you get this information then?
YATE 5.5.1-devel1 r
yatebts Release 5.0.1 formal build date Jun 11 2016 rev
-
for YateBTS it's from yate-bts startup messages I launch with sudo yate -s
for Yate, I'm not sure how I made it appear if that's of great importance I will search again and tell you
-
Could you install again with current sources?
You would need to follow:
http://wiki.yatebts.com/index.php/Prerequisites
http://wiki.yatebts.com/index.php/Installing
After that, post if you have still have the issue.
-
Have the same issue here.
Yate 6.0.1 devel1 r6316
Built from sources https://wiki.yatebts.com/index.php/Installing with patch applied - http://yate.null.ro/mantis/view.php?id=416
Linux 4.15.0-kali3-amd64 #1 SMP Debian 4.15.17-1kali1 (2018-04-25) x86_64 GNU/Linux
-
Same problem here!
Yate 6.1.1 devel1 r6325Maybe this probles is related to my post https://forum.yate.ro/index.php?topic=2004.0 (https://forum.yate.ro/index.php?topic=2004.0)
and some device cannot accept this LA so GPRS doesn't works!
-
Bug fixed: it was related to wrong handling MCC/MNC in GPRS AttachAccept