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 - SugarCakes

Pages: [1]
1
YateBTS / Re: Eliza SMS Issue - No Response
« on: August 31, 2015, 08:53:26 AM »
No problem!

It's a small shame, because the software works really well with Ettus kit using the Transceiver in the old package! (Just sad I can't update the software now)

I might look at buying a blade-rf though if some of the bugs get ironed out :)
Some big plans for the kit!

2
YateBTS / Re: USRP x310, no connection to transceiver
« on: August 31, 2015, 08:42:19 AM »
If you look at the svn history you'll see Yate made a brand new transceiver module, but it looks like this is for the blade-rf only.

What really sucks is blade-rf doesn't really work with OpenBTS.

Try the package version (make sure you have libboost-dev and pkg-config installed)
It should work ;)

3
YateBTS / Calls to 99991001 and other yate tests do not work.
« on: August 31, 2015, 08:26:26 AM »
As discussed with Oana in IRC.

Using standard regexroute.conf (the same one as in the sample) calls from yatebts cell's to numbers such as 99991001 do not work.

Log with Sniffing is here: http://pastebin.com/TnVFYpam

Thanks!

4
YateBTS / Re: GSM.Identity.Shortname ignored by Cell (works in OpenBTS)
« on: August 31, 2015, 08:24:47 AM »
Ahh ok, thanks for explaining! Maybe the web UI could be updated to reflect this.

Is it not possible for yatebts to do this in the sameway openbts does (I thought OpenBTS was opensource)?

5
YateBTS / Re: Eliza SMS Issue - No Response
« on: August 31, 2015, 08:23:18 AM »
Hi Marian

Thank you for your quick reply :)
Yes this happens repeatedly and with different phone types.

Currently tested with iPhone 4/5s/6, nokia 3310 and Blackberry 8310 and Q10.

Thank you for investigating!
Hope you don't mind me raising all these issues, I would help fix if I could debug the code.

Unrelated, if it is fixed I don't think I can upgrade because yatebts no longer works with Ettus equipment :( are there any plans to let it work again like it used too?http://forum.yate.ro/index.php?topic=495.0

Thanks!

6
YateBTS / Re: USRP x310, no connection to transceiver
« on: August 31, 2015, 08:20:34 AM »
Unfortunately it doesn't look like USRP devices work with the latest svn version.
This is because Transceiver52M is missing from the package.

If you download the "package" version of yatebts, then these devices still work :)
However you can not upgrade :(

I have asked about this here: http://forum.yate.ro/index.php?topic=495.0

7
YateBTS / Re: Eliza SMS Issue - No Response
« on: August 31, 2015, 07:16:12 AM »
I can't seem to add attachments so here is a link to the log:

http://pastebin.com/WEMTb7eu

In the log you can see the cell successfully auths to the BTS
A GPRS exchange occurs.
An SMS is sent to Eliza and a response is received.
A 2nd SMS is sent to Eliza and this fails.

Also I typed the previous message which is why I omitted the date :) nothing intentional, just saving time!

Many thanks!

8
YateBTS / Re: Dial tone can't hear
« on: August 31, 2015, 06:55:11 AM »
Super thanks for the reply.

To get Yate to use regexroute.conf do you have to remove the line
[general]
routing=welcome.js

from javascript.conf

I ask because I can see that regexroute.conf has some test numbers in such as 99991001, however when I try to ring these I get a call failed message.

Thanks

9
YateBTS / Re: Dial tone can't hear
« on: August 30, 2015, 09:49:05 PM »
Marian,

Could you please explain how you would do this.
I think you suggested doing:

^1$=fork;callto.1=tone/ring;callto.2=sip/sip:1@host1;callto.3=h323/2@host2;callto.4=|;\
 callto.5=sip/sip:3@host3;stoperror=busy;maxcall=20000;\
 callto.1.fork.calltype=persistent;callto.1.fork.autoring=true;\
 callto.1.fork.automessage=call.progress

But where do you put this file? and where are the tone files from?

The webpage you mention also has:

Providing just ringback tone
Use the fork.fake to set the fake early media. This is an easy way to provide custom ringback.
^1$=fork sip/sip:1@host1;fork.fake=tone/ring

Again where would you put this if you wanted it to happen.
We have good progress with our network but a dial tone is very important for us to check calls are making.

Thanks!

10
YateBTS / Re: Enabling 911/112
« on: August 30, 2015, 06:12:26 PM »
Access flags are set in the source code, they can be altered by editing file: GSML3RRElements.h and then re-compiling the code.

Not sure why YateBTS removed this when OpenBTS has it as an option....


/** RACH Control Parameters GSM 04.08 10.5.2.29 */
/** Default constructor parameters allows all access. */
   L3RACHControlParameters()
      :L3ProtocolElement()
   {
      // Values ditected by imnplementation are hard-coded.
      mRE=1;
      mCellBarAccess=0;
      // Configurable values.
      mMaxRetrans = gConfig.getNum("GSM.RACH.MaxRetrans");
      mTxInteger = gConfig.getNum("GSM.RACH.TxInteger");
      mAC = 0x0400; //NO EMERGENCY SERVICE - kurtis
   }

Set the bit in bold to 0x0000

Once changed the network will now advertise that it CAN handle emergency calls (so make sure it really can)

11
YateBTS / GSM.Identity.Shortname ignored by Cell (works in OpenBTS)
« on: August 30, 2015, 06:06:09 PM »
Hi,

It seems that GSM.Identity.ShortName is having no impact.

The same cellphone does display the correct shortname when set using OpenBTS5, therefore I think the issue probably lies with YateBTS and not the cellphone.
YateBTS seems more stable than OpenBTS (where GPRS fails etc, but small issues like this could do with tidying!)

Could this be looked into?

Thanks.

12
YateBTS / New Transceiver doesn't work with non-rfblade devices
« on: August 30, 2015, 06:00:31 PM »
I know that officially only the Rfblade is supported.

However the "package" currently available for download has Transceiver 52M which works with Ettus equipment.

This has been removed in the SVN which means even when setting ./transceiver-uhd devices such as the Ettus N210 do not work.

Could this be looked into?

13
YateBTS / Re: Eliza SMS Issue - No Response
« on: August 29, 2015, 01:56:08 PM »
Can't seem to attach log so here goes:
Primitive: ConnRelease
Info: 0
Connection: 5
-----
DATE: <ybts:INFO> MT SMS 'ybts/sms/1' to (some hex) TMSI=007b0001 IMSI= $
DATE <nib:INFO> Could not deliver sms from imsi nib_smsc to number 117752717
DATE <ybts:INFO> MT SMS 'ybts/sms/2 to (some hex) TMSI=007b0001 IMSI=
DATE <ybts-signalling:INFO> Sending [0x2654a30]
----
Primitive: EstablishSAPI
Info: 3
Connection :4
----
DATE: <ybts:INFO> MT SMS 'ybts/sms/2' to (some hex) TMSI=007b0001 IMSI= $
DATE <nib:INFO> Could not deliver sms from imsi nib_smsc to number 117752717
DATE <ybts:INFO> MT SMS 'ybts/sms/3 to (some hex) TMSI=007b0001 IMSI=
DATE <ybts-signalling:INFO> Sending [0x2654a30]

One other thing is a message which I can't quite remember but something along the lines of " failure = postDelayDial"

UPDATE: Eliza responded once, but it looks like a one off :S
GPRS is more stable when I edited the N210 rxgain to something higher around 25, to make the noise closer to -68/-70

14
YateBTS / Eliza SMS Issue - No Response
« on: August 29, 2015, 01:49:46 PM »
Hi,

Just setup yateBTS, all going ok so far (on the whole).
  • I can make cell to cell calls.
  • Both cells can exchange SMS.
  • Both cells can call David.

Issues:
  • No one can text Eliza.....
    Error attached in screenshot, but message is Droped sms from imsi nib_smsc to number 117752717.
  • The GPRS seems very intermittent.

Would appreciate help, especially with SMS issue.

Cheers!
Eski

Pages: [1]