Routing Area Identification Not Set Correctly

[chewwtoy]

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)

[Ioana Stanciu]

Hi,

Please provide a wireshark capture and a Yate log, if possible.

[chewwtoy]

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. 

[Ioana Stanciu]

Can you also post the configuration (ybts.conf)?

Also, did you do anything special (issued commands, modified code)?

[chewwtoy]

Here is the ybts.conf file...

I have made no modifications.

https://www.dropbox.com/s/rpiw5jge6sefem6/ybts.conf?dl=0

[Ioana Stanciu]

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?

[chewwtoy]

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.

[chewwtoy]

Bump...

[Ioana Stanciu]

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?

[chewwtoy]

I did not?  Is there an issue with the version of Yate or YateBTS that I'm using?

[Ioana Stanciu]

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).

[chewwtoy]

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.

[Ioana Stanciu]

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"?

[nicolas yate]

Hello,

I am having the exact same issue as "chewwtoy", please see attached screenshots.

Has anyone successfully resolved this issue ?

Best regards,

Nicolas

[Ioana Stanciu]

Please tell me on what type of hardware you are running yateBTS and what compiler you are using for compiling YateBTS.