Messages

31

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: April 28, 2017, 01:20:35 AM »

Then please post the output of

Code: [Select]

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.

32

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: April 27, 2017, 08:29:20 AM »

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

Code: [Select]

gcc --version command.

How did you install YateBTS and which version is it?

33

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: April 27, 2017, 06:35:01 AM »

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

34

YateBTS / Re: YateBTS GPRS not working with USRP2

« on: April 03, 2017, 05:59:14 AM »

Hi,

Please see this thread:

http://forum.yate.ro/index.php?topic=1381.0

Please post a log with the debug options specified there enabled.

The yate log shows a call and SMS being done. Keep in mind, that on 2G, CS services suspend Data services. In the GGSN log, you can actually see the GRPS suspension request.

35

Yate server for Google Voice / Re: "Jingle call failed. Incomplete caller"

« on: March 09, 2017, 09:05:10 AM »

clientlog.txt shows that you are routing in client to Google. See :

Sniffed 'call.route' time=1488989110.984375
  thread=02FF4A68 'Call Router'
  data=00000000
  retval='(null)'
  param['id'] = 'client/4'
  param['module'] = 'client'
  param['status'] = 'incoming'
  param['billid'] = '1488988375-4'
  param['answered'] = 'false'
  param['direction'] = 'incoming'
  param['called'] = '18005551212'
  param['line'] = 'sip:200@192.168.0.9'
  param['account'] = 'sip:200@192.168.0.9'
Returned true 'call.route' delay=0.000000
  thread=02FF4A68 'Call Router'
  data=00000000
  retval='jingle/18005551212@voice.google.com'
  param['id'] = 'client/4'
  param['module'] = 'client'
  param['status'] = 'incoming'
  param['billid'] = '1488988375-4'
  param['answered'] = 'false'
  param['direction'] = 'incoming'
  param['called'] = '18005551212'
  param['line'] = 'GoogleVoice'
  param['account'] = 'sip:200@192.168.0.9'
  param['handlers'] = 'javascript:15,cdrbuild:50,fileinfo:

So you either modified the configuration for the client. Or the client and server read configuration from the same place.
If you have installed both Yate and YateClient on the same machine, please start one with a different configuration directory. The default one is /etc/yate. Please check the '-c' command line option.

36

YateBTS / Re: GPRS : cannot find pdp context

« on: March 01, 2017, 06:36:37 AM »

Even if the phone isn't showing that is doing anything, you need to look at the logs.
Looking at it, I can see one time those error messages appearing after the phone was doing a call (you can see the call setup and release)
Another time, the phone is doing on voice a location update procedure (is registering to the BTS):
 * at 2017-03-01_12:36:52.516012 is doing location update request
 * at  2017-03-01_12:36:52.750290 the GPRS Suspension request arrives
 * at 2017-03-01_12:37:35.519890 the error messages appear

I don't know how you are testing, but until you do something on the phone to request data access, the phone won't probably try to do GPRS again. The fact that you are receiving data for downlink makes me assume that you do have at some point some data access.

Also, I don't think I see the termination of attach procedure for GPRS (an attach complete should be in the logs).
You can check the status of the GPRS registration for the phone with "mbts gprs list" in telnet window. If it says RegisteredNormal it means that the phone finished GPRS registration procedure, otherwise something fails along the way.

37

YateBTS / Re: GPRS : cannot find pdp context

« on: March 01, 2017, 04:00:20 AM »

The answer for what is happening is here:
  12:36:52.7:SGSN:Received GPRS SuspensionRequest for tlli=0x855ab328

This means that the phone is doing something on the CS side (voice, SMS). While doing that, data services are suspended in 2G.

38

YateBTS / Re: GPRS : cannot find pdp context

« on: February 28, 2017, 03:09:36 AM »

Those messages appear when data comes from the internet to be transmitted downlink for an IP allocated to a MS and the resources allocated in the BTS for that MS have beed deleted (PdpContext has dissappeared). This can happen for various reasons (data arrives while the phone is re-attaching)

You need to post a log with debugging enabled on SGSN and GGSN which contains more information about what is happening, not just the errors.

39

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: February 10, 2017, 06:51:12 AM »

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

40

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: February 09, 2017, 02:19:13 AM »

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

41

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: February 06, 2017, 02:44:26 AM »

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?

42

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: January 27, 2017, 09:22:59 AM »

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?

43

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: January 25, 2017, 03:13:17 AM »

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

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

44

Yate bugs / Re: Routing Area Identification Not Set Correctly

« on: January 24, 2017, 02:19:51 AM »

Hi,

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

45

YateBTS / Re: Help for yatebts + bladerf x115

« on: October 18, 2016, 09:47:35 AM »

Please see here: http://forum.yate.ro/index.php?topic=1310.msg4966#msg4966