Messages

1

YateBTS / Re: Phone doesn't auto connect to yatebts

« on: July 15, 2019, 05:29:33 AM »

Hi Desma,

To help debug this you can use the telnet console: telnet 0 5037
To clean the logs: debug gsmtrx off. That information is not relevant  and it usually flods the logs.
Then activate better logging: debug ybts level 10, debug mbts level 9. This should show if you actually see the registration requests.

Regarding automatic registration:
- if the MCC MNC on the SIM are different than the ones configured, the phone won't try to connect automatically
- if registration was rejected (depending on the error message) the phone won't try again , you can try to remove the sim and insert in back again. But some phones might not try again. You should use a different phone/sim.
- where is the subscriber information stored: subscribers in nipc mode/ regexp/ roaming mode to a core network?

If you suspect a radio issue:
https://yatebts.com/documentation/radio-access-network-documentation/radio-network-troubleshooting/radio-related-problems/

2

Other Yate server issues / Re: VoLTE Lab can be shipped out of the State?

« on: May 24, 2019, 02:31:32 AM »

Hi,

You can buy it from the shopping cart and pay with card or using wiretransfer. It shouldn't be an issue to deliver to China . You can use the chat feature on the website in case you have additional questions.

3

YateBTS / Re: YatebTS and SMSC

« on: May 13, 2019, 02:21:28 AM »

Hi,

You could, but you need a little coding for it to happen.
You could deliver the SMS from the SMSC to YateBTS on smpp (yate has support for that), or an http header that pushes the message to yatebts as an yate message.

Monica

4

YateBTS / Re: VolteLab No packet

« on: March 11, 2019, 06:42:21 AM »

Hi,

I NiPC mode the labkit doesn't communicate with the MiniCore. The NiPC contains a basic implementation of the logic for  MSC/VLR, SMSC and HLR functions locally.
To see any communication between Labkit and Minicore use any of the other modes: roaming, dataroam or LTE ENB.
For the first two modes you can look at the SIP, GTP connection between the Labkit and the Minicore. SIP is for registration, calls and sms and GTP is for data.
In the LTE ENB you should look for S1AP connection.

5

YateBTS / Re: outgoing sip call unauth error

« on: February 04, 2019, 02:57:55 AM »

Hi,

I assume you didn't route the call correctly. If you route the call to a gateway to which you previously registered you need to route to: line/$called_nr and add parameter line=name_of_sip_account_from_accfile

https://docs.yate.ro/wiki/Accfile#Example_how_to_define_a_line

6

Yate IVR / Re: IVR with JavaScript or PHP

« on: January 30, 2019, 03:01:03 AM »

Hi,

Both options would work for the IVR, but if you want to use MsSQL or Oracle, Yate doesn't have support to connect to any of them (just mysql, postgresql, sqlite). To use MsSQL or Oracle you would need to use PHP because you can use the php functions to connect to any of the two databases. From Javascript on only have access to the databases defined in Yate's configuration files.

7

YateBTS / Re: Message Identifier?

« on: January 09, 2019, 07:35:29 AM »

To enable message sniffer from telnet:

https://docs.yate.ro/wiki/Debugging_and,_or_Investigation_of_messages

Then to increase debug level and see GSM messages type in telnet command:

debug ybts level 10
debug mbts level 10

If it's too much information then use level 9.

8

YateBTS / Re: Message Identifier?

« on: January 08, 2019, 07:51:57 AM »

Please post a telnet capture with GSM / yate internal messages to make sure I understand what you need to modify.

9

Yate based projects / Re: Where can I find the javascripts on YateBTS?

« on: January 07, 2019, 02:47:56 AM »

Hi,

Yes, you need to add it to javascript.conf located with the other configuration files.
Then you should restart yate.

To check the script is running connect to with telnet:
telnet 0 5037
and then type "javascript"

You should get a list of the .js scripts running. Example:

bts_config = /usr/share/yate/scripts/bts_config.js
api_control = /usr/share/yate/scripts/sdr_control.js
calibrate = /usr/share/yate/scripts/calibrate.js
eliza = /usr/share/yate/scripts/eliza.js
roaming = /usr/share/yate/scripts/roaming.js

10

YateBTS / Re: Message Identifier?

« on: January 07, 2019, 02:36:42 AM »

Hi,

What do you mean be message identifier?

11

Yate based projects / Re: Where can I find the javascripts on YateBTS?

« on: November 12, 2018, 07:12:37 AM »

Hi Iqenas,

The .js files used by Yate/YateBTS are located in /usr/share/yate/scripts
The .conf files are in /etc/yate/sdr

Before doing any modifications please backup the content of the whole directory: both scripts and configurations.

YateBTS is an extension over Yate:
https://wiki.yatebts.com/index.php/About_YateBTS#YateBTS

In Labkit Yate runs as a service and is installed from packages. You can configure it from  /etc/yate/sdr  and add additional scripts in /usr/share/yate/scripts. It is quite rare for people to need to modify anything in the Yate code.  If you want to experiment with the C++ code of Yate you would need to download sources from svn, stop yate-sdr service and then run the downloaded version.
 

12

Installation from packets/SVN/.exe/AppStore / Re: setup stand-alone SMSC

« on: October 09, 2018, 04:57:14 AM »

Hi,

We offer YateSMSC if you want to buy it directly. I'm not sure that all the SS7 pieces needed for it are in the public release of Yate.
https://yatebts.com/products/yate-smsc-short-message-service-center/

You can use the contact options from the website.

13

YateBTS / Re: Problems MCC, MNC.

« on: September 14, 2018, 02:43:29 AM »

You can use the contact form or the chat feature on yatebts.com and talk to sales directly.

14

YateBTS / Re: Problems MCC, MNC.

« on: September 12, 2018, 04:18:48 AM »

Hi. Setting the network name is only available in the commercial version of YateBTS.

15

Yate based projects / Re: About mini cell network

« on: June 04, 2018, 05:43:18 AM »

You can do both scenarios.
The SIP server is installed by default when installing YateBTS. It will be used to route calls to the outside (outbound connection).
It's your choice what you want the "outside" to be:
* It can actually be PSTN connection (SIP gateway on the other side), and then you would have to modify the routing to enforce this. You can do this by modifying the nipc.js script or by some other module/script that chaches the call.route/call.execute message.
* or you can define the outside as your other sip server. In [outbound] you define a sip connection to it and all calls that can't be routed internally will be sent to that sip server