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

Pages: [1]
1
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 16, 2015, 01:29:44 PM »
Hello,

I'm actually in Quebec (Canada -:) )... so the filter from Miniciruit would be best for me at this time.

If you get that value with dummy load, then there are something wrong in either in the mbts module or in the BladeRF setting. It should be in the -100 area...

Super, I will build the PCB too. I do my pcb here: https://oshpark.com/. It takes time at a very low cost! Gerber or Eagle files work fine.

I see, that you are from the RF field... What I really want to do is to build a Spectrum Analyzer with Tracking generation for Antenna matching work (WiFi 2.4 Ghz band). Do you have a PCB for tracking generator???

Thank you very much!


2
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 15, 2015, 01:46:06 PM »
Hi,

No, I didn't try that DC calibration. I asked if I could get the filters YateBTS delivered with their kit... I think the board is well calibrated but the filter is really mandatory as it is written in the kit manual... http://wiki.yatebts.com/index.php/File:YateBTSLabKit_QuickGuide.pdf

Do you know this kind of filter? How could I get one such filter? The cavity filter is too big...

Vic

3
YateBTS / European / Amrican Filters
« on: April 15, 2015, 09:18:03 AM »
Hello All,

Is it possible to order the "European / Amrican Filters" depicted in the YateBTSLabKit_QuickGuide.pdf or it comes only with the kit?

Thanks,

Victor

4
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 14, 2015, 02:29:51 PM »
with 2Dbi Antenna SMA male (no filter) oriented in 90 deg:
mbts noise
noise RSSI is -13 dB wrt full scale
MS RSSI target is -50 dB wrt full scale

mbts rxgain
current RX gain is 0 dB

I need a filter before I continue with my test...

5
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 13, 2015, 03:11:49 PM »
Hello,

I see... I have seen this thread @ Nuand: https://nuand.com/forums/viewtopic.php?f=4&t=3578&hilit=http%3A%2F%2Fwww.w1ghz.org

Could you suggest  a low cost (but medium quality -:) ) Amplifier + duplexer for the 900 Mhz band? (max 1 or 2w)

I'm looking for a "safe" solution for the BladeRF board.

Thanks,

Vitia

6
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 12, 2015, 02:45:11 PM »
Hi,

I mean about this test:

http://wiki.yatebts.com/index.php/Calibrate_the_radio_board

1)telnet 127.0.0.1 5038

2) then run the folloing commands

mbts noise

----
and
----

mbts rxgain

(see my last post... the screenshots show, the card is OK)

Which type / gain of antenna are you using?

Vitia

7
YateBTS / Re: NIB Test
« on: April 11, 2015, 08:40:39 PM »
YATE source:

yate-svn$ svn info
Path: .
Working Copy Root ....projects/bladeRF-gnuradio/yate-svn
URL: http://voip.null.ro/svn/yate/trunk
Relative URL: ^/trunk
Repository Root: http://voip.null.ro/svn/yate
Repository UUID: acf43c95-373e-0410-b603-e72c3f656dc1
Revision: 5966
Node Kind: directory
Schedule: normal
Last Changed Author: paulc
Last Changed Rev: 5966
Last Changed Date: 2015-04-07 10:07:14 -0400 (Tue, 07 Apr 2015)

====

YATEBTS source:

yatebts-svn$ svn info
Path: .
Working Copy Root Path: .../projects/bladeRF-gnuradio/yatebts-svn
URL: http://voip.null.ro/svn/yatebts/trunk
Relative URL: ^/trunk
Repository Root: http://voip.null.ro/svn/yatebts
Repository UUID: 26ef948f-17ed-0410-91a8-c94bd273f071
Revision: 474
Node Kind: directory
Schedule: normal
Last Changed Author: oana
Last Changed Rev: 474
Last Changed Date: 2015-04-09 05:31:03 -0400 (Thu, 09 Apr 2015)

====

BLADERF source:

bladeRF-git$ git describe
2014.09-rc2-301-g0295340

