Messages

46

YateBTS / Re: Can't start Yate with BladeRF

« on: August 10, 2016, 01:56:43 AM »

It seems that the BladeRF module (ybladerf.yate) is missing. (See : http://forum.yate.ro/index.php?topic=1277.msg4896#msg4896)

If you compiled and installed yate by yourself, you might not have had the libusb-1.0-devel support at configure time. Install the development libraries for libusb-1.0, reconfigure Yate (and you can check in config log that libusb was detected) and re-compile, reinstall.
After this, check that in yate_src/modules/radio/ you have ybladerf.yate

If still that doesn't work, please post how you installled yate, how you started it,  Yate version and YateBTS version and the output of 'status' command in the telnet console of yate.

47

YateBTS / Re: YateBTS with B210 not working?

« on: April 28, 2016, 09:02:28 AM »

Hi,

Since revision 504 of the YateBTS repository, YateBTS only supports bladerf. If you want non-bladerf support, you must use something prior to that.

Note:
* make sure to properly cleanup the current installation, otherwise you might end up with mismatching between transceivers.
* use a Yate that corresponds with that YateBTS.

48

Features requests / Re: How to collect the debugging information?

« on: March 07, 2016, 02:23:43 AM »

Please checkout http://docs.yate.ro/wiki/Debugging_in_Yate

You probably need to turn on debug on SIP also ('debug sip level 10' command in telnet console).

Also, a wireshark capture can help.

49

YateBTS / Re: change sms welcome message

« on: February 15, 2016, 02:13:52 AM »

You need to check which one of the scripts is Yate using.
To do that, log into Yate's rmanager through telnet (telnet 127.0.0.1 5038) and issue the 'status engine' command. In the sharedpath= parameter you'll see the path from where yate loads nib.js.
You only need to change the one Yate is using. But, if it's the one from /usr/local, please make a back-up in case you re-install YateBTS (it will overwrite it in that case).

You don't need to recompile YateBTS, you just need to restart or re-initialize YateBTS.

50

YateBTS / Re: YateBTS not starting

« on: October 02, 2015, 01:29:41 AM »

Hi,

You must make that configuration in yate.conf. It's not clear from your message where you made that configuration,  but the log indicates that you are starting gsmtrx in conjuction with mbts that expects the old transceiver.

Also check that you are editing the right file (see configpath in the result of status engine command in telnet.

51

Installation from packets/SVN/.exe/AppStore / Re: Hate doesn't start on Yosemite

« on: September 17, 2015, 06:41:56 AM »

Hi,

How was it installed?
How are you starting it?
How are you checking that it's not started (please keep in mind that installing YateServer from the dmg wont show anything in the GUI)

If you're starting it from command line, please provide a log.
If you installed it from the .dmg,  try in Terminal the command 'telnet localhost 5038'. If it connects, Yate is running. If not, please provide some more info (do you see in Console any message regarding Yate? If so, please paste it here)

52

YateBTS / Re: New Transceiver doesn't work with non-rfblade devices

« on: September 10, 2015, 01:29:33 AM »

Hi,

You have a mismatch between the Yate version and the YateBTS version. In newer versions of Yate, yategsm.h and libyategsm ware renamed to yateradio.h and libyateradio.

So if you want to use YateBTS 4.0.2, i would recommend using the release of Yate from the same day (it's Yate 5.4.2).
The latest YateBTS (5.0) version also uses the old transceiver and works with the latest Yate release.

If you want the SVN, the latest SVN revision that has the old transceiver is rev. 503.

53

YateBTS / Re: Calls to 99991001 and other yate tests do not work.

« on: August 31, 2015, 08:48:58 AM »

I'm posting from the IRC chat what as happening for posterity's sake:

<oana> sugarcakes, ok. What is happening is that the handler in NIB has a higher priority than regexroute.
<oana> that handler, if it doesnt recognize the number as a registered user, it will try to route it to a gateway
<oana> and the route messages never reaches regexroute. If you want to be able to call to tone/* set a higher priority to the regexroute handler
<oana> what you need to do is to set something like route=75 in the [priorities] section in regexroute.conf
<oana> it's commented by default in the conf, so uncomment it too

54

YateBTS / Re: GSM.Identity.Shortname ignored by Cell (works in OpenBTS)

« on: August 31, 2015, 07:46:24 AM »

That issue was solved only in the commercial version of YateBTS as it uses a private library.
So, in the opensource version  that particular settings has no effect.

55

YateBTS / Re: Getting IP address for GPRS

« on: August 20, 2015, 02:45:21 AM »

In rmanager, issue command "mbts gprs list" and look at the RSSI level for the phone. If it's positive, you are probably keeping the phone too close to the base station and saturating the receiver (meaning a lot of bursts will be dropped).
Post the result of that command here.
Also post the result of the 'mbts power' command.
Also, please provide a log as specified before.

56

YateBTS / Re: Getting IP address for GPRS

« on: August 18, 2015, 01:23:22 AM »

Hi,

Please specify:
* what version of YateBTS are you using.
* how is it configured
* how are you testing (how close is the phone to the base station, what are the power levels)

Also, please provide a log with GPRS debug enabled.  Check ybts.conf.sample about how to enable that.  Debug should at leeast be enabled on the following files: MAC, TBF, RLCEngine,  LLC, FEC, SGSN. Also check this for more information: http://wiki.yatebts.com/index.php/Logging_and_Debugging

57

Yate bugs / Re: How to find out which child is unresponsive?

« on: August 10, 2015, 01:18:52 AM »

If Yate is waiting for a message to be handled by your script and the message is not handled in reasonable time (10 seconds, as fas as i rememenber), Yate will be restarted by the supervisor. So, although it may see that Yate is unresponsive, the cause could be the script.

Please provide a log and if you started yate with the -C option, look at the core left by the restart and please paste it also.

58

Linux / Re: Yate in PCLinuxOS

« on: August 10, 2015, 01:14:53 AM »

You can find the srpm here http://docs.yate.ro/wiki/Download#Downloadable
RPMs here (they're for Mageia) http://yate.null.ro/tarballs/yate5/mga4/x86_64/

59

YateBTS / Re: RACH burst for unsupported device?

« on: August 04, 2015, 01:27:57 AM »

The latest version of YateBTS has some issues with the transceiver that affects the functionality.
Please use a YateBTS prior to SVN revision 504.
First make uninstall to the current YateBTS, and then install the older version. Keep in mind that the older version has a dependency on libbladerf-dev, so you need to have it installed.
Please make sure you don't have the new transceiver (gsmtrx) and the old transceiver running at the same time (transceiver-bladerf).  They use the same port and this will affect functionality as well. The need to uninstall the new YateBTS is just avoid this issue.

60

YateBTS / Re: BladeRF issues - UPDATED

« on: July 21, 2015, 01:31:14 AM »

Hi,
 
If you're using a SVN revision prior to rev. 504, this should give you a clue:

2015-06-03_23:15:07.890780 <mbts:GOON> OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver-bladerf

Possible causes for this:
* you don't have the development version of bladerf or libusb1, so the transceiver was not compiled. Check where you compiled YateBTS that you have the compiled transceiver-bladerf (it should be in mbts/TransceiverRAD1). If you don't have it, run the configure script again and look for the lines that say if it detected support for it or not.
* you didn't configure the correct path to the transceiver-bladerf. Check again the path to the installed transceiver-bladerf and make sure you have configured it correctly in ybts.conf.


If you're using SVN revision 504 or upwards, you don't need bladerf-devel anymore. Just make sure that you use the latest Yate also and that you have libusb1-devel.