Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - kpz

Pages: [1]
YateBTS / Re: yateBTS network operator name of 712712
« on: September 25, 2018, 12:04:11 PM »
Wheres Monica on this

switch too voice pulse five SIP servers for yateBTS, config is easy and is very cheap.

YateBTS / Re: Can't installing yate on rasspberry Pi3
« on: September 25, 2018, 12:02:07 PM »
You gotta run off ubuntu 14

YateBTS / Re: Problems MCC, MNC.
« on: September 25, 2018, 12:00:51 PM »
This Monica chick/man really chooses what he/she replies too, i think most of her/his help responses are telling people they need to buy a product that is already shady to begin with lol.

YateBTS / Re: yateBTS network operator name of 712712 - SOLVED
« on: July 27, 2018, 11:47:55 AM »
This is still a problem when GPRS is enabled? admin help please? possibly? you even on here? jeez....jeesus chriszt...

YateBTS / Re: can we record calls with yatebts ?
« on: July 27, 2018, 10:17:55 AM »
Could you just use the GSM tap function included in yate?

ryaquaza, still having problems, lol.
i am running php 7.0.27 and raspbian stretch latest as of june 20 something 2018.
on my ubuntu box i have php 7 and ubuntu mate 16.04

what combo are u using?


I got the SIP outbound call stuff setup and working as well as a data connection for the phone. I can place out bound calls and get out on the web. I just was wondering if there is a next step available with yate and yateBTS to get text messages going outbound? Is there any SIP like services for text messages?

Thank you

Here is my console output when trying to send a text message, i feel like the answer is here, just cant see it

YateBTS / Re: GSM Identity Shortname
« on: June 20, 2018, 05:01:57 PM »
Any help i can do on this topic? ive been searching through old yateBTS code to try and find the old transmit code, but im too lost. willing to help though. Any updates?

YateBTS / YateBTS Web GUI Blank after fresh install and configuration
« on: June 20, 2018, 03:45:36 PM »
I bring up to access yateBTS GUI for configuration, but all i find is a white blank page displaying the contents of the index.php(see below) file that is included in the nipc_web folder.

Am i doing something wrong in configuration? I followed the instructions from, , and made sure to give a+rw privileges to the correct folder.

Any one encountering the same thing? kinda stumped.


Contents of index.php that i'm seeing instead of the GUI

 * index.php
 * This file is part of the Yate-BTS Project
 * Copyright (C) 2014 Null Team
 * This software is distributed under multiple licenses;
 * see the COPYING file in the main directory for licensing
 * information for this specific distribution.
 * This use of this software may be subject to additional restrictions.
 * See the LEGAL file in the main directory for details.
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of

Header("Location: main.php");

YateBTS / yateBTS network operator name of 712712
« on: June 18, 2018, 03:31:27 PM »
I setup yatebts NiPC, all is up and running. The only thing i cant seem to change is the Network Operator name. Even when changing the MCC and MNC in the ybts.conf file, that changes the name of the BTS that is transmitted to my phone in the "search for networks" settings menu. My BTS pops up as "320201" for a network operator, but once i register to it and bring the information up in a cell network app, The name of the network is "712712 costarica" which makes sense becuase for the 712 mcc, but no where in the code did I set that value to 712. I have NO idea where it is coming from or originating. This even happens right out of the box with the NiPC default settings. Ive tried looking through nibc.js and subcribers.conf but found nothing. Any help is appreciated.

If anyone was having the same problem i just disabled GPRS in the ybts.conf file. That seemed to fix the problem and it is now transmitting the correct MCC and MNC as the network operator.

Pages: [1]