bladeRF> version

  bladeRF-cli version:        1.1.2-git-0295340
  libbladeRF version:         1.2.1-git-0295340

  Firmware version:           1.8.0
  FPGA version:               0.1.2

====

Frist question: should I use the bladeRF lib from the yastbts repo or can I use the recent bladeRF source from Nuand's github?

My test shows that SIM card matter, even if I was running with "Regexp:.*".

For those who are using BladeRF card: what is the gain of the antenna you are using?

====

mbts noise
noise RSSI is -13 dB wrt full scale
MS RSSI target is -50 dB wrt full scale

mbts rxgain
current RX gain is 0 dB

"mbts" indicates a high noise level. Jon from BladeRF pointed me to GQRX to use as a testing tool, and the results show that the card works fine. EGSM900 / ch.100 (used with yatebts, no interference) and GSM850 / ch.128/129 (from a nearby tower).

Which "noise" value do you get at a rxgain=0?



thank you,

Vitia,

8
YateBTS / Re: YateBTS and bladeRF running problem
« on: April 11, 2015, 10:59:13 AM »
Hello,

I was there too, but the "NIB" will set a new entries in that ybts.conf file:

[transceiver]
;Path to the transceiver relative to where MBTS is started.
;Should be one of: ./transceiver-bladerf ./transceiver-rad1 ./transceiver-usrp1 ./transceiver-uhd.
;Defaults to ./transceiver
Path=./transceiver-bladerf

Pls, refer to http://wiki.yatebts.com/index.php/Javascript_NIB

I would like to exchange with you regarding "noise" on the bladerf afterwad... I have a half running yatebts/bladerf x115 (sms ok, phone registration ok, but unstable...)

Good luck and please report your status...

Vitia



9
YateBTS / Re: NIB Test
« on: April 10, 2015, 09:48:01 AM »
Hi,

libgsm1-dev was missing... I have now the IVR replying (one per restart...) and notification for sms non delivery are working... But:

I scan GSM900 & GSM850 with kalibrate-bladerf, I got only GSM850 in my area so I'm using GSM900/chan 50. The noise level is un-tunable...

mbts noise
noise RSSI is -13 dB wrt full scale
MS RSSI target is -50 dB wrt full scale

mbts rxgain
current RX gain is 0 dB

Question: Now, I'm using the bladerf library and fx3 from the nuand github. Is it ok?

I will send to Nuand osmocom_fft plot now and waiting for their reply.

Vitia









10
YateBTS / Re: NIB Test
« on: April 09, 2015, 12:50:39 AM »
Hello,

Still need helps.... I got a Win 8.1 mobile phone registered and recieve a sms from yatebts. the windows ohone can send sms to another registered phone (not vis versa).

I have one  question related to media handling: do I miss some module during my install that caused " (No DataTranslator created for 'mulaw' -> 'gsm')"?


<PhysicalInfo>TA=2 TE=0.469 UpRSSI=-2 TxPwr=33 DnRSSIdBm=-111 time=1428561378.267</PhysicalInfo>
-----
20150409063618.491826 <ybts-signalling:INFO> Received [0xb51d70]
-----
Primitive: MediaStarted
Info: 0
Connection: 1
-----
20150409063618.491841 <ybts-signalling:ALL> Connection 1 traffic channel set succeeded mode=1 [0xb51d70]
20150409063618.491867 <ybts/1:ALL> Got media started notification [0x7f6320002b20]
20150409063618.492263 <INFO> Could not classify call from 'TMSI007b0003', wasted 15 usec
20150409063618.492559 <welcome:INFO> Got call to welcome IVR.
20150409063618.512235 <wave:INFO> Play from wave file '/usr/local/share/yate/sounds/welcome.au'
20150409063618.512249 <wave/1:ALL> WaveChan::WaveChan(play) [0x7f630400a650]
20150409063618.512257 <wave:ALL> WaveSource::WaveSource("/usr/local/share/yate/sounds/welcome.au",0x7f630400a650) [0x7f630400a8d0]
20150409063618.522699 <ybts/1:NOTE> Answering now call ybts/1 because we have no targetid [0x7f6320002b20]
20150409063618.522712 <ybts/1:INFO> Call 'i0' changed state CallProceeding -> ConnectReq [0x7f6320002b20]
20150409063618.522743 <ybts-signalling:INFO> Sending [0xb51d70]
-----
Primitive: L3Message
Info: 0
Connection: 1

