Messages

1

YateBTS / Re: SIM card for Yatebts

« on: November 12, 2014, 01:07:16 PM »

Howdy,

I don't have the LabKit, but I have wrote sims through YateBTS's web gui.
I have had success with the following sim types:

SuperSim
X-Sim
sysmocom's sysmoSIM-GR1

Hope that helps.

2

YateBTS / Re: Encryption with YateBTS and Milenage

« on: October 31, 2014, 09:54:24 AM »

Howdy,
The sim that I am writing to is a Sysmocom sysmoUSIM-GR1
Their official website says the Sims are mileage capable. I have even called them to confirm.
http://www.sysmocom.de/products/programmable-sysmousim-gr1-sim-card

I wrote the sim manually and with the NIB interface. With the latest attempt, I wrote via the NIB.
Attached is the screenshot of the write.

I attached the log of the attempted attachment.
To simplify, I deleted the logs before attempting to connect.



As always, Thank you for your time and any assistance.

3

YateBTS / Encryption with YateBTS and Milenage

« on: October 29, 2014, 03:39:30 PM »

Howdy,
I had a quick question about Encryption and the use of Milenage.
According to http://wiki.yatebts.com/index.php/Network_in_a_Box Milenage is supported on YateBTS
Looking at NIB web interface, BTS Configuration/GSM/GSM Advanced there is an option for Cipher.Encrypt

In the past I have been unable to get either of these feature to work.
128 Authentication definitely works, but I never could get it to encrypt.
When trying to get a Milenage sim to authticate, I would constantly get a Reject cause 20 (MAC failure)

Before I start running experiments, I thought I would just ask on the forums first.
Are these two features fully functional? Are there additional steps to that I need to make so they will become functional?

As always, Thank you for your time and any assistance.

4

YateBTS / Re: Help with Incoming calls

« on: October 29, 2014, 11:01:46 AM »

Thank you again.
After a little more research and looking at the logs, I have a much better understanding of how everything works.
I was able to configure everything properly.
I was able to have multiple incoming calls happening simultaneously and they routed properly. 
This is all very exciting and I appreciate all the help.
I'll be moving on to the next issue and probably will be posting shortly.

5

YateBTS / Re: Help with Incoming calls

« on: October 27, 2014, 07:51:41 AM »

Thank you, that is helpful.

So, what I understand:
I will need to own a real-world-number. I can purchase this from a sip provider.
My machine that is running YateBTS will need a static IP. I will tell the sip provider to send the phone calls to the IP.
The phone that I connect to YateBTS will have the same phone number as the one I purchased from the sip provider.

What I am still unclear on:
The sip provider will send the Sip call to my machine with a static IP.
What configuration do I need to set to get that information to Yate/YateBTS.

Once everything is done, I am trying to get a new-world phone (such as a phone on AT&T) to call the phone number that I purchase from a sip provider, and have a phone connected to YateBTS receive the call.

Thank you again for your response and time.

-----------------------------------------------------------------------------------------
Update:
I have a real phone number from a sip provider. I have a static IP.
The phone that connects to YateBTS, I set the Msisdn to be the real phone number that I have purchased.
I have the server that I am using for outbound calls just sending me the inbound information.
In the NIB GUI, in the "Outgoing" tab, I have the username stated as 1000.
Because of this all incoming calls are now going to 1000.
If I set a phone's short number to 1000 that phone will receive the call.
If I set multiple phone's short numbers to be 1000, than which ever phone is physically higher on the "List subscribers" chart will receive the phone call.
(It appears Msisdn is never taken into consideration)

I want to be able to have multiple real phone numbers attached to my YateBTS.
Is there something I am missing? Do I need to tweak with how my sip server passes the information to Yate?
Any help or guidance is highly appreciated.
Thank you
 

6

YateBTS / Help with Incoming calls

« on: October 18, 2014, 12:12:02 AM »

Howdy,

I just did a fresh install of Yatebts from SVN 2 days ago.
I noticed that writing sims through the NIB is now fully functioning.

I have sims written and authenticating with 128.
I can preform outbound calls to the real world.

I am now trying to figure out how I can go the other way.
I have looked around, but I am not finding documentation on receiving inbound calls with YateBTS.
Can anyone help me/point me in the right direction.

From what I know, I will need a real phone number and I will have to insert it into the YateBTS HLR.

Thank you

7

YateBTS / Re: Help with Outbound phone calls voice cutting out.

« on: September 26, 2014, 10:31:24 AM »

Howdy,

I could post a screen shot if you wanted, but I would have to black out basically everything.
Sorry, I can't publicly share my server.

