Recent Posts

Pages: 1 [2] 3 4 ... 10
YateBTS / Re: Can't detect my GSM network with newest phones.
« Last post by paulc on December 07, 2017, 12:19:21 PM »
It is important to know the following:
- Is the bladeRF frequency (auto)calibrated?
- Are you using the 850MHz band?
- What is the PLMN (MCC+MNC) of the IMSI
- What is the PLMN broadcasted by the BTS
- Where you are located geographically

At the whim of US operators Apple (and others) have introduced restrictions about which bands are available to which networks. In some conditions the phones may not list some or all cells in a band. This depend on the hardware version, iOs version, SIM and network identity. I am not sure but it's possible that geolocation may be taken into account as well.

The GSM850 / LTE band 5 is one of the bands affected since it's supposed to be used only in North America, South Korea, China and Australia. If you're located somewhere else or not having a matching IMSI the phone may not list cells or may behave erratically.

Try using one of the worldwide GSM bands - 900 or 1800. These are unlikely to be restricted.
YateBTS / Can't detect my GSM network with newest phones.
« Last post by kycfeel on December 04, 2017, 04:27:14 AM »
Hey guys.
I'm testing my Yate 6 based GSM network built with Raspberry pi and BladeRF x40.
and I think i can't detect my network with newest phones (iPhone 6s or higher).

My old iPhone 6, 5c, and Motorola MB860 can detect it, and connect to it very well.
But newest phones, like iPhone 6s, and iPhone 7 can't even detect my network on settings.
I'm not sure about newest Android phones cause i don't have any test devices right now.

I'm pretty sure that every iPhones released to market support GSM network connectivity. So definitely not the hardware problem.
Any of you experiencing same problem as mine? Need your help!
YateBTS / Re: Problems with libusb!!
« Last post by david.burgess on November 29, 2017, 06:50:59 AM »
The timestamp jumps usually mean that the CPU is not keeping up with the radio signal. If they are not too severe, YateBTS will still work. If your phone sees the beacon, then it might be OK. You say "a lot" of timestamp jumps? How often do they happen?
YateBTS / Re: YateBTS support for Ettus B210
« Last post by david.burgess on November 29, 2017, 06:41:40 AM »
YateBTS does not support the Ettus B210.
YateBTS / Re: Solved gsmtrx:ALL ARFCN[0]: Slot ... Excessive TOA errors
« Last post by sir.costy on November 29, 2017, 04:21:25 AM »
You say solved but not explain how did you solved the issue.
Can you share it please?
Linux / Re: embedding Yateclient with rmanager controls
« Last post by marian on November 29, 2017, 02:36:10 AM »
I suppose you are routing incoming calls to an audio device module (alsachan).
You may add an autoanswer=no parameter when routing the call.

You need some logic to anwer calls on demand.
You may write a javascript script to track calls (you may use call.cdr for that, 'chan' parameter is what you need.
The script should implement a command to answer (just send a chan.masquerade message with call,answered) a specific channel id.
Linux / embedding Yateclient with rmanager controls
« Last post by brad on November 28, 2017, 10:01:26 PM »
I'm embedding yateclient in a small Linux headless machine.  I can use rmanager via telnet to initiate calls (using call) and status cdrbuild to watch for incoming calls.  I'd prefer to not 'auto answer' inbound calls, rather, I'd like to be able to control when and if the call is answered via rmanager.   

Is there a parameter that I can set via the rmanager interface to change the current cdr status from 'ringing' to 'answered'?
YateBTS / Re: Problems with libusb!!
« Last post by afk on November 28, 2017, 03:43:35 AM »
Hello Jambo,

Please try from rmanager (telnet 0 5037) to set 'debug ybts level 9'
It will give you information about the subscriber that wants to attach to the BTS. (There you will have an <imsi> </imsi> field containing the IMSI)

YateBTS / Re: Difference of the USIMS
« Last post by afk on November 28, 2017, 03:28:24 AM »
Hello smlee,

Can you please provide us the username of your HostedCore account?

Regarding the USIMs difference, there should not be one. All SIMs are from same batch, but we will look into it after we recognize your order/product.

Thank you in advance
The routing is done automatically in the nipc.js script. Regexroute is not involved at all. You leave registration with regexp (that is also done in the nipc script), and don't modify anything in the regexroute.

If the outbund connection is set and it's connected, then calls that can't be routed inside will automatically go to them. If you set in regexroute to route all calls outside, it's normal not to be able to route anything to the registered users.

Post an archive with all you configuration files and a yate log with sniffer and debug on as instructed in the previos post. Just a single screenshot doesn't help.
Pages: 1 [2] 3 4 ... 10