<CC>
  <TID TIFlag="true">0</TID>
  <Message type="Connect"/>
</CC>
-----
20150409063618.522802 <INFO> No DataTranslator created for 'mulaw' -> 'gsm'
20150409063618.522807 <WARN> DataTranslator::attachChain [0x7f630400a8d0] 'mulaw' -> [0x7f630400af10] 'gsm' failed
20150409063618.653278 <ybts-signalling:INFO> Received [0xb51d70]
-----
Primitive: L3Message
Info: 0
Connection: 1

<CC>
  <TID TIFlag="false">0</TID>
  <NSD>0</NSD>
  <Message type="ConnectAcknowledge"/>
</CC>
-----
20150409063618.653336 <ybts/1:INFO> Call 'i0' changed state ConnectReq -> Active [0x7f6320002b20]
20150409063630.528159 <ybts-signalling:INFO> Received [0xb51d70]
-----
Primitive: PhysicalInfo
Info: 0
Connection: 2

<PhysicalInfo>TA=0 TE=2.949 UpRSSI=1 TxPwr=33 DnRSSIdBm=-111 time=1428561390.038</PhysicalInfo>


 

11
YateBTS / Re: NIB Test
« on: April 07, 2015, 12:21:13 PM »
Hello,

I see, no news is bad news in a forum... Do I made something really abnormal?


Vitia

12
YateBTS / Re: NIB Test
« on: April 07, 2015, 09:36:13 AM »
Hello Folk,