To make outbound calls though, once local calls worked, I only manipulated The "Outgoing" tab in the NIB.
I picked the protocol to be sip and I expanded it to the Advance version.
I filled in a Username/Password/Server/Outbound
My transport is UDP
I checked the boxes by Enabled/Match port/Match user

I hope that helps you.
 

8

YateBTS / Rejection Cause

« on: September 15, 2014, 12:07:21 PM »

Howdy,

I currently have a hand full of test phone connected to my YateBTS that I inserted through the "Add subscriber" function in the NIB.
I am not using Regexp.
Looking at my yate logs, it looks like that YateBTS is using rejection cause 2 "IMSI unknown in HLR"
Is there any where to set/change the rejection cause through NIB or another config file?
I looked through the NIB but I could not find the option. It is always possible that I am just overlooking it.

Thank you for your time and any help.

9

YateBTS / Encryption with YateBTS

« on: September 11, 2014, 02:25:51 PM »

Howdy,

I was wondering if y'all have a way of 100% confirming that everything is encrypted with YateBTS.

I know for sure that the comp128 is working. I have programmable sims that I used pysim to write.
I inserted the subscribers through the NIB interface. I used proper Ki values and marked the Sims as 2G.
I can look through the logs and see the proper SRES and KC values on both sides.
I can send SMS messages and make voice calls (internal/external) with no problem.
I have toggled on the cipher.Encrypt inside Nib/Gsm/Gsm Advanced

Then using additional outside equipment, I can see that everything still seems un-encrypted.
I see that on http://wiki.yatebts.com/index.php/About_YateBTS it states that YateBTS A51/A53 support.

Is there something I am missing/additional I need to do to turn on the encryption?
Is there any external tools used to guarantee that encryption is in place that y'all have used?

Thank you very much for your time and any help.

10

YateBTS / Re: Help with Outbound phone calls voice cutting out.

« on: September 10, 2014, 09:23:30 AM »

Howdy,

Sorry, I cannot share my gateway.
It is a private server that I did not set up.

11

YateBTS / Re: Help with GSM phones connecting

« on: September 02, 2014, 11:01:30 PM »

I just wanted to confirm.
Pysim is a bit of an adventure to get working, but once you do, everything is fairly straight forward.
I just do all of the commands through the command line.
I have been using pysim to read/write both sims and usims.
Both of which I have connected to Yatebts and made real world phone calls with.

Fair warning though, I have had to work my way though many card readers.
The only card reader that I have that will read/write all my different sims is the Hid Omnikey 3121.

I have looked around and I do not know of any alternatives to using pysim.
If anyone knows of one, please let me know.

Thank you

12

YateBTS / Re: Help with Outbound phone calls voice cutting out.

« on: August 21, 2014, 06:03:15 PM »

Took me a little longer than expected to get back to Yate.
I have upgraded to Yate 4 and all voice problem seem to be solved.
I was able to sustain a 30 min phone call to a real-world-phone without the audio ever cutting out.
Thank you again for your time.

13

YateBTS / Re: Help with Outbound phone calls voice cutting out.

« on: August 04, 2014, 01:39:16 PM »

Howdy,

Currently I am making the rounds on similar BTS (such as OpenBTS) programs for comparison reasons.
I did save the state of my machine as it was with the logs that I already submitted.
I will go back to that state and update to YateBTS 4 to see if that solves the problem.
Unfortunately it will be about a week before I will get the chance to loop back to YateBTS.

YateBTS is definitely my front runner for BTS  programs, but I still need to make some comparisons.
No matter what, I will reflash my machine to the saved state, upgrade to 4, and post the results.

I really appreciate all the help.

14

YateBTS / Re: Help with Outbound phone calls voice cutting out.

« on: July 31, 2014, 08:30:10 AM »

My bad.
Thank you for pointing out how to do better logs.

To start yatebts i used:
sudo yate -sd -vvvvv -Dt -l /var/log/yate.log

after starting I then ran:
telnet 127.0.0.1 5038
sniffer on

I connected a phone. Made a real-world-call.
After the sound cut out, I ended the call.
I waited a few seconds and then ended the log.

Thank you again for your time.

15

YateBTS / Re: Help with Outbound phone calls voice cutting out.

« on: July 31, 2014, 07:30:16 AM »

Howdy,

Attached is a log that I just created. I mildly edited it by replacing some of the numbers with #.
I erased my previous log.
Booted yatebts and connected a phone to it.
Made an outbound real world call and then I ended the log once the real-world-phone stopped receiving sound.
This particular test lasted longer than normal.
It took 2.5 minutes before the sound cut out.

I will have to upgrade to Yatebts 4 later as I must now temporary refocus my project.
I do plan to come back to YateBTS soon though.

I am mainly wondering if I am suppose to to be able to maintain prolonged real-world-phone-calls or if the public code has some thing built in to limit them.