Hello! I Need Help
I install these three programs OpenBTS, OsmocomBB, Asterisk
Then run them, Everything works well
OpenBTS sent an SMS to my phones
I answered and he checked me
I registered into OpenBTS a second phone
I tried to transfer SMS between phones - all good
but when I try to call from one to another I did not get
Asterisk writes
================================================================
*CLI> Retransmission timeout reached on transmission 755803415(a)127.0.0.1 for
seqno 179 (Critical Response) -- See
wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32001ms with no response
================================================================
Why?
What do I do?
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp402…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hey there, I bumped into this error when testing gprsdecode from srldabs.de When I try the sample .dat files provided from srlabs.de it works fine though. Any hints?
Kind Regards
George AndguladzeSenior Software EngineerBusiness Management Technology
www.bmt.ge
Hey, I finally watched Nico's talk "let me answer that for you" and heard him say he ported layer2/3 to target.
Also found a mailing list message about him cleaning it up and putting it up on git and sending it to a few folks.
Did that code ever get shared? Would be cool to play around with and is certainly something I would eventually want to accomplish for my project of making a phone that works by itself.
-Craig
Dear all, I vae the C115 with a T1 USB to Serial cable with the Prolific
chipset.
When i run osmocon i get :- an its just sits there with no further
processing.
./osmocon -p /dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/loader.compalram.bin
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin):
file_size=17120, hdr_len=4, dnload_len=17127
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin):
file_size=17120, hdr_len=4, dnload_len=17127
got 1 bytes from modem, data looks like: 00 .
got 2 bytes from modem, data looks like: 2f 00 /.
got 1 bytes from modem, data looks like: 1b .
got 3 bytes from modem, data looks like: f6 02 00 ...
got 1 bytes from modem, data looks like: 41 A
got 1 bytes from modem, data looks like: 01 .
got 1 bytes from modem, data looks like: 40 @
Received PROMPT1 from phone, responding with CMD
got 1 bytes from modem, data looks like: 66 f
got 1 bytes from modem, data looks like: 74 t
got 1 bytes from modem, data looks like: 6d m
got 1 bytes from modem, data looks like: 74 t
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 6c l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65 e
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
I think the cable is ok as when i run my fingers on the tip i get random
Zeros so it appears to be talking to the cable.
Also when i tried to run Mobile i get the :- even though i created the
Mobile.cfg file in /etc/osmoco
Failed to parse the config file: '/home/raz/.osmocom/bb/mobile.cfg'
Please check or create config file using: 'touch
/home/raz/.osmocom/bb/mobile.cfg'
I have spent some hours researching the lists and trying various things to
no avail but I want to continue until I resolve this issues and use this
great stack to learn about the GSM network.
Please advise.
Great full for any help or pointers but this maybe a timing issue that is
difficult to debug.
Thanks
Raz
hi,
i did a lot of resarch and testing on cell selection and re-selection
process the last two week.
the cell selection process, network selection process (manual and
automatic) and mobility management process were already implemented in
OsmocomBB a long time, but turned out to be buggy and incomplete. i made
test drives to check the process and debugged it.
the re-selection process is new. it is used to track surrounding cells
while listening to the BCCH of the current cell (camping on a cell).
special extension to the layer1 firmare is used to measure neighbour
cells. if an neighbour cell becomes 'better', the mobile switches to
that cell, depening on different criteria. now it is possible to move
with OsmocomBB.
the re-selection process is not handover! handover is a process where a
phone switches between cells while doing a call. handover is one next
step to implement. the process is a little more complex, because it
requires not only neighbour cell measurements, but also syncing to them
without interrupting the traffic channel. most layer 3 stuff of handover
is already implemented.
if you like to play and test your moving OsmocomBB, you can check out
the "jolly/roaming" branch. it contains the extension to layer1, as well
as sim reader and fixes from "sylvain/testing" branch. use both "mobile"
and "layer1" firmware from this branch.
in order to see some process at VTY, you can do:
enable
monitor network 1 (continously display the strongest cell and neighbour
cells)
show ms 1 (to see current states)
show neighbour-cells 1 (to see a more detailed current list of
neighbours)
andreas
Hi,
in the osmocom bb mobile.cfg I don't see any posibility to set a fixed
Kc encryption key and the tmsi.
How could I achieve that osmocom uses my defined Kc and tmsi?
cheers,
Simian
Hi all,
*I connected, sent and made call successful with osmocombb (with real IMSI
and IMEI).
But, now, I get error, always be rejected:*
OsmocomBB# show ms
MS '1' is up, service is limited
IMEI: 357337016773249
IMEISV: 3573370167732490
IMEI generation: fixed
automatic network selection state: A0 null
cell selection state: PLMN search
radio ressource layer state: idle
mobility management layer state: MM idle, PLMN search
OsmocomBB#
% (MS 1)
% Trying to registering with network...
*in my config file (/root/.osmocom/bb/mobile.cfg)**:*
!
! OsmocomBB () configuration saved from vty
!!
!
line vty
no login
!
gps device /dev/ttyACM0
gps baudrate default
no gps enable
!
no hide-default
!
ms 1
layer2-socket /tmp/osmocom_l2
sap-socket /tmp/osmocom_sap
sim reader
network-selection-mode auto
imei 357337016773249 0
imei-fixed
emergency-imsi 452040399998391
sms-service-center +84980200030
no call-waiting
no auto-answer
no force-rekey
no clip
no clir
tx-power auto
no simulated-delay
no stick
location-updating
neighbour-measurement
codec full-speed prefer
codec half-speed
no abbrev
support
sms
a5/1
a5/2
p-gsm
e-gsm
r-gsm
gsm-850
dcs
pcs
class-900 4
class-850 4
class-dcs 1
class-pcs 1
channel-capability sdcch+tchf+tchh
full-speech-v1
full-speech-v2
half-speech-v1
min-rxlev -106
dsc-max 90
no skip-max-per-band
exit
test-sim
imsi 001010000000000
ki xor 00 00 00 00 00 00 00 00 00 00 00 00
no barred-access
no rplmn
hplmn-search foreign-country
exit
no shutdown
exit
!
Anyone help me???, thanks a lot!
--
Thanks and Best Regards
--
From: Hoàng Mạnh Hùng
Hi there,
I am sorry to bother you but I am really confused by recent experiment.
When I was doing the GSM sniffing I found that some of sms messages that
were sent continuesly were missing, I can only capture 50-60% of all test
messages. By analyzing wireshark data I found that osmocom program keeps
tracking packets(lapdm) once an Immediate Assignment captured and if at the
same time there comes another Immediate Assignment the program will miss
it.I think this is the reason why i lost some messages.So is there any
suggestions I can fix this up? Like using a backup phone to capture the
second Immediate Assignment during one period?
Thanks,
Swift
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Missing-packet-when-sniffing-by-…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hi
I have compiled mobile app with tx support .
i.e i have checked-out the testing branch .
Layer 1 seems to be uploaded to the mobile phone successfully.
But the program crashes every-time there is a successful connection with
the network service provider.
I am attaching my mobile.log and layer1.log file along for debugging.
Hoping some one replies.
" mmsgb(0x8955b0): Not enough headroom msgb_push (4285966792 < 7)
errors
Dropping frame with 66 bit errors
Dropping frame with 65 bit errors
Dropping frame with 58 bit errors
Dropping frame with 56 bit errors
LOSS counter for CCCH 57
Dropping frame with 66 bit errors
Dropping frame with 66 bit errors
Dropping frame with 65 bit errors
Dropping frame with 65 bit errors
Dropping frame with 70 bit errors
Dropping frame with 65 bit errors
Dropping frame with 80 bit errors
LOSS counter for CCCH 53
Dropping frame with 61 bit errors
Dropping frame with 76 bit errors
Dropping frame with 57 bit errors
Dropping frame with 67 bit errors
Dropping frame with 58 bit errors
Dropping frame with 72 bit errors
Dropping frame with 63 bit errors
Dropping frame with 70 bit errors
LOSS counter for CCCH 49
Dropping frame with 57 bit errors
Dropping frame with 61 bit errors
Dropping frame with 52 bit errors
Dropping frame with 77 bit errors
Dropping frame with 60 bit errors
Dropping frame with 57 bit errors
Dropping frame with 76 bit errors
LOSS counter for CCCH 45
Dropping frame with 70 bit errors
Dropping frame with 57 bit errors
Dropping frame with 65 bit errors
Dropping frame with 46 bit errors
Dropping frame with 65 bit errors
Dropping frame with 46 bit errors
Dropping frame with 70 bit errors
Dropping frame with 77 bit errors
LOSS counter for CCCH 46
Dropping frame with 51 bit errors
Dropping frame with 56 bit errors
Dropping frame with 65 bit errors
Dropping frame with 59 bit errors
Dropping frame with 65 bit errors
Dropping frame with 60 bit errors
Dropping frame with 72 bit errors
Dropping frame with 79 bit errors
Dropping frame with 75 bit errors
Dropping frame with 59 bit errors
Dropping frame with 72 bit errors
Dropping frame with 66 bit errors
Dropping frame with 69 bit errors
Dropping frame with 70 bit errors
Dropping frame with 65 bit errors
Dropping frame with 69 bit errors
Dropping frame with 66 bit errors
Dropping frame with 82 bit errors
Dropping frame with 80 bit errors
LOSS counter for CCCH 86
Dropping frame with 67 bit errors
Dropping frame with 63 bit errors
Dropping frame with 69 bit errors
Dropping frame with 69 bit errors
Dropping frame with 66 bit errors
Dropping frame with 76 bit errors
Dropping frame with 63 bit errors
LOSS counter for CCCH 87
Dropping frame with 53 bit errors
Dropping frame with 54 bit errors
LOSS counter for CCCH 88
LOSS counter for CCCH 89
Dropping frame with 46 bit errors
Dropping frame with 50 bit errors
Dropping frame with 45 bit errors
backtrace() returned 10 addresses
/usr/local/lib/libosmocore.so.6(osmo_panic+0xbe) [0x7f3ccd0745ce]
/usr/local/lib/libosmogsm.so.5(lapdm_phsap_up+0x18e) [0x7f3cccc3cc5e]
./mobile() [0x438c29]
./mobile() [0x4394cc]
/usr/local/lib/libosmocore.so.6(osmo_wqueue_bfd_cb+0x73) [0x7f3ccd071b63]
/usr/local/lib/libosmocore.so.6(osmo_select_main+0x18f) [0x7f3ccd070b9f]
./mobile() [0x4048bf]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f3ccc679ec5]
./mobile() [0x404a46]
"
there is core dumped after this error.
Hello
This patch
1. can handle LTE RRC messages and call respective dissectors
2. can handle LTE MAC frames, fill in the struct mac_lte_info and then call
the mac-lte dissector. Following the GSMTAP header, there is a 15 byte
mac_info which is needed to fill the struct mac_lte_info.
The size mac_info need not necessarily be 15 byte. But these 15 bytes are
necessary for the lte-mac dissector to understand the frame. 15 byte header
is used by the LTE_FDD_EnodeB application from the openLTE project.
There is also a patch for gsmtap.h.
Please let me know your comments.
Cheers
Altaf
Hey folks.
In a light of latest collapse of mailing list I have a proposal for backup
communication channel. It have rather limited capacity and reachability but it's
extremely reliable in case of electronic malfunctions. It's called "real-life
meeting" ;-)
I suggest bi-weekly format, time and place is up to discussion but I'm ok with what
it used to be before. We can also have 2-way proposals - some folks can suggest
topics they would like to present while others could suggest topics they would like
to ask questions on. When enough of those match together - we have a meeting.
As a starter - I'd like to ask questions on 1) call forwarding support in OpenBSC 2)
BTS emulator.
Thought/comments/suggestions?
--
best regards,
Max, http://fairwaves.co
Dear OsmocomBB-list,
I just realized that I've been unsubscribed since November 2014 from the
baseband-devel list and now I resubscribed today. The Mail-archive seems
to start from scratch since these days, too. So I guess, that this is not
an individual problem of my email address.
What happened (HDD-crash)? Why is that not mentioned on the website? Maybe
I am not the last one realizing that?
Best
Tim
Hi,all: I have got a C118 to test mobile function 1) To get the master branch code and to compile it. 2) To insert simcard(13681******) into the phone and to modify the mobile.cfg to use real simcard. 3) To connect the phone with PC(core i5/ubuntu 12.04). 4) After downloading the firmware, to start the mobile App(#sudo ./mobile 2>&1 | tee > log.txt). 5) I can see that the location update process is ok and an TMSI is allocated to the phone. 6) To telnet into the osmocon, I can start a call to another phone (#Call 1 13564******). 7) I can send a sms to another phone. So far, all(MOC) is ok.
But If using the osmocommbb phone(13681******) as the target phone(MOT), (for example, Iuse a normal phone to call the osmocombb phone), it is very rare that the osmocombb phone have a respose to the paging. 1) I have check the paging messages in the log.txt file and find that there only one paging respone messages such as "TMSI MATCH" as I have call the osmocombb phone about 20 times. In the success case: ..............gsm322.c:1966 Cell ARFCN 13 selected.gsm322.c:2423 Tune to frequency 13.gsm322.c:468 Sync to ARFCN=13 rxlev=-68 (Sysinfo, ccch mode NON-COMB)gsm322.c:2450 Cell available.gsm322.c:4049 (ms 1) Event 'EVENT_CELL_FOUND' for Cell selection in state 'C5 choose cell'gsm322.c:3383 Camping normally on cell (ARFCN=13 mcc=460 mnc=00 China, China Mobile)gsm322.c:829 new state 'C5 choose cell' -> 'C3 camped normally'gsm48_mm.c:4325 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event in state wait for network commandgsm48_mm.c:1130 We are in registered LAI as returning to MM IDLEgsm48_mm.c:919 new state wait for network command -> MM IDLE, normal servicegsm48_mm.c:426 starting T3212 (periodic loc. upd. delay) with 7200 secondsgsm322.c:2947 Channel synched. (ARFCN=13, snr=16, BSIC=29).............. gsm48_rr.c:2116 TMSI a0b186e9 matchesgsm48_rr.c:1307 Establish radio link due to paging requestgsm322.c:4049 (ms 1) Event 'EVENT_LEAVE_IDLE' for Cell selection in state 'C3 camped normally'gsm322.c:829 new state 'C3 camped normally' -> 'connected mode 1'gsm322.c:3665 Going to camping (normal) ARFCN 13.gsm322.c:468 Sync to ARFCN=13 rxlev=-68 (Sysinfo, ccch mode NON-COMB)gsm48_rr.c:355 new state idle -> connection pendinggsm48_rr.c:1422 CHANNEL REQUEST: 20 (PAGING TCH/F)gsm322.c:2947 Channel synched. (ARFCN=13, snr=16, BSIC=29) .......... From the log info I can see that: a) the phone is camped in ARFCN 13 and receive paging in this cell. b) the signal of cell is strong enough 2) I have no an OpenBTS device to send some paging messages to check where is the problem further. Maybe I miss something. Any suggestion is appreciated! Thank you very much!
Best Regards
Shang