I redo my install by following some tips I found in this forum (http://forum.yate.ro/index.php?topic=372.msg1098#msg1098), but I still not able to receive sms nor could I place a call to 333 and to another "NIB" extensions.

I clean up the old "installs" and start with the bladerf lib from http://voip.null.ro/tarballs/misc/bladeRF.tar.gz. Flash the board with firmware.img from the svn repo (Also load the hostedx115.rbf...). The firmware version is now 1.6.1...

I'm pretty sure, the issue is on the config or the operational setting of the bladeRF, juste because it seems all sip "traffic" are ok...


20150407052923.772342 <javascript:INFO> Parsed 'nib' script: /usr/local/share/yate/scripts/nib.js
20150407052923.774228 <NOTE> Failed to open config file '/usr/local/etc/yate/tmsidata.conf', using defaults (2: No such file or directory)
20150407052923.774390 <nib:INFO> Finished reading saved registered subscribers. Found 0 registered_subscribers.
20150407052923.774601 <nib:INFO> Checked that only NIB is enabled.
20150407052923.774637 <ALL> Rescanning handler list for 'engine.start' [0x7fff53a73000] at priority 100

....

20150407052924.569640 <cpuload:NOTE> Updating CPU core number from 1 to 4
20150407052924.619090 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 1
20150407052925.620371 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 2
20150407052926.620655 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 3
20150407052927.621826 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 4
ALERT 140344232867712 01:29:28.6 TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150407052928.623146 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 5
20150407052928.623189 <mbts:NOTE> TRXManager.cpp:293:sendCommandPacket: lost control link to transceiver
20150407052928.623204 <mbts:WARN> TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150407052928.681490 <mbts:NOTE> OpenBTS.cpp:145:startTransceiver: starting transceiver ./transceiver-bladerf w/ 1 ARFCNs and Args:
20150407052928.689072 <transceiver:NOTE> bladeRFDevice.cpp:110:open: Opened bladeRF serial=13d7b32e83118203e3e6db0b04de23bf firmware version 1.6.1 (1.6.1-git-053fb13-buildomatic)
20150407052929.172180 <transceiver:NOTE> Transceiver.cpp:68:Transceiver: running 1 ARFCNs with oversampling 4
Starting transceiver
20150407052933.648239 <transceiver:NOTE> bladeRFDevice.cpp:243:start: starting bladeRF in super speed mode...
20150407052933.655699 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T1
20150407052933.656943 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T2
20150407052933.657985 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T3
20150407052933.659217 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T4
20150407052933.659775 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T5
20150407052933.660560 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T6
20150407052933.661467 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T7
20150407052933.914541 <mbts:MILD> iputils.cpp:456:ip_finddns: GGSN: DNS servers: 127.0.1.1 0.0.0.0
RTNETLINK answers: File exists
20150407052934.283060 <transceiver:NOTE> Transceiver.cpp:274:pushRadioVector: dumping STALE burst in TRX->USRP interface cn=0 at 1:497921
MBTS ready
20150407052934.417997 <ybts-signalling:INFO> Received [0x1df0f10]
-----
Primitive: RadioReady
Info: 0
-----
20150407052934.418032 <ybts:NOTE> State changed Running -> RadioUp


IT SAID DESTINATION OFFLINE...

How the debug this?


Primitive: L3Message
Info: 0
Connection: 1

<MM>
  <SkipIndicator>0</SkipIndicator>
  <NSD>0</NSD>
  <Message type="LocationUpdatingRequest">
    <LocationUpdatingType>
      <FOR>false</FOR>
      <LUT>normal-location-updating</LUT>
    </LocationUpdatingType>
    <CipheringKeySequenceNumber>no-key/reserved</CipheringKeySequenceNumber>
    <LAI>
      <LAC>ffff</LAC>
    </LAI>
    <MobileStationClassmark>
      <RFPowerCapability>class4</RFPowerCapability>
      <RevisionLevel>GSM-phase2</RevisionLevel>
      <Flags>ES-IND</Flags>
    </MobileStationClassmark>
    <MobileIdentity>
      <IMSI>302500300094469</IMSI>
    </MobileIdentity>
  </Message>
</MM>
-----
20150407053043.655104 <ybts-signalling:ALL> Added connection (0x7fa6040020a0,1) [0x1df0f10]
20150407053043.655145 <ybts-mm:ALL> Handling LocationUpdatingRequest conn=1: ident=IMSI/302500300094469 LAI=_ffff [0x1df12f0]
20150407053043.655165 <ybts-mm:ALL> Added UE (0x7fa604002220) TMSI= IMSI=302500300094469 [0x1df12f0]
20150407053043.655178 <ybts-signalling:ALL> Connection 1 set UE (0x7fa604002220) TMSI= IMSI=302500300094469 [0x7fa6040020a0]
20150407053043.655256 <ybts-signalling:INFO> Sending [0x1df0f10]
-----
Primitive: L3Message
Info: 0
Connection: 1

<MM>
  <Message type="IdentityRequest">
    <IdentityType>IMEI</IdentityType>
  </Message>
</MM>
-----
20150407053044.125445 <ybts-signalling:INFO> Received [0x1df0f10]
-----
Primitive: PhysicalInfo
Info: 0
Connection: 1

<PhysicalInfo>TA=0 TE=-0.191 UpRSSI=-6 TxPwr=33 DnRSSIdBm=-111 time=1428384643.351</PhysicalInfo>
-----
20150407053044.125569 <ybts-signalling:INFO> Received [0x1df0f10]
-----
Primitive: L3Message
Info: 0
Connection: 1

<MM>
  <SkipIndicator>0</SkipIndicator>
  <NSD>1</NSD>
  <Message type="IdentityResponse">
    <MobileIdentity>
      <IMEI>355987050357630</IMEI>
    </MobileIdentity>
  </Message>
</MM>
-----
20150407053044.125735 <ybts:ALL> Started location updating thread for (0x7fa604002220) TMSI= IMSI=302500300094469 [0x7fa604002360]
20150407053044.126179 <nib:INFO> Got user.register for imsi='302500300094469', tmsi=''
20150407053044.126503 <nib:INFO> Allocated random number
20150407053044.128911 <nib:INFO> Registered imsi 302500300094469 with number 10094469
20150407053044.128973 <ybts:ALL> Location updating thread for (0x7fa604002220) TMSI= IMSI=302500300094469 terminated [0x7fa604002360]
20150407053044.128992 <ybts-mm:ALL> UE (0x7fa604002220) registered TMSI '' -> '007b0001', IMSI '302500300094469' -> '302500300094469' conn=1 [0x1df12f0]
20150407053044.129004 <ybts-mm:ALL> UE (0x7fa604002220) TMSI=007b0001 IMSI=302500300094469 register succeeded [0x1df12f0]
20150407053044.129127 <ybts-signalling:INFO> Sending [0x1df0f10]
-----
Primitive: L3Message
Info: 0
Connection: 1

<MM>
  <Message type="LocationUpdatingAccept">
    <LAI>
      <PLMNidentity>00101</PLMNidentity>
      <LAC>03e8</LAC>
    </LAI>
    <MobileIdentity>
      <TMSI>007b0001</TMSI>
    </MobileIdentity>
  </Message>
</MM>
-----
20150407053044.596150 <ybts-signalling:INFO> Received [0x1df0f10]
-----
Primitive: PhysicalInfo
Info: 0
Connection: 1

<PhysicalInfo>TA=3 TE=0.059 UpRSSI=-5 TxPwr=33 DnRSSIdBm=-111 time=1428384644.358</PhysicalInfo>
-----
20150407053044.596251 <ybts-signalling:INFO> Received [0x1df0f10]
-----
Primitive: L3Message
Info: 0
Connection: 1

<MM>
  <SkipIndicator>0</SkipIndicator>
  <NSD>0</NSD>
  <Message type="TMSIReallocationComplete"/>
</MM>
-----
20150407053044.596289 <ybts-signalling:ALL> Releasing connection (0x7fa6040020a0,1) [0x1df0f10]
20150407053044.596311 <ybts-signalling:INFO> Sending [0x1df0f10]
-----
Primitive: ConnRelease
Info: 0
Connection: 1
-----
20150407053046.261966 <ybts-signalling:INFO> Received [0x1df0f10]
-----
Primitive: PhysicalInfo
Info: 0
Connection: 2

<PhysicalInfo>TA=0 TE=3.020 UpRSSI=-4 TxPwr=33 DnRSSIdBm=-111 time=1428384645.961</PhysicalInfo>
-----
20150407053046.262152 <ybts-signalling:INFO> Received [0x1df0f10]
-----
Primitive: L3Message
Info: 0
Connection: 2

<MM>
  <SkipIndicator>0</SkipIndicator>
  <NSD>0</NSD>
  <Message type="IMSIDetachIndication">
    <MobileStationClassmark>
      <RFPowerCapability>class4</RFPowerCapability>
      <RevisionLevel>GSM-phase2</RevisionLevel>
      <Flags>ES-IND</Flags>
    </MobileStationClassmark>
    <MobileIdentity>
      <TMSI>007b0001</TMSI>
    </MobileIdentity>
  </Message>
</MM>
-----
20150407053046.262175 <ybts-signalling:ALL> Added connection (0x7fa604002390,2) [0x1df0f10]
20150407053046.262192 <ybts-signalling:ALL> Releasing connection (0x7fa604002390,2) [0x1df0f10]
20150407053046.262213 <ybts-signalling:INFO> Sending [0x1df0f10]
-----
Primitive: ConnRelease
Info: 0
Connection: 2
-----
20150407053046.262253 <ybts-mm:INFO> Detached UE (0x7fa604002220) TMSI=007b0001 IMSI=302500300094469 [0x1df12f0]
20150407053046.266264 <nib:INFO> Finished onUnregister imsi 302500300094469
20150407053054.052272 <nib:INFO> Did not deliver sms from imsi nib_smsc to number 10094469 because destination is offline. Waiting 5 minutes before trying again.
20150407053055.895599 <ybts-signalling:INFO> Received [0x1df0f10]
-----

I attache the full log and configs and share directory and hope that someone will help me with this...

Thanks













13
YateBTS / NIB Test
« on: April 04, 2015, 09:00:48 AM »
Hello,

I need helps to resolve my setup issue: unable to perform any of the test described in the NIB using one successfully registered phone (via regex: .*).
The config folder and the log are in the attachment.


OS: Ubuntu 14.04, 64bit,  3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

gcc version 4.9.2 (Ubuntu 4.9.2-0ubuntu1~14.04)
yate-5.4.2-1.tar.gz
yate-bts-4.0.2-1.tar.gz

======================================================================================================
bladeRF> info

  Serial #:                 13d7b32e83118203e3e6db0b04de23bf
  VCTCXO DAC calibration:   0x91b1
  FPGA size:                115 KLE
  FPGA loaded:              yes
  USB bus:                  4
  USB address:              2
  USB speed:                SuperSpeed
  Backend:                  libusb
  Instance:                 0

bladeRF> version

  bladeRF-cli version:        1.1.2-git-37c5b38
  libbladeRF version:         1.2.1-git-37c5b38

  Firmware version:           1.8.0
  FPGA version:               0.1.2

bladeRF>
=============================================================================================================

NIB setting as per the WIKI:

javascript.conf
; routing: string: Name of the file holding the routing instructions
; Example: routing=route.js
routing=welcome.js

ybts.conf
...
mode=nib

config folder: usr-local-etc-yate.tar.gz

yate log: yate.gz


log:

-----

Primitive: Handshake
Info: 0
-----
20150404143546.100401 <javascript:INFO> Parsed 'nib' script: /usr/local/share/yate/scripts/nib.js
20150404143546.102621 <nib:INFO> Finished reading saved registered subscribers. Found 1 registered_subscribers.
20150404143546.102855 <nib:INFO> Checked that only NIB is enabled.
20150404143546.102889 <ALL> Rescanning handler list for 'engine.start' [0x7fff13710de0] at priority 100
Yate engine is initialized and starting up on...
20150404143546.102970 <INFO> Creating first message dispatching thread
20150404143546.892332 <cpuload:NOTE> Updating CPU core number from 1 to 4
20150404143546.945799 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 1
20150404143547.946257 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 2
20150404143548.947236 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 3
20150404143549.948508 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 4
20150404143550.949599 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 5
20150404143550.949645 <mbts:NOTE> TRXManager.cpp:293:sendCommandPacket: lost control link to transceiver
ALERT 140437058942848 10:35:50.9 TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150404143550.949723 <mbts:WARN> TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150404143551.011847 <mbts:NOTE> OpenBTS.cpp:145:startTransceiver: starting transceiver ./transceiver-bladerf w/ 1 ARFCNs and Args:
20150404143551.165150 <transceiver:NOTE> bladeRFDevice.cpp:106:open: Opened bladeRF serial=13d7b32e83118203e3e6db0b04de23bf firmware version 1.8.0 (1.8.0)
20150404143551.657441 <transceiver:NOTE> Transceiver.cpp:68:Transceiver: running 1 ARFCNs with oversampling 4
Starting transceiver
20150404143555.975268 <transceiver:NOTE> bladeRFDevice.cpp:239:start: starting bladeRF in super speed mode...
20150404143555.977841 <transceiver:NOTE> bladeRFDevice.cpp:482:readSamples: RX Timestamp adjusted by 1 to 2
20150404143555.984484 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T1
20150404143555.984898 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T2
20150404143555.985388 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T3
20150404143555.985754 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T4
20150404143555.986482 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T5
20150404143555.987108 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T6
20150404143555.987557 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T7
RTNETLINK answers: File exists
20150404143556.724381 <transceiver:NOTE> Transceiver.cpp:274:pushRadioVector: dumping STALE burst in TRX->USRP interface cn=0 at 2:1779366
MBTS ready
20150404143556.744533 <ybts-signalling:INFO> Received [0x1b75500]
-----
Primitive: RadioReady
Info: 0
-----
20150404143556.744566 <ybts:NOTE> State changed Running -> RadioUp
20150404143628.743658 <ybts-signalling:INFO> Received [0x1b75500]

-----

<PhysicalInfo>TA=0 TE=0.426 UpRSSI=-11 TxPwr=33 DnRSSIdBm=-111 time=1428158188.505</PhysicalInfo>
-----
20150404143628.743916 <ybts-signalling:INFO> Received [0x1b75500]
-----
Primitive: L3Message
Info: 0
Connection: 1

<MM>
  <SkipIndicator>0</SkipIndicator>
  <NSD>0</NSD>
  <Message type="CMServiceRequest">
    <CMServiceType>MO-call-establishment-or-PM-connection-establishment</CMServiceType>
    <CipheringKeySequenceNumber>no-key/reserved</CipheringKeySequenceNumber>
    <MobileStationClassmark2>
      <RFPowerCapability>class4</RFPowerCapability>
      <RevisionLevel>GSM-phase2</RevisionLevel>
      <SSScreeningIndicator>ellipsis-notation-and-phase2-error-handling</SSScreeningIndicator>
      <Flags>ES-IND,E-GSM-and-R-GSM-support,MT-sms-point-to-point-capability,pseudo-sync-capability,A5/3-support,CMSP-support,LCS-VA-support,CM3-support</Flags>
    </MobileStationClassmark2>
    <MobileIdentity>
      <TMSI>007b0001</TMSI>
    </MobileIdentity>
  </Message>
</MM>
-----
20150404143628.743949 <ybts-signalling:ALL> Added connection (0x7fd948001ae0,1) [0x1b75500]
20150404143628.743990 <ybts-mm:ALL> Handling CMServiceRequest conn=1: ident=TMSI/007b0001 type=MO-call-establishment-or-PM-connection-establishment [0x1b758e0]
20150404143628.744009 <ybts-mm:ALL> Added UE (0x7fd948002120) TMSI=007b0001 IMSI= [0x1b758e0]
20150404143628.744021 <ybts-signalling:ALL> Connection 1 set UE (0x7fd948002120) TMSI=007b0001 IMSI= [0x7fd948001ae0]
20150404143628.744135 <ybts-signalling:INFO> Sending [0x1b75500]
-----
Primitive: L3Message
Info: 0
Connection: 1

<MM>
  <Message type="CMServiceAccept"/>
</MM>

Primitive: L3Message
Info: 0
Connection: 1

<CC>
  <TID TIFlag="false">0</TID>
  <NSD>1</NSD>
  <Message type="Setup">
    <BearerCapability1>
      <ITC>speech</ITC>
      <TransferMode>circuit-mode</TransferMode>
      <CodingStandard>GSM</CodingStandard>
      <RadioChannelRequirement>FR-and-HR-speech-version1-supported/FR-speech-preferred</RadioChannelRequirement>
      <SpeechVersions>GSM-FR-speech-version3,GSM-FR-speech-version2,GSM-FR-speech-version1,GSM-HR-speech-version3,GSM-HR-speech-version1</SpeechVersions>
    </BearerCapability1>
    <CalledPartyBCDNumber nature="unknown" plan="isdn">32843</CalledPartyBCDNumber>
    <CCCapabilities>
      <Flags>DTMF</Flags>
      <MaxSupportedBearers>0</MaxSupportedBearers>
      <MaxSpeechBearers>0</MaxSpeechBearers>
    </CCCapabilities>
  </Message>
</CC>
-----
20150404143629.084794 <ybts/1:CALL> Incoming address=TMSI007b0001 conn=1 [0x7fd948002a40]
20150404143629.084837 <ybts-signalling:INFO> Sending [0x1b75500]
-----
Primitive: AllocMedia
Info: 0
Connection: 1
-----
20150404143629.084864 <ybts/1:INFO> Call 'i0' changed state Null -> CallProceeding [0x7fd948002a40]
20150404143629.084942 <ybts-signalling:INFO> Sending [0x1b75500]
-----
Primitive: L3Message
Info: 0
Connection: 1

<CC>
  <TID TIFlag="true">0</TID>
  <Message type="CallProceeding"/>
</CC>
-----
20150404143629.084971 <ybts/1:INFO> Added call 'i0' [0x7fd948002a40]
20150404143629.085008 <ybts-signalling:INFO> Sending [0x1b75500]
-----
Primitive: StartMedia
Info: 1
Connection: 1
-----
20150404143629.085035 <ybts-signalling:ALL> Connection 1 waiting for traffic channel allocation mode=1 ... [0x1b75500]
20150404143701.558527 <mbts:NOTE> DCCHDispatch.cpp:127:connDispatchLoop: error reading on connection 1
20150404143701.558615 <ybts-signalling:INFO> Received [0x1b75500]
-----
Primitive: ConnLost
Info: 0
Connection: 1
-----
20150404143701.558659 <ybts-signalling:ALL> Removing connection (0x7fd948001ae0,1) [0x1b75500]
20150404143701.558704 <ybts/1:INFO> Connection released [0x7fd948002a40]
20150404143701.558730 <ybts/1:NOTE> deref() on releasing initial route message [0x7fd948002a40]
20150404143701.558765 <ybts/1:CALL> Hangup reason='net-out-of-order' [0x7fd948002a40][/i][/i]
20150404143701.558880 <ybts/1:CALL> Destroyed [0x7fd948002a40]
20150404143701.558931 <ybts-mm:ALL> Removed UE (0x7fd948002120): destroyed [0x1b758e0]
20150404143701.558952 <ybts:ALL> UE destroyed [0x7fd948002120]
20150404143701.559213 <mbts:MILD> SigConnection.cpp:506:process: primitive 3 length 0 took 32474 ms
20150404143701.559885 <javascript:ALL> Assistant for 'ybts/1' deleted
20150404143814.671183 <sip:ALL> Returning false from engine.stop handler
20150404143814.671203 <iaxengine:INFO> Status changed Listening -> Exiting [0x1a9ab60]
20150404143814.671207 <iaxengine:ALL> Set terminate timeout=16500ms status=Exiting [0x1a9ab60]
20150404143814.671216 <iax:INFO> Removed listener (0x1a9ab60) 'iaxengine' status='Exiting'
20150404143814.671377 <iaxengine:ALL> Thread (0x1aa8650) 'YIAXGetEvent' terminated [0x1a9ab60]
20150404143814.671537 <iaxengine:ALL> Thread (0x1aa8140) 'YIAXListener' terminated [0x1a9ab60]
20150404143814.671572 <iaxengine:ALL> Thread (0x1aa8360) 'YIAXListener' terminated [0x1a9ab60]
20150404143814.671608 <iaxengine:ALL> Thread (0x1aab290) 'YIAXListener' terminated [0x1a9ab60]
20150404143814.671666 <iaxengine:ALL> Thread (0x1aa8a90) 'YIAXGetEvent' terminated [0x1a9ab60]
20150404143814.672022 <iaxengine:ALL> Thread (0x1aa8d80) 'YIAXTrunking' terminated [0x1a9ab60]
20150404143814.672054 <jingle:ALL> YJGEngineWorker stop running
20150404143814.672935 <iaxengine:ALL> Thread (0x1aa8870) 'YIAXGetEvent' terminated [0x1a9ab60]
20150404143814.676296 <iaxengine:ALL> Destroyed [0x1a9ab60]

====================================================================================






Thank you,

Vic

Pages: [1]