Messages

1

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: February 09, 2017, 07:54:23 AM »

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.

2

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: February 08, 2017, 09:32:53 AM »

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

3

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: February 02, 2017, 08:20:21 AM »

Bump...

4

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: January 30, 2017, 11:57:31 AM »

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.

5

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: January 26, 2017, 08:10:42 AM »

Here is the ybts.conf file...

I have made no modifications.

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

6

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: January 24, 2017, 08:34:29 AM »

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. 

7

Yate bugs / Routing Area Identification Not Set Correctly

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