16
YateBTS / Re: Can't installing yate on rasspberry Pi3
« on: September 25, 2018, 06:21:42 AM »
Please post a log and configuration files.
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.
17
YateBTS / Re: Can't installing yate on rasspberry Pi3
« on: September 25, 2018, 01:24:16 AM »
Did you 'make install' for YateBTS?
If you did and the files are stil not there ( i dont think subscribers.conf is automatically installed), you can always copy them from the source or create them.
See https://wiki.yatebts.com/index.php/Javascript_NiPC
If you did and the files are stil not there ( i dont think subscribers.conf is automatically installed), you can always copy them from the source or create them.
See https://wiki.yatebts.com/index.php/Javascript_NiPC
18
YateBTS / Re: Can't installing yate on rasspberry Pi3
« on: September 24, 2018, 01:38:55 AM »
There is a mismatch between your YATE version and the OpenSSL version. The OpenSSL API changed and the fix for it was committed to YATE in June 2018.
The YATE version you are trying to use from that repository is more than a year old.
You can get the up to date versions of Yate and YateBTS from the official repositories (those git repositories were just a clone of the SVN):
Make sure to clean up the previous installation.
The YATE version you are trying to use from that repository is more than a year old.
You can get the up to date versions of Yate and YateBTS from the official repositories (those git repositories were just a clone of the SVN):
Code: [Select]
svn co http://voip.null.ro/svn/yate/trunk yate
svn co http://voip.null.ro/svn/yatebts/trunk/ yatebtsMake sure to clean up the previous installation.
19
YateBTS / Re: Can't installing yate on rasspberry Pi3
« on: September 19, 2018, 01:25:08 AM »
Please state YATE version and what version of OpenSSL you have on the raspberryPi.
Also please tell us what is the detected version of OpenSSL by the configure script of YATE.
This looks like a mismatch between what is detected by the configure script for OpenSSL and what is actually installed. Maybe you updated OpenSSL and did not run configure again when compiling YATE?
Also please tell us what is the detected version of OpenSSL by the configure script of YATE.
This looks like a mismatch between what is detected by the configure script for OpenSSL and what is actually installed. Maybe you updated OpenSSL and did not run configure again when compiling YATE?
20
Yate users hangout place / Re: Copy All Parameters from Handled message
« on: September 05, 2018, 06:20:44 AM »
notify->copyParams(*m) is what you are looking for.
Please see: http://yate.null.ro/docs/api/TelEngine__NamedList.html#ref17
Please see: http://yate.null.ro/docs/api/TelEngine__NamedList.html#ref17
22
YateBTS / Re: Can't build yatebts. Error at make
« on: January 25, 2018, 02:58:22 AM »
Hi,
This is an issues that happens when you try to compile YateBTS with gcc-6.
Please see: http://yate.null.ro/mantis/view.php?id=416 , where a patch that should solve this compilation error is provided.
Apply the patch and then retry recompiling.
And MSInfo is a file that contains classes that keep information about a MS (Mobile Station). It's not related with Microsoft.
This is an issues that happens when you try to compile YateBTS with gcc-6.
Please see: http://yate.null.ro/mantis/view.php?id=416 , where a patch that should solve this compilation error is provided.
Apply the patch and then retry recompiling.
And MSInfo is a file that contains classes that keep information about a MS (Mobile Station). It's not related with Microsoft.
23
Linux / Re: Can't find or build yate client in debian 9
« on: September 12, 2017, 02:12:03 AM »
If you are building from sources, you first need to run './autogen.sh' in order to generate configure from configure.ac.
24
Linux / Re: Can't find or build yate client in debian 9
« on: August 25, 2017, 06:28:12 AM »
Please post a log of configure and build steps.
25
YateBTS / Re: Handset Gets Rejected When connecting to BTS but is not listed as Rejected
« on: June 29, 2017, 01:45:54 AM »
Does the type of the SIM match what you configured (imsi_type=2g)? What authentication algorithm does the SIM support? NIB only supports compV1. Maybe there is a mismatch between authentication algorithms.
Regarding, ki=*, you need to restart Yate after configuring that.
Regarding logs, you can always take pictures of the screen and attach them.
Anyway, if you don't want authentication, you can always configure in [general] section of subscribers.conf the regexp setting. This will allow registration of UEs that match the regular expression you set. Something like regexp=^00101 will allow registration for all IMSIs that start with 00101. Please keep in mind that authentication will not take place anymore.
Make sure to uncomment the regexp section and also comment the section regarding particular IMSIs.
Regarding, ki=*, you need to restart Yate after configuring that.
Regarding logs, you can always take pictures of the screen and attach them.
Anyway, if you don't want authentication, you can always configure in [general] section of subscribers.conf the regexp setting. This will allow registration of UEs that match the regular expression you set. Something like regexp=^00101 will allow registration for all IMSIs that start with 00101. Please keep in mind that authentication will not take place anymore.
Make sure to uncomment the regexp section and also comment the section regarding particular IMSIs.
26
YateBTS / Re: Handset Gets Rejected When connecting to BTS but is not listed as Rejected
« on: June 28, 2017, 05:47:04 AM »
Please post a log starting from LocationUpdateRequest and please do not cut out parts of it. If you want to hide the IMSI and Ki fine. Just the piece of log from where it rejects the authentication is irrelevant if I can't see what happened before.
Anyway, the piece of log points to a mismatch in results obtained by the phone and the network when doing authentication algorithm on the same data.
You could also try again with ki=*
Anyway, the piece of log points to a mismatch in results obtained by the phone and the network when doing authentication algorithm on the same data.
You could also try again with ki=*
27
YateBTS / Re: Handset Gets Rejected When connecting to BTS but is not listed as Rejected
« on: June 27, 2017, 01:51:31 AM »
Ok, so at one point gsm_auth.sh was renamed to nib_auth.sh
So if you have a YateBTS older than SVN revision 605, you need to look for and set 'gsm_auth=' in extmodule.conf. That setting is all that is needed.
If you have something newer than SVN revision 605, you need to look for and set 'nib_auth=' in extmodule.conf.
Posting a log with sniffer enabled might help. Also posting the configuration files. Also please post the YateBTS version and the NIB version.
So if you have a YateBTS older than SVN revision 605, you need to look for and set 'gsm_auth=' in extmodule.conf. That setting is all that is needed.
If you have something newer than SVN revision 605, you need to look for and set 'nib_auth=' in extmodule.conf.
Quote
Note, does it matter that I am using 2g here when configuring the IMSI's in the configuration files?If the SIM is of type 2G it should be ok. As far as I know, if it's 3G (USIM), you also need to set op
Posting a log with sniffer enabled might help. Also posting the configuration files. Also please post the YateBTS version and the NIB version.
28
YateBTS / Re: Handset Gets Rejected When connecting to BTS but is not listed as Rejected
« on: June 23, 2017, 04:19:41 AM »
The phone seems to be rejected because it cannot be authenticated.
A complete log with sniffer enabled would be helpful.
Anyway, to check that the issue is authentication of the IMSI please check that:
1. you have the nib_auth.sh script loaded (command in telnet is 'external info');
2. you have setup the right ki, op and imsi type in subscribers.conf for the IMSI you test with. Also, if you dont have the ki, you could set ki=* to skip authentication.
A complete log with sniffer enabled would be helpful.
Anyway, to check that the issue is authentication of the IMSI please check that:
1. you have the nib_auth.sh script loaded (command in telnet is 'external info');
2. you have setup the right ki, op and imsi type in subscribers.conf for the IMSI you test with. Also, if you dont have the ki, you could set ki=* to skip authentication.
29
Yate bugs / Re: Routing Area Identification Not Set Correctly
« on: April 28, 2017, 04:08:05 AM »
Could you install again with current sources?
You would need to follow:
http://wiki.yatebts.com/index.php/Prerequisites
http://wiki.yatebts.com/index.php/Installing
After that, post if you have still have the issue.
You would need to follow:
http://wiki.yatebts.com/index.php/Prerequisites
http://wiki.yatebts.com/index.php/Installing
After that, post if you have still have the issue.
30
Yate bugs / Re: Routing Area Identification Not Set Correctly
« on: April 28, 2017, 02:58:14 AM »
From where did you get this information then?
Code: [Select]
YATE 5.5.1-devel1 r
yatebts Release 5.0.1 formal build date Jun 11 2016 rev